[Touch-packages] [Bug 1991146] Re: ibus-daemon crashed with SIGABRT

2022-09-28 Thread Gunnar Hjalmarsson
** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1991146/+attachment/5619840/+files/CoreDump.gz

** Information type changed from Private to Public

-- 
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/1991146

Title:
  ibus-daemon crashed with SIGABRT

Status in ibus package in Ubuntu:
  New

Bug description:
  Was logged on to user1 and did a Power off>Switch User to user2.
  Logged off user2 and signed in to user1.  This crash was waiting.

  ProblemType: Crash
  DistroRelease: Ubuntu 22.10
  Package: ibus 1.5.27-2
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Wed Sep 28 14:22:49 2022
  ExecutablePath: /usr/bin/ibus-daemon
  InstallationDate: Installed on 2022-09-17 (11 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220917)
  ProcCmdline: ibus-daemon --panel disable --xim
  ProcEnviron: LANG=en_US.UTF-8
  Signal: 6
  SourcePackage: ibus
  StacktraceTop:
   () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ()
   () at /lib/x86_64-linux-gnu/libgio-2.0.so.0
   () at /lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: ibus-daemon crashed with SIGABRT
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1991146/+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 1976255] Re: accountsservice ftbfs in the jammy release pocket

2022-05-30 Thread Gunnar Hjalmarsson
This was fixed via accountsservice 22.07.5-2ubuntu1.3 in jammy-updates.

** Changed in: accountsservice (Ubuntu)
   Status: New => 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/1976255

Title:
  accountsservice ftbfs in the jammy release pocket

Status in accountsservice package in Ubuntu:
  Fix Released

Bug description:
  as seen in a test rebuild, this package fails to build in the jammy
  release pocket (note the log behind the link might go away):

  https://launchpadlibrarian.net/604216054/buildlog_ubuntu-jammy-
  amd64.accountsservice_22.07.5-2ubuntu1_BUILDING.txt.gz

  Ok: 2   
  Expected Fail:  0   
  Fail:   10  
  Unexpected Pass:0   
  Skipped:0   
  Timeout:0   

  Full log written to 
/<>/obj-x86_64-linux-gnu/meson-logs/testlog.txt
cd obj-x86_64-linux-gnu && tail -v -n \+0 meson-logs/testlog.txt
  ==> meson-logs/testlog.txt <==
  Log of Meson test suite run on 2022-05-30T08:33:42.861398

  Inherited environment: SCHROOT_GID=2501
  DEB_HOST_MULTIARCH=x86_64-linux-gnu LC_ALL=C.UTF-8
  DEB_HOST_GNU_SYSTEM=linux-gnu DEB_BUILD_GNU_TYPE=x86_64-linux-gnu
  DEB_LDFLAGS_MAINT_APPEND=-Wl,--as-needed DEB_TARGET_ARCH_LIBC=gnu
  DEB_BUILD_ARCH_ENDIAN=little DEB_BUILD_GNU_SYSTEM=linux-gnu
  DEB_BUILD_ARCH_BITS=64 DEB_BUILD_OPTIONS=parallel=4
  DEB_HOST_ARCH=amd64 DEB_TARGET_ARCH_ENDIAN=little
  DEB_BUILD_PROFILES=noudeb SOURCE_DATE_EPOCH=1645543676 V=1
  DEB_HOST_ARCH_BITS=64 LANG=C.UTF-8 MAKEFLAGS='' SCHROOT_GROUP=buildd
  DEB_TARGET_ARCH=amd64 DEB_HOST_GNU_CPU=x86_64 DEB_BUILD_ARCH_LIBC=gnu
  MFLAGS='' DEB_TARGET_ARCH_BITS=64 DEB_BUILD_ARCH_CPU=amd64
  SCHROOT_ALIAS_NAME=build-PACKAGEBUILD-23614463 DEB_HOST_ARCH_OS=linux
  SHELL=/bin/sh DEB_HOST_ARCH_CPU=amd64 SCHROOT_USER=buildd
  PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
  DEB_BUILD_ARCH_ABI=base DEB_BUILD_ARCH=amd64 DEB_HOST_ARCH_LIBC=gnu
  SCHROOT_SESSION_ID=build-PACKAGEBUILD-23614463
  DEB_TARGET_ARCH_CPU=amd64 DEB_HOST_GNU_TYPE=x86_64-linux-gnu
  DEB_BUILD_ARCH_OS=linux LOGNAME=buildd
  DEB_TARGET_MULTIARCH=x86_64-linux-gnu DEB_BUILD_GNU_CPU=x86_64
  DEB_TARGET_ARCH_OS=linux USER=buildd DEB_HOST_ARCH_ABI=base
  DEB_BUILD_MULTIARCH=x86_64-linux-gnu DEB_TARGET_GNU_TYPE=x86_64-linux-
  gnu DEB_TARGET_ARCH_ABI=base SCHROOT_UID=2001 SCHROOT_COMMAND='dpkg-
  buildpackage -us -uc -mLaunchpad Build Daemon
   -b -rfakeroot'
  DEB_TARGET_GNU_CPU=x86_64 APT_CONFIG=/var/lib/sbuild/apt.conf
  HOME=/<>/debian/.debhelper/generated/_source/home
  DEB_RULES_REQUIRES_ROOT=binary-targets DEB_TARGET_GNU_SYSTEM=linux-gnu
  DEB_HOST_ARCH_ENDIAN=little TERM=unknown SCHROOT_CHROOT_NAME=build-
  PACKAGEBUILD-23614463 MAKELEVEL=1 DH_INTERNAL_BUILDFLAGS=1 ASFLAGS=''
  CFLAGS='-g -O2 -ffile-prefix-map=/<>=. -flto=auto -ffat-
  lto-objects -flto=auto -ffat-lto-objects -fstack-protector-strong
  -Wformat -Werror=format-security' CPPFLAGS='-Wdate-time
  -D_FORTIFY_SOURCE=2' CXXFLAGS='-g -O2 -ffile-prefix-
  map=/<>=. -flto=auto -ffat-lto-objects -flto=auto -ffat-
  lto-objects -fstack-protector-strong -Wformat -Werror=format-security'
  DFLAGS=-frelease FCFLAGS='-g -O2 -ffile-prefix-map=/<>=.
  -flto=auto -ffat-lto-objects -flto=auto -ffat-lto-objects -fstack-
  protector-strong' FFLAGS='-g -O2 -ffile-prefix-map=/<>=.
  -flto=auto -ffat-lto-objects -flto=auto -ffat-lto-objects -fstack-
  protector-strong' GCJFLAGS='-g -O2 -ffile-prefix-
  map=/<>=. -flto=auto -ffat-lto-objects -fstack-protector-
  strong' LDFLAGS='-Wl,-Bsymbolic-functions -flto=auto -ffat-lto-objects
  -flto=auto -Wl,-z,relro -Wl,--as-needed' OBJCFLAGS='-g -O2 -ffile-
  prefix-map=/<>=. -flto=auto -ffat-lto-objects -flto=auto
  -ffat-lto-objects -fstack-protector-strong -Wformat -Werror=format-
  security' OBJCXXFLAGS='-g -O2 -ffile-prefix-map=/<>=.
  -flto=auto -ffat-lto-objects -flto=auto -ffat-lto-objects -fstack-
  protector-strong -Wformat -Werror=format-security'
  XDG_RUNTIME_DIR=/tmp/dh-xdg-rundir-JPi9I5rR MESON_TESTTHREADS=4

   1/12 accountsservice:accounts-service+libaccountsservice+TestAccountsService 
/ TestAccountsService.test_cache_user   FAIL0.33s   
exit status 1
  08:33:42 
LD_LIBRARY_PATH=/<>/obj-x86_64-linux-gnu/src/libaccountsservice 
GI_TYPELIB_PATH=/<>/obj-x86_64-linux-gnu/src/libaccountsservice 
G_DEBUG=fatal-criticals G_MESSAGES_DEBUG=all MALLOC_PERTURB_=58 
/usr/bin/python3 
/<>/obj-x86_64-linux-gnu/../tests/test-libaccountsservice.py 
TestAccountsService.test_cache_user
  --- output ---
  test_cache_user (__main__.TestAccountsService) ... (process:11790): 
accountsservice-DEBUG: 08:33:43.062: Finding a graphical session for user 2001
  (process:11790): accountsservice-DEBUG: 08:33:43.062: Failed to identify the 
current session
  (process:11790): 

[Touch-packages] [Bug 1974250] Re: ~/.pam_environment gets created as owned by root

2022-05-27 Thread Gunnar Hjalmarsson
On 2022-05-20 16:54, Marc Deslauriers wrote:
> Or remove those scripts from Debian completely...looks like they
> were added because of https://bugs.debian.org/cgi- 
> bin/bugreport.cgi?bug=756259 , but muon doesn't seem to use them
> anymore...

FTR I removed 0009-language-tools.patch from Debian.

https://salsa.debian.org/freedesktop-
team/accountsservice/-/commit/294910b8

Let's see if somebody complains.. Hopefully not.

-- 
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/1974250

Title:
  ~/.pam_environment gets created as owned by root

Status in accountsservice package in Ubuntu:
  Fix Released
Status in accountsservice source package in Jammy:
  Fix Released
Status in accountsservice source package in Kinetic:
  Fix Released

Bug description:
  Something has happened lately with accountsservice, which makes it act
  as root instead of the current user when creating ~/.pam_environment.
  The very old bug #904395 comes to mind, and this smells a security
  issue.

  The function which is supposed to prevent this behavior is here:

  https://salsa.debian.org/freedesktop-
  team/accountsservice/-/blob/ubuntu/debian/patches/0010-set-
  language.patch#L75

  Haven't investigated further yet.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1974250/+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 1974250] Re: ~/.pam_environment gets created as owned by root

2022-05-24 Thread Gunnar Hjalmarsson
** Changed in: accountsservice (Ubuntu Kinetic)
   Status: Confirmed => Fix Committed

-- 
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/1974250

Title:
  ~/.pam_environment gets created as owned by root

Status in accountsservice package in Ubuntu:
  Fix Committed
Status in accountsservice source package in Jammy:
  Fix Released
Status in accountsservice source package in Kinetic:
  Fix Committed

Bug description:
  Something has happened lately with accountsservice, which makes it act
  as root instead of the current user when creating ~/.pam_environment.
  The very old bug #904395 comes to mind, and this smells a security
  issue.

  The function which is supposed to prevent this behavior is here:

  https://salsa.debian.org/freedesktop-
  team/accountsservice/-/blob/ubuntu/debian/patches/0010-set-
  language.patch#L75

  Haven't investigated further yet.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1974250/+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 1974217] Re: ibus not detecting other languages other than default english

2022-05-19 Thread Gunnar Hjalmarsson
Thanks for your report.

Which ibus applet are you talking about? On Ubuntu with the GNOME
desktop you are supposed to add IBus input methods via Settings ->
Keyboard -> Input Sources.

Please let us know whether that helps.

** 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/1974217

Title:
  ibus not detecting other languages other than default english

Status in ibus package in Ubuntu:
  Incomplete

Bug description:
  ibus not detecting other languages. I cannot change languages with
  ibus applet

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ibus 1.5.26-4
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Uname: Linux 5.15.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 19 22:19:05 2022
  ExecutablePath: /usr/libexec/ibus-x11
  InstallationDate: Installed on 2022-04-26 (23 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  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/1974217/+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 1973424] Re: ibus-extension-gtk3 does not start automatically

2022-05-14 Thread Gunnar Hjalmarsson
*** This bug is a duplicate of bug 1969637 ***
https://bugs.launchpad.net/bugs/1969637

Thanks for your report!

If you install gnome-settings-daemon 42.1-1ubuntu2.1 from jammy-
proposed, the issue will hopefully go away. Please let us know if that
is not sufficient.

Marking this bug as a duplicate in the meantime.

** Package changed: ibus (Ubuntu) => gnome-settings-daemon (Ubuntu)

** This bug has been marked a duplicate of bug 1969637
   IBus lookup table appears bottom left of application (x11)

-- 
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/1973424

Title:
  ibus-extension-gtk3 does not start automatically

Status in gnome-settings-daemon package in Ubuntu:
  New

Bug description:
  ibus-extension-gtk3 does not start automatically, which causes the
  candidate box of the Ibus input method to not follow the cursor of any
  gtk application.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ibus 1.5.26-4
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 14 22:18:41 2022
  InstallationDate: Installed on 2022-04-23 (21 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1973424/+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 1892825] Re: update-locale not perform correctly sanity checks

2022-05-11 Thread Gunnar Hjalmarsson
This was fixed in devel (and with that jammy) through the upload of
glibc 2.35-0ubuntu1, even if it wasn't mentioned in d/changelog. So
marking as fixed.

** Changed in: glibc (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  update-locale not perform correctly sanity checks

Status in glibc package in Ubuntu:
  Fix Released
Status in pam package in Ubuntu:
  New
Status in glibc source package in Bionic:
  New
Status in pam source package in Bionic:
  New
Status in glibc source package in Focal:
  Fix Released
Status in pam source package in Focal:
  New
Status in glibc source package in Hirsute:
  Won't Fix
Status in pam source package in Hirsute:
  New
Status in glibc source package in Impish:
  New
Status in pam source package in Impish:
  New

Bug description:
  [impact]
  A simple typo using the update-locale script can render a system inoperable 
without booting into single user mode or similar:

  $ sudo update-locale LANGUAGE = en_US.UTF-8
  $ sudo -s
  sudo: pam_open_session: Bad item passed to pam_*_item()
  sudo: policy plugin failed session initialization

  [test case]
  $ cp /etc/default/locale /tmp/locale
  $ update-locale --locale-file /tmp/locale LANGUAGE = en_US.UTF-8

  "diff -u /etc/default/locale /tmp/locale" should be empty.

  $ update-locale --locale-file /tmp/locale LANGUAGE=en_US.UTF-8

  The LANGUAGE=en_US.UTF-8 line should have been replaced by
  LANGUAGE=en_GB.UTF-8.

  $ update-locale --locale-file /tmp/locale LANGUAGE

  The LANGUAGE setting is now commented out.

  [regression potential]
  Apart from the general concerns about a glibc rebuild, this is a simple 
change to a simple script. Performing the test as in the test case section is 
enough to ensure it still works.

  [original description]
  By passing wrong input as following:
   sudo update-locale LANGUAGE = en_US.UTF-8
  result is:
  ...
  #LANGUAGE=en
  =

  This "equal" sign that was added makes system completely
  unusable(can't run sudo anymore):

  bentzy@bentzy-nb:~$ sudo vim /etc/default/locale
  sudo: pam_open_session: Bad item passed to pam_*_item()
  sudo: policy plugin failed session initialization

  Fixed it booting from installation disk and fixing corrupted
  /etc/default/locale

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: locales 2.31-0ubuntu9
  Uname: Linux 5.5.4-050504-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Tue Aug 25 09:36:03 2020
  InstallationDate: Installed on 2020-08-17 (7 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: glibc
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1892825/+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 1969396] Re: Can't use Right Alt as compose key with English (Dvorak, alt. intl.) layout

2022-04-27 Thread Gunnar Hjalmarsson
Now I have tested a bit more back and forth, and here is a new attempt
to describe the nature of the issue:

Whether Right Alt works as the compose key or not depends mostly on
where in the list of input sources the keyboard layout in effect is
present.

If the layout in effect is the first one in the list, Right Alt works
fine as compose key. This is true whether Alternate Characters Key is
switched off or set to "None". (No problem with "English (Dvorak, alt.,
intl.)" either, in other words, if that layout is first in the list of
input sources.)

If the layout in effect is further down in the list, Right Alt may or
may not work as compose key. Not sure about the exact pattern here.

As regards Alternate Characters Key, I notice a marginal impact. If the
English (US) layout is not the first layout in the list, Right Alt works
as compose key with that layout if Alternate Characters Key is switched
off, but not if it's set to "None". It should be noted that English (US)
does not set Right Alt to the 3rd level key by default.

Steve, does the above description reflect your observations too?

Over to the question whether this is a g-c-c bug to some extent. I still
think that g-c-c sets sensible options, and that the unexpected behavior
is rather an XKB issue. The reason why Alternate Characters Key sets
"lv3:ralt_alt" is that it assumes that a user who picks something else
but Right Alt wants to be able to use Right Alt as any Alt key.

OTOH, given this issue wrt Right Alt as compose key, you can argue that
g-c-c should better not provide Right Alt as a compose key option...

** Summary changed:

- Can't use Right Alt as compose key with English (Dvorak, alt. intl.) layout
+ Right Alt not working reliably as compose key unless the layout in effect is 
first in the list of sources

-- 
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/1969396

Title:
  Right Alt not working reliably as compose key unless the layout in
  effect is first in the list of sources

Status in gnome-control-center package in Ubuntu:
  New
Status in xkeyboard-config package in Ubuntu:
  Confirmed

Bug description:
  I noticed after upgrade from impish to jammy that my compose key is
  not working correctly.

  Going into gnome-control-center -> Keyboard, I see that 'Alternate
  Characters Key' and 'Compose Key' are both set to Right Alt.

  Setting Alternate Characters Key to None, and moving the Compose Key
  setting around between different options (and then back to Right Alt),
  the behavior of the Right Alt key is still AltGr and not Compose.
  From xev:

  KeyPress event, serial 37, synthetic NO, window 0x401,
  root 0x50e, subw 0x0, time 287242336, (310,502), root:(434,617),
  state 0x10, keycode 108 (keysym 0xfe03, ISO_Level3_Shift), same_screen 
YES,
  XKeysymToKeycode returns keycode: 92
  XLookupString gives 0 bytes: 
  XmbLookupString gives 0 bytes: 
  XFilterEvent returns: False

  KeyRelease event, serial 37, synthetic NO, window 0x401,
  root 0x50e, subw 0x0, time 287242456, (310,502), root:(434,617),
  state 0x90, keycode 108 (keysym 0xfe03, ISO_Level3_Shift), same_screen 
YES,
  XKeysymToKeycode returns keycode: 92
  XLookupString gives 0 bytes: 
  XFilterEvent returns: False

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-control-center 1:41.4-1ubuntu12
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon 
znvpair
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 18 16:01:10 2022
  InstallationDate: Installed on 2019-12-23 (847 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to jammy on 2022-04-15 (3 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1969396/+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 1969396] Re: Can't use Right Alt as compose key with English (Dvorak, alt. intl.) layout

2022-04-19 Thread Gunnar Hjalmarsson
I concluded that the description was related to the use of the
us+dvorak-alt-intl layout, and not to g-c-c setting incorrect options.
Observations from use of the us+intl layout:

Alternate Characters Key to None

$ gsettings get org.gnome.desktop.input-sources xkb-options
['lv3:ralt_alt']

Right Alt according to xev: Alt_R

Alternate Characters Key to None + Compose key to Right Ctrl

$ gsettings get org.gnome.desktop.input-sources xkb-options
['lv3:ralt_alt', 'compose:rctrl']

Right Alt according to xev: Alt_R
Right Ctrl according to xev: Multi_key

Alternate Charters Key to None + Compose key to Right Alt
-
$ gsettings get org.gnome.desktop.input-sources xkb-options
['lv3:ralt_alt', 'compose:ralt']

Right Alt according to xev: Multi_key

I see only expected options and expected results. So please elaborate on
how you think that g-c-c behaves incorrectly, preferably with a
reproducible use case.

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Incomplete

-- 
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/1969396

Title:
  Can't use Right Alt as compose key with English (Dvorak, alt. intl.)
  layout

Status in gnome-control-center package in Ubuntu:
  Incomplete
Status in xkeyboard-config package in Ubuntu:
  Confirmed

Bug description:
  I noticed after upgrade from impish to jammy that my compose key is
  not working correctly.

  Going into gnome-control-center -> Keyboard, I see that 'Alternate
  Characters Key' and 'Compose Key' are both set to Right Alt.

  Setting Alternate Characters Key to None, and moving the Compose Key
  setting around between different options (and then back to Right Alt),
  the behavior of the Right Alt key is still AltGr and not Compose.
  From xev:

  KeyPress event, serial 37, synthetic NO, window 0x401,
  root 0x50e, subw 0x0, time 287242336, (310,502), root:(434,617),
  state 0x10, keycode 108 (keysym 0xfe03, ISO_Level3_Shift), same_screen 
YES,
  XKeysymToKeycode returns keycode: 92
  XLookupString gives 0 bytes: 
  XmbLookupString gives 0 bytes: 
  XFilterEvent returns: False

  KeyRelease event, serial 37, synthetic NO, window 0x401,
  root 0x50e, subw 0x0, time 287242456, (310,502), root:(434,617),
  state 0x90, keycode 108 (keysym 0xfe03, ISO_Level3_Shift), same_screen 
YES,
  XKeysymToKeycode returns keycode: 92
  XLookupString gives 0 bytes: 
  XFilterEvent returns: False

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-control-center 1:41.4-1ubuntu12
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon 
znvpair
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 18 16:01:10 2022
  InstallationDate: Installed on 2019-12-23 (847 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to jammy on 2022-04-15 (3 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1969396/+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 1969396] Re: gnome-control-center compose key setting does not set compose key

2022-04-19 Thread Gunnar Hjalmarsson
>> 1. Which keyboard layout are you using?
> 
> English (Dvorak, alt. intl.)

There is something with that layout. With that enabled I can reproduce
the problem. Both on jammy and impish.

>> 2. What happens if you drop the 'lv3:none' option, so you only have:
>> ['altwin:menu', 'compose:ralt']
> 
> This works.

It doesn't work for me with the "English (Dvorak, alt. intl.)" layout.
Unlike when using for instance the Swedish or "English (US, intl., with
dead keys)" layout, 'compose:ralt' does not override the layout's
default definition of "Right Alt" as the 3rd level key. Can it be some
kind of race condition?

So it seems to be the combination of Right Alt as compose key and the
English (Dvorak, alt. intl.) layout which does not work. I changed the
bug title accordingly.

And AFAICT gnome-control-center sets the expected XKB options, so it's
not a g-c-c bug. Maybe an xkeyboard-config bug.

@Steve: Are we agreed on this problem description?

** Summary changed:

- gnome-control-center compose key setting does not set compose key
+ Can't use Right Alt as compose key with English (Dvorak, alt. intl.) layout

** Package changed: gnome-control-center (Ubuntu) => xkeyboard-config
(Ubuntu)

** Changed in: xkeyboard-config (Ubuntu)
   Importance: High => Medium

** Changed in: xkeyboard-config (Ubuntu)
   Status: Incomplete => Confirmed

** Tags added: impish

-- 
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/1969396

Title:
  Can't use Right Alt as compose key with English (Dvorak, alt. intl.)
  layout

Status in xkeyboard-config package in Ubuntu:
  Confirmed

Bug description:
  I noticed after upgrade from impish to jammy that my compose key is
  not working correctly.

  Going into gnome-control-center -> Keyboard, I see that 'Alternate
  Characters Key' and 'Compose Key' are both set to Right Alt.

  Setting Alternate Characters Key to None, and moving the Compose Key
  setting around between different options (and then back to Right Alt),
  the behavior of the Right Alt key is still AltGr and not Compose.
  From xev:

  KeyPress event, serial 37, synthetic NO, window 0x401,
  root 0x50e, subw 0x0, time 287242336, (310,502), root:(434,617),
  state 0x10, keycode 108 (keysym 0xfe03, ISO_Level3_Shift), same_screen 
YES,
  XKeysymToKeycode returns keycode: 92
  XLookupString gives 0 bytes: 
  XmbLookupString gives 0 bytes: 
  XFilterEvent returns: False

  KeyRelease event, serial 37, synthetic NO, window 0x401,
  root 0x50e, subw 0x0, time 287242456, (310,502), root:(434,617),
  state 0x90, keycode 108 (keysym 0xfe03, ISO_Level3_Shift), same_screen 
YES,
  XKeysymToKeycode returns keycode: 92
  XLookupString gives 0 bytes: 
  XFilterEvent returns: False

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-control-center 1:41.4-1ubuntu12
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon 
znvpair
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 18 16:01:10 2022
  InstallationDate: Installed on 2019-12-23 (847 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to jammy on 2022-04-15 (3 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1969396/+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 1968478] Re: ibus-x11 crashed with SIGSEGV in g_closure_invoke()

2022-04-10 Thread Gunnar Hjalmarsson
Thanks for your report.

I'm not sure if it's related, but accidentally I have just uploaded a
fix of bug #1968459. It would be good if you could upgrade to ibus
1.5.26-4 when it becomes available, and let us know if the problem
persists with that version.

** 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/1968478

Title:
  ibus-x11 crashed with SIGSEGV in g_closure_invoke()

Status in ibus package in Ubuntu:
  Incomplete

Bug description:
  Description:  Ubuntu Jammy Jellyfish (development branch)
  Release:  22.04

  ibus:
Installed: 1.5.26-3
Candidate: 1.5.26-3
Version table:
   *** 1.5.26-3 500
  500 http://pl.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status

  4) What happened instead
  closed

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: ibus 1.5.26-3
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 10 16:44:38 2022
  Disassembly: => 0x7fba2e2504f0:   Cannot access memory at address 
0x7fba2e2504f0
  ExecutablePath: /usr/libexec/ibus-x11
  InstallationDate: Installed on 2022-04-10 (0 days ago)
  InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 
(20220409)
  ProcCmdline: /usr/libexec/ibus-x11
  SegvAnalysis:
   Segfault happened at: 0x7fba2e2504f0:Cannot access memory at address 
0x7fba2e2504f0
   PC (0x7fba2e2504f0) not located in a known VMA region (needed executable 
region)!
  SegvReason: executing unknown VMA
  Signal: 11
  SourcePackage: ibus
  StacktraceTop:
   ?? ()
   g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: ibus-x11 crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1968478/+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 1968478] Re: ibus-x11 crashed with SIGSEGV in g_closure_invoke()

2022-04-10 Thread Gunnar Hjalmarsson
** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1968478/+attachment/5578958/+files/CoreDump.gz

** Information type changed from Private to Public

-- 
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/1968478

Title:
  ibus-x11 crashed with SIGSEGV in g_closure_invoke()

Status in ibus package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu Jammy Jellyfish (development branch)
  Release:  22.04

  ibus:
Installed: 1.5.26-3
Candidate: 1.5.26-3
Version table:
   *** 1.5.26-3 500
  500 http://pl.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status

  4) What happened instead
  closed

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: ibus 1.5.26-3
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 10 16:44:38 2022
  Disassembly: => 0x7fba2e2504f0:   Cannot access memory at address 
0x7fba2e2504f0
  ExecutablePath: /usr/libexec/ibus-x11
  InstallationDate: Installed on 2022-04-10 (0 days ago)
  InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 
(20220409)
  ProcCmdline: /usr/libexec/ibus-x11
  SegvAnalysis:
   Segfault happened at: 0x7fba2e2504f0:Cannot access memory at address 
0x7fba2e2504f0
   PC (0x7fba2e2504f0) not located in a known VMA region (needed executable 
region)!
  SegvReason: executing unknown VMA
  Signal: 11
  SourcePackage: ibus
  StacktraceTop:
   ?? ()
   g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: ibus-x11 crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1968478/+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 1968459] Re: IBus 1.5.26 does not enable on Xorg sesson

2022-04-10 Thread Gunnar Hjalmarsson
Thanks for your report and the proposed solution. Fix is on its way, in
unstable to start with:

https://tracker.debian.org/news/1317558/accepted-ibus-1526-4-source-
into-unstable/

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

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

** Changed in: ibus (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 ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1968459

Title:
  IBus 1.5.26 does not enable on Xorg sesson

Status in ibus:
  New
Status in ibus package in Ubuntu:
  In Progress
Status in ibus package in Debian:
  Unknown

Bug description:
  I tested newly installed Ubuntu 22.04 LTS dev.

  step to reproduce:
  1. boot
  2. select user
  3. session changes to Ubuntu on Xorg from Ubuntu
  4. enter password
  5. run gedit
  6. put Hankaku/Zenkaku key
  7. nothing to happen

  consideration:
  Run "ps ax |grep ibus" on terminal:
  $ ps ax |grep ibus
     5774 ?Ss 0:00 sh -c /usr/bin/ibus-daemon --panel disable $([[ 
$XDG_SESSION_TYPE == "x11" ]] && echo "--xim")
     5779 ?Sl 0:00 /usr/bin/ibus-daemon --panel disable
     5863 ?Sl 0:00 /usr/libexec/ibus-dconf
     5864 ?Sl 0:00 /usr/libexec/ibus-extension-gtk3
     5868 ?Sl 0:00 /usr/libexec/ibus-portal
     5965 ?Sl 0:00 /usr/lib/ibus-mozc/ibus-engine-mozc --ibus
     6831 pts/1R+ 0:00 grep --color=auto ibus
  It is strange.

  IBus 1.5.25 introduces systemd user unit files.
  /usr/lib/systemd/user/org.freedesktop.IBus.session.GNOME.service
  /usr/lib/systemd/user/org.freedesktop.IBus.session.generic.service
  above contains "ExecStart=sh -c '/usr/bin/ibus-daemon --panel disable $([[ 
$XDG_SESSION_TYPE == "x11" ]] && echo "--xim")"
  
https://github.com/ibus/ibus/blob/master/bus/services/org.freedesktop.IBus.session.GNOME.service.in#L21
  It may be bashism.
  I changed to "ExecStart=bash -c '/usr/bin/ibus-daemon --panel disable $([[ 
$XDG_SESSION_TYPE == "x11" ]] && echo "--xim")" and reboot then works as 
expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ibus/+bug/1968459/+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 1965563] Re: gnome-extensions-app fails to start (Protocol error)

2022-03-30 Thread Gunnar Hjalmarsson
I see a similar error message when trying to start yelp:

$ yelp
Gdk-Message: 01:23:31.232: Error flushing display: Protocol error
$ gnome-extensions-app
Gdk-Message: 01:23:48.075: Error reading events from display: Protocol error

-- 
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/1965563

Title:
  gnome-extensions-app fails to start (Protocol error)

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  $ dpkg-query -W gnome-shell-extension-prefs
  gnome-shell-extension-prefs   42~beta-1ubuntu3
  $ gnome-extensions-app
  Gdk-Message: 17:54:19.697: Error reading events from display: Protocol error

  Caveat: I currently have a mix of packages from jammy-release and
  jammy-proposed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965563/+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 1966552] Re: IBus input method candidate box cannot follow the cursor

2022-03-29 Thread Gunnar Hjalmarsson
** Bug watch added: github.com/ibus/ibus/issues #2391
   https://github.com/ibus/ibus/issues/2391

** Also affects: ibus via
   https://github.com/ibus/ibus/issues/2391
   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/1966552

Title:
  IBus input method candidate box cannot follow the cursor

Status in ibus:
  Unknown
Status in ibus package in Ubuntu:
  New
Status in ibus-libpinyin package in Ubuntu:
  New

Bug description:
  I have tested it in some software, such as Microsoft Edge, Onlyoffice,
  and it does not follow the cursor position correctly, but always at
  the bottom left of the application window. However, in some
  applications such as Gedit, it works fine.

  Pictures are here:https://i.bmp.ovh/imgs/2022/03/34ebb5158ceeedfc.png

  OS: Ubuntu Jammy Jellyfish
  Kernel: 5.15.0-23-generic
  on Wayland

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ibus-libpinyin 1.12.1-2ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 26 23:59:28 2022
  InstallationDate: Installed on 2022-02-09 (45 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  SourcePackage: ibus-libpinyin
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ibus/+bug/1966552/+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 1965563] Re: gnome-extensions-app fails to start (Protocol error)

2022-03-29 Thread Gunnar Hjalmarsson
I installed version 42.0-1ubuntu1 of the mutter and gnome-shell
packages. Didn't help, neither on Wayland nor Xorg.

-- 
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/1965563

Title:
  gnome-extensions-app fails to start (Protocol error)

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  $ dpkg-query -W gnome-shell-extension-prefs
  gnome-shell-extension-prefs   42~beta-1ubuntu3
  $ gnome-extensions-app
  Gdk-Message: 17:54:19.697: Error reading events from display: Protocol error

  Caveat: I currently have a mix of packages from jammy-release and
  jammy-proposed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965563/+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 1966552] Re: IBus input method candidate box cannot follow the cursor

2022-03-27 Thread Gunnar Hjalmarsson
Ok, so setting "GTK_IM_MODULE=ibus" would work around the issue. That's
valuable knowledge, and thank you for figuring it out.

Unfortunately you are not supposed to set that variable explicitly on a
GNOME desktop, and especially not in a Wayland session. Doing so has
adverse side effects, so we can't do it for all users just like that.

The root cause might be in some GNOME package, e.g. mutter. Not sure how
to proceed. Maybe report it to ibus upstream to ask for help with the
analysis.

-- 
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/1966552

Title:
  IBus input method candidate box cannot follow the cursor

Status in ibus package in Ubuntu:
  New
Status in ibus-libpinyin package in Ubuntu:
  New

Bug description:
  I have tested it in some software, such as Microsoft Edge, Onlyoffice,
  and it does not follow the cursor position correctly, but always at
  the bottom left of the application window. However, in some
  applications such as Gedit, it works fine.

  Pictures are here:https://i.bmp.ovh/imgs/2022/03/34ebb5158ceeedfc.png

  OS: Ubuntu Jammy Jellyfish
  Kernel: 5.15.0-23-generic
  on Wayland

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ibus-libpinyin 1.12.1-2ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 26 23:59:28 2022
  InstallationDate: Installed on 2022-02-09 (45 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  SourcePackage: ibus-libpinyin
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1966552/+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 1966552] Re: IBus input method candidate box cannot follow the cursor

2022-03-27 Thread Gunnar Hjalmarsson
In any case using /etc/environment on Ubuntu for this purpose won't
happen. But maybe your finding can be helpful in figuring out a proper
fix.

Can you please clean up your /etc/environment from IM related variables,
reboot, and run this command:

env | grep -E 'XMOD|_IM'

Probably it outputs:

XMODIFIERS=@im=ibus
QT_IM_MODULE=ibus

Then, as a test, please add only this line to /etc/environment:

GTK_IM_MODULE=ibus

and reboot. Is that sufficient to make the candidate window be shown
correctly on e.g. Microsoft Edge?

-- 
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/1966552

Title:
  IBus input method candidate box cannot follow the cursor

Status in ibus package in Ubuntu:
  New
Status in ibus-libpinyin package in Ubuntu:
  New

Bug description:
  I have tested it in some software, such as Microsoft Edge, Onlyoffice,
  and it does not follow the cursor position correctly, but always at
  the bottom left of the application window. However, in some
  applications such as Gedit, it works fine.

  Pictures are here:https://i.bmp.ovh/imgs/2022/03/34ebb5158ceeedfc.png

  OS: Ubuntu Jammy Jellyfish
  Kernel: 5.15.0-23-generic
  on Wayland

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ibus-libpinyin 1.12.1-2ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 26 23:59:28 2022
  InstallationDate: Installed on 2022-02-09 (45 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  SourcePackage: ibus-libpinyin
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1966552/+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 1966552] Re: IBus input method candidate box cannot follow the cursor

2022-03-27 Thread Gunnar Hjalmarsson
I doubt that. The page you linked to does not apply to Debian/Ubuntu
systems. On GNOME desktops (including Ubuntu) we let GNOME set the
required environment variables, and on other desktops they are set via
the im-config package.

Also, I don't understand how the page is related to the problem with the
position of the candidate window.

-- 
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/1966552

Title:
  IBus input method candidate box cannot follow the cursor

Status in ibus package in Ubuntu:
  New
Status in ibus-libpinyin package in Ubuntu:
  New

Bug description:
  I have tested it in some software, such as Microsoft Edge, Onlyoffice,
  and it does not follow the cursor position correctly, but always at
  the bottom left of the application window. However, in some
  applications such as Gedit, it works fine.

  Pictures are here:https://i.bmp.ovh/imgs/2022/03/34ebb5158ceeedfc.png

  OS: Ubuntu Jammy Jellyfish
  Kernel: 5.15.0-23-generic
  on Wayland

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ibus-libpinyin 1.12.1-2ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 26 23:59:28 2022
  InstallationDate: Installed on 2022-02-09 (45 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  SourcePackage: ibus-libpinyin
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1966552/+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 1966552] Re: IBus input method candidate box cannot follow the cursor

2022-03-26 Thread Gunnar Hjalmarsson
Thanks for your report!

I tested on some applications shipped with Ubuntu by default
(LibreOffice Writer, Firefox, gedit, gnome-terminal) and couldn't
reproduce the issue. On Wayland session (not Xorg) I did notice that if
I open e.g. gedit or LibreOffice Writer, the candidate window may be
shown at the wrong position after my very first key press. But already
after the second key press it's shown close to the cursor as expected.

Maybe the issue is specific to certain applications, such as those you
mentioned.

Anyway, I think this is an ibus issue rather than an ibus-libpinyin one.
It would be good if you could confirm that by installing e.g. ibus-
hangul and see if the issue is present also when inputting Korean.

Also, the issue is an upstream one. If you too conclude that it's
probably an ibus issue, it would be great if you could submit an
upstream issue:

https://github.com/ibus/ibus/issues/

If you do, please post the URL to it in a comment here for tracking
purposes.

** Also 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/1966552

Title:
  IBus input method candidate box cannot follow the cursor

Status in ibus package in Ubuntu:
  New
Status in ibus-libpinyin package in Ubuntu:
  New

Bug description:
  I have tested it in some software, such as Microsoft Edge, Onlyoffice,
  and it does not follow the cursor position correctly, but always at
  the bottom left of the application window. However, in some
  applications such as Gedit, it works fine.

  Pictures are here:https://i.bmp.ovh/imgs/2022/03/34ebb5158ceeedfc.png

  OS: Ubuntu Jammy Jellyfish
  Kernel: 5.15.0-23-generic
  on Wayland

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ibus-libpinyin 1.12.1-2ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 26 23:59:28 2022
  InstallationDate: Installed on 2022-02-09 (45 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  SourcePackage: ibus-libpinyin
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1966552/+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 1966356] Re: ibus input method not working

2022-03-24 Thread Gunnar Hjalmarsson
I can't reproduce it either.

It can be noted that a (possible) issue on standard Ubuntu related to
how ibus-daemon is started is not an issue with ibus but rather with
gnome-shell.

Anyway, this is a bit odd:

$ env | grep -i type
XDG_SESSION_TYPE=x11
$ ps ux | grep ibus-daemon
gunnar  2932  0.0  0.0   2888   956 ?Ss   06:04   0:00 sh -c 
/usr/bin/ibus-daemon --panel disable $([[ $XDG_SESSION_TYPE == "x11" ]] && echo 
"--xim")
gunnar  2935  0.4  0.0 406192 14220 ?Sl   06:04   0:02 
/usr/bin/ibus-daemon --panel disable
gunnar  5761  0.0  0.0  24844  2632 pts/0S+   06:14   0:00 grep 
--color=auto ibus-daemon

OTOH I can't tell the significance of '--xim' not being included in the
second ibus-daemon process.

@Yuan-Chen Cheng: Well, if nobody — not even you — is able to reproduce
the issue on an upgraded jammy, the bug shouldn't be set to "Incomplete"
but rather be closed. So I closed it.

Please feel free to request it to be reopened or submit a new bug if the
issue reappears.

** Also affects: gnome-shell (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: gnome-shell (Ubuntu)
   Status: New => Invalid

** Changed in: ibus (Ubuntu)
   Status: Incomplete => 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/1966356

Title:
  ibus input method not working

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

Bug description:
  per test on jammy, config traditional Chinese and input method as ibus

  Chinese input method not working.

  Per check around, found that just force add "--xim" to /usr/bin/ibus-daemon,
  then it works.

  Note: per test, add --xim works for below cases:

  1. x11 mode
  2. Wayland mode, x11 client, test by using microsoft edge.
  3. Wayland mode, Wayland client, tested by using gnome-terminal.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1966356/+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 1965993] Re: Remove Ubuntu Pro settings

2022-03-23 Thread Gunnar Hjalmarsson
Sebastien subscribed me to this bug, but I'm not sure why. Robert has
already posted about it to the ubuntu-translators list. The feature is
not mentioned in Ubuntu Desktop Guide.

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

Title:
  Remove Ubuntu Pro settings

Status in software-properties package in Ubuntu:
  New

Bug description:
  Due to backend delay, we want to remove the Ubuntu Pro settings and
  only show Livepatch settings as were previously shown. This feature
  will be re-added at a future time.

  This change will rename the "Ubuntu Pro" page to "Livepatch" and hide various 
UI elements. This adds the following new strings for translations:
  "This machine is not covered by an Ubuntu Advantage subscription."
  "Ubuntu Advantage subscription attached."
  "Livepatch"

  All existing strings for the Ubuntu Pro settings remain, so should
  remain translated when this change is reverted.

  See below for screenshots of the change.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1965993/+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 1965609] Re: Not all Hunngarian keyboard layouts' name translated to Hungarian layout

2022-03-19 Thread Gunnar Hjalmarsson
Thanks for your report.

In xkeyboard-config the string representing the first of those layout
variants looks like this:

"Hungarian (101/QWERTY/comma/dead keys)"

And that string has a Hungarian translation:

https://translations.launchpad.net/ubuntu/jammy/+source/xkeyboard-
config/+pots/xkeyboard-config/hu/515

However, the gnome-control-center developers seem to think that commas
look better than slashes to separate the various aspects of the layout:

"Hungarian (QWERTY, 101-key, comma, dead keys)"

But by splitting and recreating the string that way, they end up with a
different string for which no translation exists. And that's most likely
the explanation for the other untranslated layout names as well. And
it's not only affecting users with a Hungarian locale — I see those
strings untranslated when using a Swedish locale, for instance.

So it's a bug in gnome-control-center.

@Viktor: It would be great if you could call upstream's attention to
this by submitting an issue:

https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues

If you do, can you please post the URL to the upstream issue here for
tracking purposes.

** Also affects: gnome-control-center (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: gnome-control-center (Ubuntu)
   Importance: Undecided => Medium

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Confirmed

** Changed in: xkeyboard-config (Ubuntu)
   Status: New => Invalid

** Summary changed:

- Not all Hunngarian keyboard layouts' name translated to Hungarian layout
+ Several Hungarian keyboard layout labels untranslated

-- 
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/1965609

Title:
  Several Hungarian keyboard layout labels untranslated

Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in xkeyboard-config package in Ubuntu:
  Invalid

Bug description:
  Wen I wanted to choose a Hungarian layout, I saw, that not all
  Hungarian layouts' name translated into Hungarian language.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1965609/+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 1965609] Re: Several Hungarian keyboard layout labels untranslated

2022-03-19 Thread Gunnar Hjalmarsson
(Possibly it's a bug in the gnome-desktop package. But let's report it
to gnome-control-center, and have upstream sort it.)

-- 
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/1965609

Title:
  Several Hungarian keyboard layout labels untranslated

Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in xkeyboard-config package in Ubuntu:
  Invalid

Bug description:
  Wen I wanted to choose a Hungarian layout, I saw, that not all
  Hungarian layouts' name translated into Hungarian language.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1965609/+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 1965610] Re: Extra layouts don't work on Hungarian UI

2022-03-19 Thread Gunnar Hjalmarsson
You should run that command without "sudo".

gsettings set org.gnome.desktop.input-sources show-all-sources true

** Package changed: xkeyboard-config (Ubuntu) => gnome-control-center
(Ubuntu)

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Invalid

-- 
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/1965610

Title:
  Extra layouts don't work on Hungarian UI

Status in gnome-control-center package in Ubuntu:
  Invalid

Bug description:
  When I set into a terminal the following command:
  "sudo gsettings set org.gnome.desktop.input-sources show-all-sources true"
  it fails.
  We required for "Old Hungarian" layout, short description:"oldhun" -> 
"Székely-magyar rovásírás" and "Old Hungarian (for ligatures)" layout, short 
description: "oldhun(lig)" id:"oldhunlig" ->"Székely-magyar rovásírás 
(ligatúrákhoz)"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1965610/+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 1895454] Re: ibus indicator is unreadable, and the dropdown doesn't clarify what option is selected

2022-03-15 Thread Gunnar Hjalmarsson
Change of default color included in ibus 1.5.26-2.

** Changed in: ibus (Ubuntu)
   Status: Fix Committed => 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/1895454

Title:
  ibus indicator is unreadable, and the dropdown doesn't clarify what
  option is selected

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

Bug description:
  I don't know exactly what iBus is and what it does, but it has this
  indicator on the bottom-right corner of the screen (whatever that area
  is called) which shows what the currently selected input language is,
  whatever that means. For example, on my system there are two choices
  available: "Spanish - Spanish" and "English - English (US)", and
  therefore the indicator shows either "ES" or "EN" depending on which
  one is selected. Whatever the effect of that is.

  The issue is, this indicator is designed with an idiotic choice of
  colours: a very dark blue text on a very dark gray background, which
  makes it mostly unreadable. I am not color blind nor visually
  impaired, yet both colors are almost undistinguishable to me, and it
  costs me a great effort to tell whether it says "EN" or "ES".

  Additionally, adding to the idiocy, if I click on it to see which one
  is actually selected, a dropdown unfolds where the two options are
  listed, and the currently selected one is not highlighted in any way!!
  It seems that the selected one is always shown first, which, assuming
  it's true, I can only learn by changing the selection back and forth,
  when it could have been as easy as showing the currently selected one
  in bold.

  It looks as if every single possible step had been purposefully taken
  to make this less useful, because even by doing it carelessly and
  without putting any thought into it, it's unlikely that it could turn
  out so ridiculously badly designed.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ibus 1.5.22-2ubuntu2.1
  ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
  Uname: Linux 5.4.0-47-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  Date: Sun Sep 13 15:38:34 2020
  InstallationDate: Installed on 2013-10-11 (2528 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: ibus
  UpgradeStatus: Upgraded to focal on 2020-07-12 (62 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ibus/+bug/1895454/+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 1964682] Re: IBus not starting properly at login to wayland with gnome-shell 42

2022-03-14 Thread Gunnar Hjalmarsson
systemd in Build-Depends seems to be it. Thanks Mitsuya and Jeremy!

Uploaded again and keeping my fingers crossed.

-- 
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/1964682

Title:
  IBus not starting properly at login to wayland with gnome-shell 42

Status in gnome-shell package in Ubuntu:
  Invalid
Status in ibus package in Ubuntu:
  In Progress

Bug description:
  To get to the state in the bug summary I did:

  1. Installed Ubuntu via the 220312 ISO

  2. Made sure that all packages were updated

  3. Installed ibus-libpinyin, re-logged in, and added "Intelligent
  Pinyin" to the input sources

  4. Enabled -proposed

  5. Run this command:
  sudo apt install gnome-shell gnome-shell-common gir1.2-mutter-10 
libmutter-10-0 mutter-common

  6. Rebooted

  Now, once logged in, gnome-shell does not include "Intelligent Pinyin"
  in the input source menu. Several expected processes are missing:

  $ ps aux | grep ibus
  gunnar  3057  0.0  0.0 232404  7984 ?Sl   20:05   0:00 
ibus-daemon --panel disable -r --xim
  gunnar  3076  0.0  0.0 157280  6228 ?Sl   20:05   0:00 
/usr/libexec/ibus-memconf
  gunnar  5117  0.0  0.0  24492  2776 pts/0S+   20:06   0:00 grep 
--color=auto ibus

  If I start ibus-setup it shows the attached dialog. From there I can
  click "Yes" and successfully start IBus that way, and then it works as
  expected.

  Note that im-config is not involved. Nowadays, on GNOME desktops, we
  rely completely on the GNOME mechanisms for starting and configuring
  IBus.

  One thought is that ibus upstream has not released since August 20.
  Can it possibly be that some unreleased upstream ibus commits are
  needed for gnome-shell 42?

  https://github.com/ibus/ibus/commits/master

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964682/+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 1964682] Re: IBus not starting properly at login to wayland with gnome-shell 42

2022-03-14 Thread Gunnar Hjalmarsson
Yeah, I too think it looks like bug fixes only.

But there is a problem: Salsa's pipeline shows a build failure:

https://salsa.debian.org/debian/ibus/-/pipelines/358170

But since I already had built successfully in a jammy PPA:

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

and also built successfully locally on Debian testing, I decided to take
a chance and uploaded anyway. Proved to not be very wise:

https://buildd.debian.org/status/package.php?p=ibus

I will need some help to figure out what the problem is.

(There is of course the option to upload it directly to Ubuntu as
-0ubuntu1 for now. But I feel it would be safer to make the build
succeed on Debian first so the Debian side gets involved.)

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

** Changed in: gnome-shell (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/1964682

Title:
  IBus not starting properly at login to wayland with gnome-shell 42

Status in gnome-shell package in Ubuntu:
  Invalid
Status in ibus package in Ubuntu:
  In Progress

Bug description:
  To get to the state in the bug summary I did:

  1. Installed Ubuntu via the 220312 ISO

  2. Made sure that all packages were updated

  3. Installed ibus-libpinyin, re-logged in, and added "Intelligent
  Pinyin" to the input sources

  4. Enabled -proposed

  5. Run this command:
  sudo apt install gnome-shell gnome-shell-common gir1.2-mutter-10 
libmutter-10-0 mutter-common

  6. Rebooted

  Now, once logged in, gnome-shell does not include "Intelligent Pinyin"
  in the input source menu. Several expected processes are missing:

  $ ps aux | grep ibus
  gunnar  3057  0.0  0.0 232404  7984 ?Sl   20:05   0:00 
ibus-daemon --panel disable -r --xim
  gunnar  3076  0.0  0.0 157280  6228 ?Sl   20:05   0:00 
/usr/libexec/ibus-memconf
  gunnar  5117  0.0  0.0  24492  2776 pts/0S+   20:06   0:00 grep 
--color=auto ibus

  If I start ibus-setup it shows the attached dialog. From there I can
  click "Yes" and successfully start IBus that way, and then it works as
  expected.

  Note that im-config is not involved. Nowadays, on GNOME desktops, we
  rely completely on the GNOME mechanisms for starting and configuring
  IBus.

  One thought is that ibus upstream has not released since August 20.
  Can it possibly be that some unreleased upstream ibus commits are
  needed for gnome-shell 42?

  https://github.com/ibus/ibus/commits/master

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964682/+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 1964682] Re: IBus not starting properly at login to wayland with gnome-shell 42

2022-03-14 Thread Gunnar Hjalmarsson
Upstream just released ibus 1.5.26. I tested it in jammy, and it proved
to solve this issue.

I'm about to upload to unstable. Maybe somebody can decide if it can be
considered a bug fix release which can be synced without a FFe request:

https://github.com/ibus/ibus/releases/tag/1.5.26

-- 
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/1964682

Title:
  IBus not starting properly at login to wayland with gnome-shell 42

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

Bug description:
  To get to the state in the bug summary I did:

  1. Installed Ubuntu via the 220312 ISO

  2. Made sure that all packages were updated

  3. Installed ibus-libpinyin, re-logged in, and added "Intelligent
  Pinyin" to the input sources

  4. Enabled -proposed

  5. Run this command:
  sudo apt install gnome-shell gnome-shell-common gir1.2-mutter-10 
libmutter-10-0 mutter-common

  6. Rebooted

  Now, once logged in, gnome-shell does not include "Intelligent Pinyin"
  in the input source menu. Several expected processes are missing:

  $ ps aux | grep ibus
  gunnar  3057  0.0  0.0 232404  7984 ?Sl   20:05   0:00 
ibus-daemon --panel disable -r --xim
  gunnar  3076  0.0  0.0 157280  6228 ?Sl   20:05   0:00 
/usr/libexec/ibus-memconf
  gunnar  5117  0.0  0.0  24492  2776 pts/0S+   20:06   0:00 grep 
--color=auto ibus

  If I start ibus-setup it shows the attached dialog. From there I can
  click "Yes" and successfully start IBus that way, and then it works as
  expected.

  Note that im-config is not involved. Nowadays, on GNOME desktops, we
  rely completely on the GNOME mechanisms for starting and configuring
  IBus.

  One thought is that ibus upstream has not released since August 20.
  Can it possibly be that some unreleased upstream ibus commits are
  needed for gnome-shell 42?

  https://github.com/ibus/ibus/commits/master

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964682/+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 1964682] Re: IBus not starting properly at login with gnome-shell 42

2022-03-13 Thread Gunnar Hjalmarsson
The issue only happens when logging in to a wayland session.

Also, I stumbled upon this upstream gtk issue:

https://gitlab.gnome.org/GNOME/gtk/-/issues/4699

Currently we install ibus-gtk4 by default (ibus recommends it), which is
my 'fault'. Assumed that it should be consistent with how ibus-gtk3 is
handled. Maybe not? OTOH, uninstalling ibus-gtk4 does not make a
difference with respect to the issue reported through this bug, so this
piece of info may be off topic here.

** Bug watch added: gitlab.gnome.org/GNOME/gtk/-/issues #4699
   https://gitlab.gnome.org/GNOME/gtk/-/issues/4699

** Tags added: wayland

** Summary changed:

- IBus not starting properly at login with gnome-shell 42
+ IBus not starting properly at login to wayland with gnome-shell 42

-- 
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/1964682

Title:
  IBus not starting properly at login to wayland with gnome-shell 42

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

Bug description:
  To get to the state in the bug summary I did:

  1. Installed Ubuntu via the 220312 ISO

  2. Made sure that all packages were updated

  3. Installed ibus-libpinyin, re-logged in, and added "Intelligent
  Pinyin" to the input sources

  4. Enabled -proposed

  5. Run this command:
  sudo apt install gnome-shell gnome-shell-common gir1.2-mutter-10 
libmutter-10-0 mutter-common

  6. Rebooted

  Now, once logged in, gnome-shell does not include "Intelligent Pinyin"
  in the input source menu. Several expected processes are missing:

  $ ps aux | grep ibus
  gunnar  3057  0.0  0.0 232404  7984 ?Sl   20:05   0:00 
ibus-daemon --panel disable -r --xim
  gunnar  3076  0.0  0.0 157280  6228 ?Sl   20:05   0:00 
/usr/libexec/ibus-memconf
  gunnar  5117  0.0  0.0  24492  2776 pts/0S+   20:06   0:00 grep 
--color=auto ibus

  If I start ibus-setup it shows the attached dialog. From there I can
  click "Yes" and successfully start IBus that way, and then it works as
  expected.

  Note that im-config is not involved. Nowadays, on GNOME desktops, we
  rely completely on the GNOME mechanisms for starting and configuring
  IBus.

  One thought is that ibus upstream has not released since August 20.
  Can it possibly be that some unreleased upstream ibus commits are
  needed for gnome-shell 42?

  https://github.com/ibus/ibus/commits/master

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964682/+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 1964682] Re: IBus not starting properly at login with gnome-shell 42

2022-03-12 Thread Gunnar Hjalmarsson
A no-change rebuild of ibus doesn't help.

-- 
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/1964682

Title:
  IBus not starting properly at login with gnome-shell 42

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

Bug description:
  To get to the state in the bug summary I did:

  1. Installed Ubuntu via the 220312 ISO

  2. Made sure that all packages were updated

  3. Installed ibus-libpinyin, re-logged in, and added "Intelligent
  Pinyin" to the input sources

  4. Enabled -proposed

  5. Run this command:
  sudo apt install gnome-shell gnome-shell-common gir1.2-mutter-10 
libmutter-10-0 mutter-common

  6. Rebooted

  Now, once logged in, gnome-shell does not include "Intelligent Pinyin"
  in the input source menu. Several expected processes are missing:

  $ ps aux | grep ibus
  gunnar  3057  0.0  0.0 232404  7984 ?Sl   20:05   0:00 
ibus-daemon --panel disable -r --xim
  gunnar  3076  0.0  0.0 157280  6228 ?Sl   20:05   0:00 
/usr/libexec/ibus-memconf
  gunnar  5117  0.0  0.0  24492  2776 pts/0S+   20:06   0:00 grep 
--color=auto ibus

  If I start ibus-setup it shows the attached dialog. From there I can
  click "Yes" and successfully start IBus that way, and then it works as
  expected.

  Note that im-config is not involved. Nowadays, on GNOME desktops, we
  rely completely on the GNOME mechanisms for starting and configuring
  IBus.

  One thought is that ibus upstream has not released since August 20.
  Can it possibly be that some unreleased upstream ibus commits are
  needed for gnome-shell 42?

  https://github.com/ibus/ibus/commits/master

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964682/+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 1964682] [NEW] IBus not starting properly at login with gnome-shell 42

2022-03-12 Thread Gunnar Hjalmarsson
Public bug reported:

To get to the state in the bug summary I did:

1. Installed Ubuntu via the 220312 ISO

2. Made sure that all packages were updated

3. Installed ibus-libpinyin, re-logged in, and added "Intelligent
Pinyin" to the input sources

4. Enabled -proposed

5. Run this command:
sudo apt install gnome-shell gnome-shell-common gir1.2-mutter-10 libmutter-10-0 
mutter-common

6. Rebooted

Now, once logged in, gnome-shell does not include "Intelligent Pinyin"
in the input source menu. Several expected processes are missing:

$ ps aux | grep ibus
gunnar  3057  0.0  0.0 232404  7984 ?Sl   20:05   0:00 ibus-daemon 
--panel disable -r --xim
gunnar  3076  0.0  0.0 157280  6228 ?Sl   20:05   0:00 
/usr/libexec/ibus-memconf
gunnar  5117  0.0  0.0  24492  2776 pts/0S+   20:06   0:00 grep 
--color=auto ibus

If I start ibus-setup it shows the attached dialog. From there I can
click "Yes" and successfully start IBus that way, and then it works as
expected.

Note that im-config is not involved. Nowadays, on GNOME desktops, we
rely completely on the GNOME mechanisms for starting and configuring
IBus.

One thought is that ibus upstream has not released since August 20. Can
it possibly be that some unreleased upstream ibus commits are needed for
gnome-shell 42?

https://github.com/ibus/ibus/commits/master

** Affects: gnome-shell (Ubuntu)
 Importance: High
 Status: New

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


** Tags: jammy rls-jj-incoming

** Attachment added: "ibus-setup_response.png"
   
https://bugs.launchpad.net/bugs/1964682/+attachment/5568298/+files/ibus-setup_response.png

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

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

-- 
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/1964682

Title:
  IBus not starting properly at login with gnome-shell 42

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

Bug description:
  To get to the state in the bug summary I did:

  1. Installed Ubuntu via the 220312 ISO

  2. Made sure that all packages were updated

  3. Installed ibus-libpinyin, re-logged in, and added "Intelligent
  Pinyin" to the input sources

  4. Enabled -proposed

  5. Run this command:
  sudo apt install gnome-shell gnome-shell-common gir1.2-mutter-10 
libmutter-10-0 mutter-common

  6. Rebooted

  Now, once logged in, gnome-shell does not include "Intelligent Pinyin"
  in the input source menu. Several expected processes are missing:

  $ ps aux | grep ibus
  gunnar  3057  0.0  0.0 232404  7984 ?Sl   20:05   0:00 
ibus-daemon --panel disable -r --xim
  gunnar  3076  0.0  0.0 157280  6228 ?Sl   20:05   0:00 
/usr/libexec/ibus-memconf
  gunnar  5117  0.0  0.0  24492  2776 pts/0S+   20:06   0:00 grep 
--color=auto ibus

  If I start ibus-setup it shows the attached dialog. From there I can
  click "Yes" and successfully start IBus that way, and then it works as
  expected.

  Note that im-config is not involved. Nowadays, on GNOME desktops, we
  rely completely on the GNOME mechanisms for starting and configuring
  IBus.

  One thought is that ibus upstream has not released since August 20.
  Can it possibly be that some unreleased upstream ibus commits are
  needed for gnome-shell 42?

  https://github.com/ibus/ibus/commits/master

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964682/+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 1895454] Re: ibus indicator is unreadable, and the dropdown doesn't clarify what option is selected

2022-01-31 Thread Gunnar Hjalmarsson
Color changed upstream:

https://github.com/ibus/ibus/commit/0e118e7e

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

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

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

-- 
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/1895454

Title:
  ibus indicator is unreadable, and the dropdown doesn't clarify what
  option is selected

Status in ibus:
  Unknown
Status in ibus package in Ubuntu:
  Fix Committed

Bug description:
  I don't know exactly what iBus is and what it does, but it has this
  indicator on the bottom-right corner of the screen (whatever that area
  is called) which shows what the currently selected input language is,
  whatever that means. For example, on my system there are two choices
  available: "Spanish - Spanish" and "English - English (US)", and
  therefore the indicator shows either "ES" or "EN" depending on which
  one is selected. Whatever the effect of that is.

  The issue is, this indicator is designed with an idiotic choice of
  colours: a very dark blue text on a very dark gray background, which
  makes it mostly unreadable. I am not color blind nor visually
  impaired, yet both colors are almost undistinguishable to me, and it
  costs me a great effort to tell whether it says "EN" or "ES".

  Additionally, adding to the idiocy, if I click on it to see which one
  is actually selected, a dropdown unfolds where the two options are
  listed, and the currently selected one is not highlighted in any way!!
  It seems that the selected one is always shown first, which, assuming
  it's true, I can only learn by changing the selection back and forth,
  when it could have been as easy as showing the currently selected one
  in bold.

  It looks as if every single possible step had been purposefully taken
  to make this less useful, because even by doing it carelessly and
  without putting any thought into it, it's unlikely that it could turn
  out so ridiculously badly designed.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ibus 1.5.22-2ubuntu2.1
  ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
  Uname: Linux 5.4.0-47-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  Date: Sun Sep 13 15:38:34 2020
  InstallationDate: Installed on 2013-10-11 (2528 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: ibus
  UpgradeStatus: Upgraded to focal on 2020-07-12 (62 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ibus/+bug/1895454/+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 1794869] Re: ibus-daemon crashed with SIGABRT in g_assertion_message_expr()

2022-01-19 Thread Gunnar Hjalmarsson
*** This bug is a duplicate of bug 1545811 ***
https://bugs.launchpad.net/bugs/1545811

The duplicate bug is old, and it's open now.

-- 
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/1794869

Title:
  ibus-daemon crashed with SIGABRT in g_assertion_message_expr()

Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  No

  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: ibus 1.5.19-1ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 27 15:35:04 2018
  ExecutablePath: /usr/bin/ibus-daemon
  InstallationDate: Installed on 2018-09-11 (15 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180908)
  ProcCmdline: ibus-daemon --xim --panel disable
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.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-daemon crashed with SIGABRT in g_assertion_message_expr()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1794869/+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 1545811] Re: ibus-daemon crashed with SIGABRT in g_assertion_message()

2022-01-19 Thread Gunnar Hjalmarsson
** Information type changed from Private to Public

-- 
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/1545811

Title:
  ibus-daemon crashed with SIGABRT in g_assertion_message()

Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  ubuntu 16.04 alpha. ibus-daemon crashed popped up after testing
  another bug

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: ibus 1.5.11-1ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-4.19-generic 4.4.1
  Uname: Linux 4.4.0-4-generic x86_64
  ApportVersion: 2.19.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Feb 15 18:57:55 2016
  ExecutablePath: /usr/bin/ibus-daemon
  InstallationDate: Installed on 2013-09-28 (870 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1)
  ProcCmdline: /usr/bin/ibus-daemon --daemonize --xim
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: ibus
  StacktraceTop:
   g_assertion_message () 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 /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: ibus-daemon crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: Upgraded to xenial on 2016-02-11 (4 days ago)
  UserGroups: adm cdrom dip disk fax lp lpadmin plugdev sambashare sudo 
vboxusers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1545811/+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 1955461] Re: ibus-x11 crashed with SIGSEGV in __pthread_kill_implementation()

2021-12-21 Thread Gunnar Hjalmarsson
** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1955461/+attachment/5548856/+files/CoreDump.gz

** Information type changed from Private to Public

-- 
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/1955461

Title:
  ibus-x11 crashed with SIGSEGV in __pthread_kill_implementation()

Status in ibus package in Ubuntu:
  New

Bug description:
  Nothing observed

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: ibus 1.5.25-3
  Uname: Linux 5.15.7-051507-generic x86_64
  ApportVersion: 2.20.11-0ubuntu74
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec 21 07:30:13 2021
  ExecutablePath: /usr/libexec/ibus-x11
  InstallationDate: Installed on 2021-12-10 (10 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211209)
  ProcCmdline: /usr/libexec/ibus-x11 --kill-daemon
  SegvAnalysis:
   Segfault happened at: 0x7f615926644c <__run_exit_handlers+108>:  mov
0x10(%r15,%rdx,1),%rcx
   PC (0x7f615926644c) ok
   source "0x10(%r15,%rdx,1)" (0x1041bf32f0b920) not located in a known VMA 
region (needed readable region)!
   destination "%rcx" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: ibus
  StacktraceTop:
   __pthread_kill_implementation (no_tid=0, signo=15, threadid=140056065796736) 
at pthread_kill.c:44
   __pthread_kill_internal (signo=15, threadid=140056065796736) at 
pthread_kill.c:80
   __GI___pthread_kill (threadid=140056065796736, signo=signo@entry=15) at 
pthread_kill.c:91
   __GI_raise (sig=15) at ../sysdeps/posix/raise.c:26
   ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: ibus-x11 crashed with SIGSEGV in __pthread_kill_implementation()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1955461/+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 1892825] Re: update-locale not perform correctly sanity checks

2021-12-13 Thread Gunnar Hjalmarsson
I verified the test case using locales 2.31-0ubuntu9.4 from focal-
proposed.

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

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

Title:
  update-locale not perform correctly sanity checks

Status in glibc package in Ubuntu:
  In Progress
Status in pam package in Ubuntu:
  New
Status in glibc source package in Bionic:
  New
Status in pam source package in Bionic:
  New
Status in glibc source package in Focal:
  Fix Committed
Status in pam source package in Focal:
  New
Status in glibc source package in Hirsute:
  New
Status in pam source package in Hirsute:
  New
Status in glibc source package in Impish:
  New
Status in pam source package in Impish:
  New

Bug description:
  [impact]
  A simple typo using the update-locale script can render a system inoperable 
without booting into single user mode or similar:

  $ sudo update-locale LANGUAGE = en_US.UTF-8
  $ sudo -s
  sudo: pam_open_session: Bad item passed to pam_*_item()
  sudo: policy plugin failed session initialization

  [test case]
  $ cp /etc/default/locale /tmp/locale
  $ update-locale --locale-file /tmp/locale LANGUAGE = en_US.UTF-8

  
  "diff -u /etc/default/locale /tmp/locale" should be empty.

  [original description]
  By passing wrong input as following:
   sudo update-locale LANGUAGE = en_US.UTF-8
  result is:
  ...
  #LANGUAGE=en
  =

  This "equal" sign that was added makes system completely
  unusable(can't run sudo anymore):

  bentzy@bentzy-nb:~$ sudo vim /etc/default/locale
  sudo: pam_open_session: Bad item passed to pam_*_item()
  sudo: policy plugin failed session initialization

  Fixed it booting from installation disk and fixing corrupted
  /etc/default/locale

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: locales 2.31-0ubuntu9
  Uname: Linux 5.5.4-050504-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Tue Aug 25 09:36:03 2020
  InstallationDate: Installed on 2020-08-17 (7 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: glibc
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1892825/+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 1892014] Re: 18.04.14.7 regression: no alt_shift_toggle in XKBOPTIONS

2021-11-20 Thread Gunnar Hjalmarsson
Ubiquity? That sounds more like bug #1875062.

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

Title:
  18.04.14.7 regression: no alt_shift_toggle in XKBOPTIONS

Status in console-setup package in Ubuntu:
  Confirmed
Status in ubiquity package in Ubuntu:
  Confirmed

Bug description:
  Up to ubuntu-mate-18.04.1.iso, everything was fine. Starting with
  18.04.2, XKB_OPTIONS does not contain "alt_shift_toggle" anymore and
  we cannot switch the keyboard layout to e.g. Greek using Alt+Shift.

  Reading the changelog, I see:

  $ ~/source/ubiquity$ git show 786a5325ef
  +console-setup (1.178ubuntu6) cosmic; urgency=medium
  +
  +  * keyboard-configuration.{config,templates}: There is no good default for
  +layout toggling, stop pretending there is.  Console users can set one
  +with dpkg-reconfigure or editing /etc/defaults/keyboard (LP: #1762952)

  I'm guessing that ubiquity duplicates some code from console-setup,
  and LP: #1762952 caused this regression.

  To reproduce:
  1) Start ubuntu-mate-18.04.1-desktop-amd64.iso
  2) Select Ελληνικά (Greek) and start installing Ubuntu using the default 
options
  3) Right after the keyboard layout step, run:
  $ grep XKBOPTIONS /etc/default/keyboard 
  XKBOPTIONS="grp:alt_shift_toggle,grp_led:scroll"
  4) Verify that you can switch to Greek with Alt+Shift

  Starting from ubuntu-mate-18.04.2-desktop-amd64.iso (.1=OK, .2=BAD), we 
cannot switch to Greek using Alt+Shift anymore:
  $ grep XKBOPTIONS /etc/default/keyboard 
  XKBOPTIONS="grp_led:scroll"

  Does ubiquity really expect the users to run `dpkg-reconfigure
  console-setup`?

  Note that selecting Greek in the syslinux menu produces the correct
  XKBOPTIONS, yet ubiquity overwrites them later on with the wrong ones.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1892014/+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 1950828] Re: ibus-daemon crashed with SIGABRT in g_mutex_clear().

2021-11-12 Thread Gunnar Hjalmarsson
** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1950828/+attachment/5540511/+files/CoreDump.gz

** Information type changed from Private to Public

-- 
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/1950828

Title:
  ibus-daemon crashed with SIGABRT in g_mutex_clear().

Status in ibus package in Ubuntu:
  New

Bug description:
  Bug report generated after logging in.  Nothing other then the log in
  was done.

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: ibus 1.5.25-2build1
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu73
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov 12 15:58:02 2021
  ExecutablePath: /usr/bin/ibus-daemon
  InstallationDate: Installed on 2021-10-27 (16 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211025)
  ProcCmdline: ibus-daemon --panel disable
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: ibus
  StacktraceTop:
   g_mutex_clear () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: ibus-daemon crashed with SIGABRT in g_mutex_clear()
  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/1950828/+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 1946499] Re: SRU: GDebi - installation of deb-packages with gdebi-gtk not working at all

2021-11-06 Thread Gunnar Hjalmarsson
For the record: Version 0.64.2-3 of vte2.91, without 91_keep_fds.patch,
has migrated to jammy.

** Also affects: vte2.91 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: vte2.91 (Ubuntu)
   Status: New => Fix Released

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

Title:
  SRU: GDebi - installation of deb-packages with gdebi-gtk not working
  at all

Status in gdebi package in Ubuntu:
  Fix Released
Status in vte2.91 package in Ubuntu:
  Fix Released
Status in gdebi source package in Impish:
  Fix Committed

Bug description:
  Steps to reproduce:
  1. Install Ubuntu MATE 21.10
  2. Open Firefox, navigate to discord.com
  3. Download deb-file. At time of writing from the 
https://dl.discordapp.net/apps/linux/0.0.16/discord-0.0.16.deb link
  4. Open Caja in ~/Downloads folder and use GDebi to install the 
discord-0.0.16.deb file
  5. In the GDebi window click Install button

  Expected results:
  * Gdebi quietly install discord package, there are no error messages in its 
terminal

  Actual results:
  * Gdebi terminal shows the error in the last line

  ```
  Selecting previously unselected package gconf2-common.
  (Reading database ... 457178 files and directories currently installed.)
  Preparing to unpack .../0-gconf2-common_3.2.6-7ubuntu2_all.deb ...
  Unpacking gconf2-common (3.2.6-7ubuntu2) ...
  Selecting previously unselected package libgconf-2-4:amd64.
  Preparing to unpack .../1-libgconf-2-4_3.2.6-7ubuntu2_amd64.deb ...
  Unpacking libgconf-2-4:amd64 (3.2.6-7ubuntu2) ...
  Selecting previously unselected package gconf-service-backend.
  Preparing to unpack .../2-gconf-service-backend_3.2.6-7ubuntu2_amd64.deb ...
  Unpacking gconf-service-backend (3.2.6-7ubuntu2) ...
  Selecting previously unselected package gconf-service.
  Preparing to unpack .../3-gconf-service_3.2.6-7ubuntu2_amd64.deb ...
  Unpacking gconf-service (3.2.6-7ubuntu2) ...
  Selecting previously unselected package libappindicator1.
  Preparing to unpack 
.../4-libappindicator1_12.10.1+20.10.20200706.1-0ubuntu1_amd64.deb ...
  Unpacking libappindicator1 (12.10.1+20.10.20200706.1-0ubuntu1) ...
  Selecting previously unselected package libunwind-13:amd64.
  Preparing to unpack .../5-libunwind-13_1%3a13.0.0-2_amd64.deb ...
  Unpacking libunwind-13:amd64 (1:13.0.0-2) ...
  Selecting previously unselected package libc++abi1-13:amd64.
  Preparing to unpack .../6-libc++abi1-13_1%3a13.0.0-2_amd64.deb ...
  Unpacking libc++abi1-13:amd64 (1:13.0.0-2) ...
  Selecting previously unselected package libc++1-13:amd64.
  Preparing to unpack .../7-libc++1-13_1%3a13.0.0-2_amd64.deb ...
  Unpacking libc++1-13:amd64 (1:13.0.0-2) ...
  Selecting previously unselected package libc++1:amd64.
  Preparing to unpack .../8-libc++1_1%3a13.0-53~exp1_amd64.deb ...
  Unpacking libc++1:amd64 (1:13.0-53~exp1) ...
  Setting up libappindicator1 (12.10.1+20.10.20200706.1-0ubuntu1) ...
  Setting up gconf2-common (3.2.6-7ubuntu2) ...

  Creating config file /etc/gconf/2/path with new version
  Setting up libunwind-13:amd64 (1:13.0.0-2) ...
  Setting up libc++abi1-13:amd64 (1:13.0.0-2) ...
  Setting up libc++1-13:amd64 (1:13.0.0-2) ...
  Setting up libc++1:amd64 (1:13.0-53~exp1) ...
  Setting up gconf-service (3.2.6-7ubuntu2) ...
  Processing triggers for libc-bin (2.34-0ubuntu2) ...
  Processing triggers for sgml-base (1.30) ...
  Setting up libgconf-2-4:amd64 (3.2.6-7ubuntu2) ...
  Setting up gconf-service-backend (3.2.6-7ubuntu2) ...
  Processing triggers for libc-bin (2.34-0ubuntu2) ...
  dpkg: error: unable to read filedescriptor flags for : Bad file descriptor
  ```

  and as the result Discord package is not installed .

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gdebi 0.9.5.7+nmu5ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  Date: Fri Oct  8 18:17:36 2021
  InstallationDate: Installed on 2021-10-08 (0 days ago)
  InstallationMedia: Ubuntu-MATE 21.10 "Impish Indri" - Daily amd64 (20211008)
  PackageArchitecture: all
  SourcePackage: gdebi
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2021-10-08T15:41:41.001986

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1946499/+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 1946499] Re: installation of deb-packages with gdebi-gtk shows "dpkg: error: unable to read filedescriptor flags for : Bad file descr

2021-10-20 Thread Gunnar Hjalmarsson
On 2021-10-20 22:58, Dani Llewellyn wrote:
> There are zero changes made to the strings themselves, only the line
> numbers used to generate the templates changed.

Thanks for explaining. Apparently I didn't look close enough. :/

Then I suppose we'd better use your small debdiff also for impish (once
the bug description has been updated).

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

Title:
  installation of deb-packages with gdebi-gtk shows "dpkg: error: unable
  to read filedescriptor flags for : Bad file descriptor" in gdebi terminal, package is not
  installed

Status in Ubuntu MATE:
  Invalid
Status in gdebi package in Ubuntu:
  Fix Released
Status in vte2.91 package in Ubuntu:
  Confirmed
Status in gdebi source package in Impish:
  Triaged

Bug description:
  Steps to reproduce:
  1. Install Ubuntu MATE 21.10
  2. Open Firefox, navigate to discord.com
  3. Download deb-file. At time of writing from the 
https://dl.discordapp.net/apps/linux/0.0.16/discord-0.0.16.deb link
  4. Open Caja in ~/Downloads folder and use GDebi to install the 
discord-0.0.16.deb file
  5. In the GDebi window click Install button

  Expected results:
  * Gdebi quietly install discord package, there are no error messages in its 
terminal

  Actual results:
  * Gdebi terminal shows the error in the last line

  ```
  Selecting previously unselected package gconf2-common.
  (Reading database ... 457178 files and directories currently installed.)
  Preparing to unpack .../0-gconf2-common_3.2.6-7ubuntu2_all.deb ...
  Unpacking gconf2-common (3.2.6-7ubuntu2) ...
  Selecting previously unselected package libgconf-2-4:amd64.
  Preparing to unpack .../1-libgconf-2-4_3.2.6-7ubuntu2_amd64.deb ...
  Unpacking libgconf-2-4:amd64 (3.2.6-7ubuntu2) ...
  Selecting previously unselected package gconf-service-backend.
  Preparing to unpack .../2-gconf-service-backend_3.2.6-7ubuntu2_amd64.deb ...
  Unpacking gconf-service-backend (3.2.6-7ubuntu2) ...
  Selecting previously unselected package gconf-service.
  Preparing to unpack .../3-gconf-service_3.2.6-7ubuntu2_amd64.deb ...
  Unpacking gconf-service (3.2.6-7ubuntu2) ...
  Selecting previously unselected package libappindicator1.
  Preparing to unpack 
.../4-libappindicator1_12.10.1+20.10.20200706.1-0ubuntu1_amd64.deb ...
  Unpacking libappindicator1 (12.10.1+20.10.20200706.1-0ubuntu1) ...
  Selecting previously unselected package libunwind-13:amd64.
  Preparing to unpack .../5-libunwind-13_1%3a13.0.0-2_amd64.deb ...
  Unpacking libunwind-13:amd64 (1:13.0.0-2) ...
  Selecting previously unselected package libc++abi1-13:amd64.
  Preparing to unpack .../6-libc++abi1-13_1%3a13.0.0-2_amd64.deb ...
  Unpacking libc++abi1-13:amd64 (1:13.0.0-2) ...
  Selecting previously unselected package libc++1-13:amd64.
  Preparing to unpack .../7-libc++1-13_1%3a13.0.0-2_amd64.deb ...
  Unpacking libc++1-13:amd64 (1:13.0.0-2) ...
  Selecting previously unselected package libc++1:amd64.
  Preparing to unpack .../8-libc++1_1%3a13.0-53~exp1_amd64.deb ...
  Unpacking libc++1:amd64 (1:13.0-53~exp1) ...
  Setting up libappindicator1 (12.10.1+20.10.20200706.1-0ubuntu1) ...
  Setting up gconf2-common (3.2.6-7ubuntu2) ...

  Creating config file /etc/gconf/2/path with new version
  Setting up libunwind-13:amd64 (1:13.0.0-2) ...
  Setting up libc++abi1-13:amd64 (1:13.0.0-2) ...
  Setting up libc++1-13:amd64 (1:13.0.0-2) ...
  Setting up libc++1:amd64 (1:13.0-53~exp1) ...
  Setting up gconf-service (3.2.6-7ubuntu2) ...
  Processing triggers for libc-bin (2.34-0ubuntu2) ...
  Processing triggers for sgml-base (1.30) ...
  Setting up libgconf-2-4:amd64 (3.2.6-7ubuntu2) ...
  Setting up gconf-service-backend (3.2.6-7ubuntu2) ...
  Processing triggers for libc-bin (2.34-0ubuntu2) ...
  dpkg: error: unable to read filedescriptor flags for : Bad file descriptor
  ```

  and as the result Discord package is not installed .

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gdebi 0.9.5.7+nmu5ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  Date: Fri Oct  8 18:17:36 2021
  InstallationDate: Installed on 2021-10-08 (0 days ago)
  InstallationMedia: Ubuntu-MATE 21.10 "Impish Indri" - Daily amd64 (20211008)
  PackageArchitecture: all
  SourcePackage: gdebi
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2021-10-08T15:41:41.001986

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


-- 
Mailing list: 

[Touch-packages] [Bug 1926912] Re: 21.10 Impish gdebi Programm fehlt Paket?

2021-10-20 Thread Gunnar Hjalmarsson
*** This bug is a duplicate of bug 1926697 ***
https://bugs.launchpad.net/bugs/1926697

** This bug has been marked a duplicate of bug 1926697
   gdebi-gtk does not start w msg 'Download failed'

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

Title:
  21.10 Impish gdebi Programm fehlt Paket?

Status in gdebi package in Ubuntu:
  New

Bug description:
  Hallo
  Programm gdebi fehlen Pakete?
  Sieh Bild
  Gruß

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1926912/+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 1946499] Re: installation of deb-packages with gdebi-gtk shows "dpkg: error: unable to read filedescriptor flags for : Bad file descr

2021-10-20 Thread Gunnar Hjalmarsson
It looks like also bug #1926697 is coincidentally about to be fixed
through the fix of this bug.

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

Title:
  installation of deb-packages with gdebi-gtk shows "dpkg: error: unable
  to read filedescriptor flags for : Bad file descriptor" in gdebi terminal, package is not
  installed

Status in Ubuntu MATE:
  Invalid
Status in gdebi package in Ubuntu:
  Fix Released
Status in vte2.91 package in Ubuntu:
  Confirmed
Status in gdebi source package in Impish:
  Triaged

Bug description:
  Steps to reproduce:
  1. Install Ubuntu MATE 21.10
  2. Open Firefox, navigate to discord.com
  3. Download deb-file. At time of writing from the 
https://dl.discordapp.net/apps/linux/0.0.16/discord-0.0.16.deb link
  4. Open Caja in ~/Downloads folder and use GDebi to install the 
discord-0.0.16.deb file
  5. In the GDebi window click Install button

  Expected results:
  * Gdebi quietly install discord package, there are no error messages in its 
terminal

  Actual results:
  * Gdebi terminal shows the error in the last line

  ```
  Selecting previously unselected package gconf2-common.
  (Reading database ... 457178 files and directories currently installed.)
  Preparing to unpack .../0-gconf2-common_3.2.6-7ubuntu2_all.deb ...
  Unpacking gconf2-common (3.2.6-7ubuntu2) ...
  Selecting previously unselected package libgconf-2-4:amd64.
  Preparing to unpack .../1-libgconf-2-4_3.2.6-7ubuntu2_amd64.deb ...
  Unpacking libgconf-2-4:amd64 (3.2.6-7ubuntu2) ...
  Selecting previously unselected package gconf-service-backend.
  Preparing to unpack .../2-gconf-service-backend_3.2.6-7ubuntu2_amd64.deb ...
  Unpacking gconf-service-backend (3.2.6-7ubuntu2) ...
  Selecting previously unselected package gconf-service.
  Preparing to unpack .../3-gconf-service_3.2.6-7ubuntu2_amd64.deb ...
  Unpacking gconf-service (3.2.6-7ubuntu2) ...
  Selecting previously unselected package libappindicator1.
  Preparing to unpack 
.../4-libappindicator1_12.10.1+20.10.20200706.1-0ubuntu1_amd64.deb ...
  Unpacking libappindicator1 (12.10.1+20.10.20200706.1-0ubuntu1) ...
  Selecting previously unselected package libunwind-13:amd64.
  Preparing to unpack .../5-libunwind-13_1%3a13.0.0-2_amd64.deb ...
  Unpacking libunwind-13:amd64 (1:13.0.0-2) ...
  Selecting previously unselected package libc++abi1-13:amd64.
  Preparing to unpack .../6-libc++abi1-13_1%3a13.0.0-2_amd64.deb ...
  Unpacking libc++abi1-13:amd64 (1:13.0.0-2) ...
  Selecting previously unselected package libc++1-13:amd64.
  Preparing to unpack .../7-libc++1-13_1%3a13.0.0-2_amd64.deb ...
  Unpacking libc++1-13:amd64 (1:13.0.0-2) ...
  Selecting previously unselected package libc++1:amd64.
  Preparing to unpack .../8-libc++1_1%3a13.0-53~exp1_amd64.deb ...
  Unpacking libc++1:amd64 (1:13.0-53~exp1) ...
  Setting up libappindicator1 (12.10.1+20.10.20200706.1-0ubuntu1) ...
  Setting up gconf2-common (3.2.6-7ubuntu2) ...

  Creating config file /etc/gconf/2/path with new version
  Setting up libunwind-13:amd64 (1:13.0.0-2) ...
  Setting up libc++abi1-13:amd64 (1:13.0.0-2) ...
  Setting up libc++1-13:amd64 (1:13.0.0-2) ...
  Setting up libc++1:amd64 (1:13.0-53~exp1) ...
  Setting up gconf-service (3.2.6-7ubuntu2) ...
  Processing triggers for libc-bin (2.34-0ubuntu2) ...
  Processing triggers for sgml-base (1.30) ...
  Setting up libgconf-2-4:amd64 (3.2.6-7ubuntu2) ...
  Setting up gconf-service-backend (3.2.6-7ubuntu2) ...
  Processing triggers for libc-bin (2.34-0ubuntu2) ...
  dpkg: error: unable to read filedescriptor flags for : Bad file descriptor
  ```

  and as the result Discord package is not installed .

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gdebi 0.9.5.7+nmu5ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  Date: Fri Oct  8 18:17:36 2021
  InstallationDate: Installed on 2021-10-08 (0 days ago)
  InstallationMedia: Ubuntu-MATE 21.10 "Impish Indri" - Daily amd64 (20211008)
  PackageArchitecture: all
  SourcePackage: gdebi
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2021-10-08T15:41:41.001986

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1946499/+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 1926697] Re: gdebi does not start w msg 'Download failed'

2021-10-20 Thread Gunnar Hjalmarsson
I can confirm this bug in 21.04. However, I think it's about to be
coincidentally fixed through the solution to bug #1946499. At least I
can successfully open gdebi-gtk in jammy (without passing a .deb file as
argument), and if the SRU of the other bug gets completed it ought to be
fixed in 21.10 as well.

So since I believe it's fixed in jammy I mark this bug "Fix Released".

@corrado: Please add a comment if you disagree on my conclusion, and
I'll re-open the bug.

** Summary changed:

- gdebi does not start w msg 'Download failed'
+ gdebi-gtk does not start w msg 'Download failed'

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

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

Title:
  gdebi-gtk does not start w msg 'Download failed'

Status in gdebi package in Ubuntu:
  Fix Released

Bug description:
  Just click on gdebi icon on dash.
  problem occurs in both xorg and wayland sessions

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gdebi 0.9.5.7+nmu4
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 30 08:15:15 2021
  ExecutablePath: /usr/share/gdebi/gdebi-gtk
  InstallationDate: Installed on 2021-04-23 (6 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  InterpreterPath: /usr/bin/python3.9
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.9, Python 3.9.4, python3-minimal, 3.9.4-1
  PythonDetails: N/A
  SourcePackage: gdebi
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1926697/+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 1946499] Re: installation of deb-packages with gdebi-gtk shows "dpkg: error: unable to read filedescriptor flags for : Bad file descr

2021-10-20 Thread Gunnar Hjalmarsson
My understanding is that it was intended for impish as well. If so, can
somebody (@Norbert, @Martin, anyone...) please edit the bug description
to comply with the SRU template:

https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template

Another thing: When uploading to Debian, I picked Dani's small debdiff,
i.e. the one without translation changes. gdebi is a universe package
which is normally sync'ed from Debian, so we should avoid to struggle
with translations in an Ubuntu specific upload.

@Dani: From where did you pick the translation changes in your first
bigger debdiff? I'd say that if there are additional translations
available, they'd better be added to the Debian version of gdebi.

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

Title:
  installation of deb-packages with gdebi-gtk shows "dpkg: error: unable
  to read filedescriptor flags for : Bad file descriptor" in gdebi terminal, package is not
  installed

Status in Ubuntu MATE:
  Invalid
Status in gdebi package in Ubuntu:
  Fix Released
Status in vte2.91 package in Ubuntu:
  Confirmed
Status in gdebi source package in Impish:
  Triaged

Bug description:
  Steps to reproduce:
  1. Install Ubuntu MATE 21.10
  2. Open Firefox, navigate to discord.com
  3. Download deb-file. At time of writing from the 
https://dl.discordapp.net/apps/linux/0.0.16/discord-0.0.16.deb link
  4. Open Caja in ~/Downloads folder and use GDebi to install the 
discord-0.0.16.deb file
  5. In the GDebi window click Install button

  Expected results:
  * Gdebi quietly install discord package, there are no error messages in its 
terminal

  Actual results:
  * Gdebi terminal shows the error in the last line

  ```
  Selecting previously unselected package gconf2-common.
  (Reading database ... 457178 files and directories currently installed.)
  Preparing to unpack .../0-gconf2-common_3.2.6-7ubuntu2_all.deb ...
  Unpacking gconf2-common (3.2.6-7ubuntu2) ...
  Selecting previously unselected package libgconf-2-4:amd64.
  Preparing to unpack .../1-libgconf-2-4_3.2.6-7ubuntu2_amd64.deb ...
  Unpacking libgconf-2-4:amd64 (3.2.6-7ubuntu2) ...
  Selecting previously unselected package gconf-service-backend.
  Preparing to unpack .../2-gconf-service-backend_3.2.6-7ubuntu2_amd64.deb ...
  Unpacking gconf-service-backend (3.2.6-7ubuntu2) ...
  Selecting previously unselected package gconf-service.
  Preparing to unpack .../3-gconf-service_3.2.6-7ubuntu2_amd64.deb ...
  Unpacking gconf-service (3.2.6-7ubuntu2) ...
  Selecting previously unselected package libappindicator1.
  Preparing to unpack 
.../4-libappindicator1_12.10.1+20.10.20200706.1-0ubuntu1_amd64.deb ...
  Unpacking libappindicator1 (12.10.1+20.10.20200706.1-0ubuntu1) ...
  Selecting previously unselected package libunwind-13:amd64.
  Preparing to unpack .../5-libunwind-13_1%3a13.0.0-2_amd64.deb ...
  Unpacking libunwind-13:amd64 (1:13.0.0-2) ...
  Selecting previously unselected package libc++abi1-13:amd64.
  Preparing to unpack .../6-libc++abi1-13_1%3a13.0.0-2_amd64.deb ...
  Unpacking libc++abi1-13:amd64 (1:13.0.0-2) ...
  Selecting previously unselected package libc++1-13:amd64.
  Preparing to unpack .../7-libc++1-13_1%3a13.0.0-2_amd64.deb ...
  Unpacking libc++1-13:amd64 (1:13.0.0-2) ...
  Selecting previously unselected package libc++1:amd64.
  Preparing to unpack .../8-libc++1_1%3a13.0-53~exp1_amd64.deb ...
  Unpacking libc++1:amd64 (1:13.0-53~exp1) ...
  Setting up libappindicator1 (12.10.1+20.10.20200706.1-0ubuntu1) ...
  Setting up gconf2-common (3.2.6-7ubuntu2) ...

  Creating config file /etc/gconf/2/path with new version
  Setting up libunwind-13:amd64 (1:13.0.0-2) ...
  Setting up libc++abi1-13:amd64 (1:13.0.0-2) ...
  Setting up libc++1-13:amd64 (1:13.0.0-2) ...
  Setting up libc++1:amd64 (1:13.0-53~exp1) ...
  Setting up gconf-service (3.2.6-7ubuntu2) ...
  Processing triggers for libc-bin (2.34-0ubuntu2) ...
  Processing triggers for sgml-base (1.30) ...
  Setting up libgconf-2-4:amd64 (3.2.6-7ubuntu2) ...
  Setting up gconf-service-backend (3.2.6-7ubuntu2) ...
  Processing triggers for libc-bin (2.34-0ubuntu2) ...
  dpkg: error: unable to read filedescriptor flags for : Bad file descriptor
  ```

  and as the result Discord package is not installed .

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gdebi 0.9.5.7+nmu5ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  Date: Fri Oct  8 18:17:36 2021
  InstallationDate: Installed on 2021-10-08 (0 days ago)
  InstallationMedia: Ubuntu-MATE 21.10 "Impish Indri" - Daily amd64 (20211008)
  PackageArchitecture: all
  SourcePackage: gdebi
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.apport:
   # set 

[Touch-packages] [Bug 1946499] Re: installation of deb-packages with gdebi-gtk shows "dpkg: error: unable to read filedescriptor flags for : Bad file descr

2021-10-19 Thread Gunnar Hjalmarsson
@Nikola: If that issue happened also in 21.04, it's not the same issue
as the one dealt with in this bug report. The latter is about a
regression due to an upgrade of vte2.91.

So you may want to submit a new bug report (with more details, exact
error messages, etc.).

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

Title:
  installation of deb-packages with gdebi-gtk shows "dpkg: error: unable
  to read filedescriptor flags for : Bad file descriptor" in gdebi terminal, package is not
  installed

Status in Ubuntu MATE:
  Invalid
Status in gdebi package in Ubuntu:
  Fix Released
Status in vte2.91 package in Ubuntu:
  Confirmed
Status in gdebi source package in Impish:
  Triaged

Bug description:
  Steps to reproduce:
  1. Install Ubuntu MATE 21.10
  2. Open Firefox, navigate to discord.com
  3. Download deb-file. At time of writing from the 
https://dl.discordapp.net/apps/linux/0.0.16/discord-0.0.16.deb link
  4. Open Caja in ~/Downloads folder and use GDebi to install the 
discord-0.0.16.deb file
  5. In the GDebi window click Install button

  Expected results:
  * Gdebi quietly install discord package, there are no error messages in its 
terminal

  Actual results:
  * Gdebi terminal shows the error in the last line

  ```
  Selecting previously unselected package gconf2-common.
  (Reading database ... 457178 files and directories currently installed.)
  Preparing to unpack .../0-gconf2-common_3.2.6-7ubuntu2_all.deb ...
  Unpacking gconf2-common (3.2.6-7ubuntu2) ...
  Selecting previously unselected package libgconf-2-4:amd64.
  Preparing to unpack .../1-libgconf-2-4_3.2.6-7ubuntu2_amd64.deb ...
  Unpacking libgconf-2-4:amd64 (3.2.6-7ubuntu2) ...
  Selecting previously unselected package gconf-service-backend.
  Preparing to unpack .../2-gconf-service-backend_3.2.6-7ubuntu2_amd64.deb ...
  Unpacking gconf-service-backend (3.2.6-7ubuntu2) ...
  Selecting previously unselected package gconf-service.
  Preparing to unpack .../3-gconf-service_3.2.6-7ubuntu2_amd64.deb ...
  Unpacking gconf-service (3.2.6-7ubuntu2) ...
  Selecting previously unselected package libappindicator1.
  Preparing to unpack 
.../4-libappindicator1_12.10.1+20.10.20200706.1-0ubuntu1_amd64.deb ...
  Unpacking libappindicator1 (12.10.1+20.10.20200706.1-0ubuntu1) ...
  Selecting previously unselected package libunwind-13:amd64.
  Preparing to unpack .../5-libunwind-13_1%3a13.0.0-2_amd64.deb ...
  Unpacking libunwind-13:amd64 (1:13.0.0-2) ...
  Selecting previously unselected package libc++abi1-13:amd64.
  Preparing to unpack .../6-libc++abi1-13_1%3a13.0.0-2_amd64.deb ...
  Unpacking libc++abi1-13:amd64 (1:13.0.0-2) ...
  Selecting previously unselected package libc++1-13:amd64.
  Preparing to unpack .../7-libc++1-13_1%3a13.0.0-2_amd64.deb ...
  Unpacking libc++1-13:amd64 (1:13.0.0-2) ...
  Selecting previously unselected package libc++1:amd64.
  Preparing to unpack .../8-libc++1_1%3a13.0-53~exp1_amd64.deb ...
  Unpacking libc++1:amd64 (1:13.0-53~exp1) ...
  Setting up libappindicator1 (12.10.1+20.10.20200706.1-0ubuntu1) ...
  Setting up gconf2-common (3.2.6-7ubuntu2) ...

  Creating config file /etc/gconf/2/path with new version
  Setting up libunwind-13:amd64 (1:13.0.0-2) ...
  Setting up libc++abi1-13:amd64 (1:13.0.0-2) ...
  Setting up libc++1-13:amd64 (1:13.0.0-2) ...
  Setting up libc++1:amd64 (1:13.0-53~exp1) ...
  Setting up gconf-service (3.2.6-7ubuntu2) ...
  Processing triggers for libc-bin (2.34-0ubuntu2) ...
  Processing triggers for sgml-base (1.30) ...
  Setting up libgconf-2-4:amd64 (3.2.6-7ubuntu2) ...
  Setting up gconf-service-backend (3.2.6-7ubuntu2) ...
  Processing triggers for libc-bin (2.34-0ubuntu2) ...
  dpkg: error: unable to read filedescriptor flags for : Bad file descriptor
  ```

  and as the result Discord package is not installed .

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gdebi 0.9.5.7+nmu5ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  Date: Fri Oct  8 18:17:36 2021
  InstallationDate: Installed on 2021-10-08 (0 days ago)
  InstallationMedia: Ubuntu-MATE 21.10 "Impish Indri" - Daily amd64 (20211008)
  PackageArchitecture: all
  SourcePackage: gdebi
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2021-10-08T15:41:41.001986

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


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

[Touch-packages] [Bug 1892825] Re: update-locale not perform correctly sanity checks

2021-10-18 Thread Gunnar Hjalmarsson
@Michael: I could easily reproduce the issue at the time (a year ago).

Good that it's about to be fixed. As you can see in comment #2 I first
turned to Debian, but the response was a bit disappointing. Any chance
that you can handle this on the Debian side too?

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

Title:
  update-locale not perform correctly sanity checks

Status in glibc package in Ubuntu:
  In Progress
Status in pam package in Ubuntu:
  New

Bug description:
  By passing wrong input as following:
   sudo update-locale LANGUAGE = en_US.UTF-8
  result is:
  ...
  #LANGUAGE=en
  =

  This "equal" sign that was added makes system completely
  unusable(can't run sudo anymore):

  bentzy@bentzy-nb:~$ sudo vim /etc/default/locale 
  sudo: pam_open_session: Bad item passed to pam_*_item()
  sudo: policy plugin failed session initialization

  Fixed it booting from installation disk and fixing corrupted
  /etc/default/locale

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: locales 2.31-0ubuntu9
  Uname: Linux 5.5.4-050504-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Tue Aug 25 09:36:03 2020
  InstallationDate: Installed on 2020-08-17 (7 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: glibc
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1892825/+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 1946499] Re: installation of deb-packages with gdebi-gtk shows "dpkg: error: unable to read filedescriptor flags for : Bad file descr

2021-10-14 Thread Gunnar Hjalmarsson
I just uploaded Dani's gdebi fix to Debian unstable. Tested it in a PPA
first:

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

With that, and for impish+1, we will be able to sync the source from
Debian for both gdebi and vte2.91.

The gdebi change must of course be SRUed to impish. As regards the now
obsolete VTE patch, and assuming that it doesn't hurt, SRUing vte2.91 is
probably not needed.

** Also affects: gdebi (Ubuntu Impish)
   Importance: High
   Status: Fix Committed

** Also affects: vte2.91 (Ubuntu Impish)
   Importance: Undecided
   Status: Confirmed

** No longer affects: vte2.91 (Ubuntu Impish)

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

Title:
  installation of deb-packages with gdebi-gtk shows "dpkg: error: unable
  to read filedescriptor flags for : Bad file descriptor" in gdebi terminal, package is not
  installed

Status in Ubuntu MATE:
  Invalid
Status in gdebi package in Ubuntu:
  Fix Committed
Status in vte2.91 package in Ubuntu:
  Confirmed
Status in gdebi source package in Impish:
  Fix Committed

Bug description:
  Steps to reproduce:
  1. Install Ubuntu MATE 21.10
  2. Open Firefox, navigate to discord.com
  3. Download deb-file. At time of writing from the 
https://dl.discordapp.net/apps/linux/0.0.16/discord-0.0.16.deb link
  4. Open Caja in ~/Downloads folder and use GDebi to install the 
discord-0.0.16.deb file
  5. In the GDebi window click Install button

  Expected results:
  * Gdebi quietly install discord package, there are no error messages in its 
terminal

  Actual results:
  * Gdebi terminal shows the error in the last line

  ```
  Selecting previously unselected package gconf2-common.
  (Reading database ... 457178 files and directories currently installed.)
  Preparing to unpack .../0-gconf2-common_3.2.6-7ubuntu2_all.deb ...
  Unpacking gconf2-common (3.2.6-7ubuntu2) ...
  Selecting previously unselected package libgconf-2-4:amd64.
  Preparing to unpack .../1-libgconf-2-4_3.2.6-7ubuntu2_amd64.deb ...
  Unpacking libgconf-2-4:amd64 (3.2.6-7ubuntu2) ...
  Selecting previously unselected package gconf-service-backend.
  Preparing to unpack .../2-gconf-service-backend_3.2.6-7ubuntu2_amd64.deb ...
  Unpacking gconf-service-backend (3.2.6-7ubuntu2) ...
  Selecting previously unselected package gconf-service.
  Preparing to unpack .../3-gconf-service_3.2.6-7ubuntu2_amd64.deb ...
  Unpacking gconf-service (3.2.6-7ubuntu2) ...
  Selecting previously unselected package libappindicator1.
  Preparing to unpack 
.../4-libappindicator1_12.10.1+20.10.20200706.1-0ubuntu1_amd64.deb ...
  Unpacking libappindicator1 (12.10.1+20.10.20200706.1-0ubuntu1) ...
  Selecting previously unselected package libunwind-13:amd64.
  Preparing to unpack .../5-libunwind-13_1%3a13.0.0-2_amd64.deb ...
  Unpacking libunwind-13:amd64 (1:13.0.0-2) ...
  Selecting previously unselected package libc++abi1-13:amd64.
  Preparing to unpack .../6-libc++abi1-13_1%3a13.0.0-2_amd64.deb ...
  Unpacking libc++abi1-13:amd64 (1:13.0.0-2) ...
  Selecting previously unselected package libc++1-13:amd64.
  Preparing to unpack .../7-libc++1-13_1%3a13.0.0-2_amd64.deb ...
  Unpacking libc++1-13:amd64 (1:13.0.0-2) ...
  Selecting previously unselected package libc++1:amd64.
  Preparing to unpack .../8-libc++1_1%3a13.0-53~exp1_amd64.deb ...
  Unpacking libc++1:amd64 (1:13.0-53~exp1) ...
  Setting up libappindicator1 (12.10.1+20.10.20200706.1-0ubuntu1) ...
  Setting up gconf2-common (3.2.6-7ubuntu2) ...

  Creating config file /etc/gconf/2/path with new version
  Setting up libunwind-13:amd64 (1:13.0.0-2) ...
  Setting up libc++abi1-13:amd64 (1:13.0.0-2) ...
  Setting up libc++1-13:amd64 (1:13.0.0-2) ...
  Setting up libc++1:amd64 (1:13.0-53~exp1) ...
  Setting up gconf-service (3.2.6-7ubuntu2) ...
  Processing triggers for libc-bin (2.34-0ubuntu2) ...
  Processing triggers for sgml-base (1.30) ...
  Setting up libgconf-2-4:amd64 (3.2.6-7ubuntu2) ...
  Setting up gconf-service-backend (3.2.6-7ubuntu2) ...
  Processing triggers for libc-bin (2.34-0ubuntu2) ...
  dpkg: error: unable to read filedescriptor flags for : Bad file descriptor
  ```

  and as the result Discord package is not installed .

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gdebi 0.9.5.7+nmu5ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  Date: Fri Oct  8 18:17:36 2021
  InstallationDate: Installed on 2021-10-08 (0 days ago)
  InstallationMedia: Ubuntu-MATE 21.10 "Impish Indri" - Daily amd64 (20211008)
  PackageArchitecture: all
  SourcePackage: gdebi
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # 

[Touch-packages] [Bug 1946499] Re: installation of deb-packages with gdebi-gtk shows "dpkg: error: unable to read filedescriptor flags for : Bad file descr

2021-10-14 Thread Gunnar Hjalmarsson
@Dani: Needless to say I didn't see your patch before submitting my
latest comment.

This sounds very promising! :) And suddenly I understand why gdebi
behaves differently in Ubuntu compared to Debian...

Will test is in a minute.

And yes, this means that we can simply start sync'ing vte2.91 from
Debian in the jj cycle.

Thanks a lot!

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

Title:
  installation of deb-packages with gdebi-gtk shows "dpkg: error: unable
  to read filedescriptor flags for : Bad file descriptor" in gdebi terminal, package is not
  installed

Status in Ubuntu MATE:
  Confirmed
Status in gdebi package in Ubuntu:
  Confirmed
Status in ubuntu-mate-meta package in Ubuntu:
  Confirmed
Status in vte2.91 package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Install Ubuntu MATE 21.10
  2. Open Firefox, navigate to discord.com
  3. Download deb-file. At time of writing from the 
https://dl.discordapp.net/apps/linux/0.0.16/discord-0.0.16.deb link
  4. Open Caja in ~/Downloads folder and use GDebi to install the 
discord-0.0.16.deb file
  5. In the GDebi window click Install button

  Expected results:
  * Gdebi quietly install discord package, there are no error messages in its 
terminal

  Actual results:
  * Gdebi terminal shows the error in the last line

  ```
  Selecting previously unselected package gconf2-common.
  (Reading database ... 457178 files and directories currently installed.)
  Preparing to unpack .../0-gconf2-common_3.2.6-7ubuntu2_all.deb ...
  Unpacking gconf2-common (3.2.6-7ubuntu2) ...
  Selecting previously unselected package libgconf-2-4:amd64.
  Preparing to unpack .../1-libgconf-2-4_3.2.6-7ubuntu2_amd64.deb ...
  Unpacking libgconf-2-4:amd64 (3.2.6-7ubuntu2) ...
  Selecting previously unselected package gconf-service-backend.
  Preparing to unpack .../2-gconf-service-backend_3.2.6-7ubuntu2_amd64.deb ...
  Unpacking gconf-service-backend (3.2.6-7ubuntu2) ...
  Selecting previously unselected package gconf-service.
  Preparing to unpack .../3-gconf-service_3.2.6-7ubuntu2_amd64.deb ...
  Unpacking gconf-service (3.2.6-7ubuntu2) ...
  Selecting previously unselected package libappindicator1.
  Preparing to unpack 
.../4-libappindicator1_12.10.1+20.10.20200706.1-0ubuntu1_amd64.deb ...
  Unpacking libappindicator1 (12.10.1+20.10.20200706.1-0ubuntu1) ...
  Selecting previously unselected package libunwind-13:amd64.
  Preparing to unpack .../5-libunwind-13_1%3a13.0.0-2_amd64.deb ...
  Unpacking libunwind-13:amd64 (1:13.0.0-2) ...
  Selecting previously unselected package libc++abi1-13:amd64.
  Preparing to unpack .../6-libc++abi1-13_1%3a13.0.0-2_amd64.deb ...
  Unpacking libc++abi1-13:amd64 (1:13.0.0-2) ...
  Selecting previously unselected package libc++1-13:amd64.
  Preparing to unpack .../7-libc++1-13_1%3a13.0.0-2_amd64.deb ...
  Unpacking libc++1-13:amd64 (1:13.0.0-2) ...
  Selecting previously unselected package libc++1:amd64.
  Preparing to unpack .../8-libc++1_1%3a13.0-53~exp1_amd64.deb ...
  Unpacking libc++1:amd64 (1:13.0-53~exp1) ...
  Setting up libappindicator1 (12.10.1+20.10.20200706.1-0ubuntu1) ...
  Setting up gconf2-common (3.2.6-7ubuntu2) ...

  Creating config file /etc/gconf/2/path with new version
  Setting up libunwind-13:amd64 (1:13.0.0-2) ...
  Setting up libc++abi1-13:amd64 (1:13.0.0-2) ...
  Setting up libc++1-13:amd64 (1:13.0.0-2) ...
  Setting up libc++1:amd64 (1:13.0-53~exp1) ...
  Setting up gconf-service (3.2.6-7ubuntu2) ...
  Processing triggers for libc-bin (2.34-0ubuntu2) ...
  Processing triggers for sgml-base (1.30) ...
  Setting up libgconf-2-4:amd64 (3.2.6-7ubuntu2) ...
  Setting up gconf-service-backend (3.2.6-7ubuntu2) ...
  Processing triggers for libc-bin (2.34-0ubuntu2) ...
  dpkg: error: unable to read filedescriptor flags for : Bad file descriptor
  ```

  and as the result Discord package is not installed .

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gdebi 0.9.5.7+nmu5ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  Date: Fri Oct  8 18:17:36 2021
  InstallationDate: Installed on 2021-10-08 (0 days ago)
  InstallationMedia: Ubuntu-MATE 21.10 "Impish Indri" - Daily amd64 (20211008)
  PackageArchitecture: all
  SourcePackage: gdebi
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2021-10-08T15:41:41.001986

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


-- 
Mailing list: 

[Touch-packages] [Bug 1946499] Re: installation of deb-packages with gdebi-gtk shows "dpkg: error: unable to read filedescriptor flags for : Bad file descr

2021-10-14 Thread Gunnar Hjalmarsson
The downgrade idea would need to be approved by some leading member of
Ubuntu's desktop team, and since 21.10 is released today, also the SRU
team would need to approve it. (You already know what I think the answer
will be.)

It's correct that I have helped with some routine packaging of VTE a
couple of times, but that does not make me "familiar with VTE codebase".
I'm not. Packaging and tweaking upstream code are different things.

So it boils down to neither you nor me has the sufficient skill to dig
into the code, and that somebody who has needs to give it priority.
Maybe Martin W., maybe somebody in Ubuntu's desktop team.

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

Title:
  installation of deb-packages with gdebi-gtk shows "dpkg: error: unable
  to read filedescriptor flags for : Bad file descriptor" in gdebi terminal, package is not
  installed

Status in Ubuntu MATE:
  Confirmed
Status in gdebi package in Ubuntu:
  Confirmed
Status in ubuntu-mate-meta package in Ubuntu:
  Confirmed
Status in vte2.91 package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Install Ubuntu MATE 21.10
  2. Open Firefox, navigate to discord.com
  3. Download deb-file. At time of writing from the 
https://dl.discordapp.net/apps/linux/0.0.16/discord-0.0.16.deb link
  4. Open Caja in ~/Downloads folder and use GDebi to install the 
discord-0.0.16.deb file
  5. In the GDebi window click Install button

  Expected results:
  * Gdebi quietly install discord package, there are no error messages in its 
terminal

  Actual results:
  * Gdebi terminal shows the error in the last line

  ```
  Selecting previously unselected package gconf2-common.
  (Reading database ... 457178 files and directories currently installed.)
  Preparing to unpack .../0-gconf2-common_3.2.6-7ubuntu2_all.deb ...
  Unpacking gconf2-common (3.2.6-7ubuntu2) ...
  Selecting previously unselected package libgconf-2-4:amd64.
  Preparing to unpack .../1-libgconf-2-4_3.2.6-7ubuntu2_amd64.deb ...
  Unpacking libgconf-2-4:amd64 (3.2.6-7ubuntu2) ...
  Selecting previously unselected package gconf-service-backend.
  Preparing to unpack .../2-gconf-service-backend_3.2.6-7ubuntu2_amd64.deb ...
  Unpacking gconf-service-backend (3.2.6-7ubuntu2) ...
  Selecting previously unselected package gconf-service.
  Preparing to unpack .../3-gconf-service_3.2.6-7ubuntu2_amd64.deb ...
  Unpacking gconf-service (3.2.6-7ubuntu2) ...
  Selecting previously unselected package libappindicator1.
  Preparing to unpack 
.../4-libappindicator1_12.10.1+20.10.20200706.1-0ubuntu1_amd64.deb ...
  Unpacking libappindicator1 (12.10.1+20.10.20200706.1-0ubuntu1) ...
  Selecting previously unselected package libunwind-13:amd64.
  Preparing to unpack .../5-libunwind-13_1%3a13.0.0-2_amd64.deb ...
  Unpacking libunwind-13:amd64 (1:13.0.0-2) ...
  Selecting previously unselected package libc++abi1-13:amd64.
  Preparing to unpack .../6-libc++abi1-13_1%3a13.0.0-2_amd64.deb ...
  Unpacking libc++abi1-13:amd64 (1:13.0.0-2) ...
  Selecting previously unselected package libc++1-13:amd64.
  Preparing to unpack .../7-libc++1-13_1%3a13.0.0-2_amd64.deb ...
  Unpacking libc++1-13:amd64 (1:13.0.0-2) ...
  Selecting previously unselected package libc++1:amd64.
  Preparing to unpack .../8-libc++1_1%3a13.0-53~exp1_amd64.deb ...
  Unpacking libc++1:amd64 (1:13.0-53~exp1) ...
  Setting up libappindicator1 (12.10.1+20.10.20200706.1-0ubuntu1) ...
  Setting up gconf2-common (3.2.6-7ubuntu2) ...

  Creating config file /etc/gconf/2/path with new version
  Setting up libunwind-13:amd64 (1:13.0.0-2) ...
  Setting up libc++abi1-13:amd64 (1:13.0.0-2) ...
  Setting up libc++1-13:amd64 (1:13.0.0-2) ...
  Setting up libc++1:amd64 (1:13.0-53~exp1) ...
  Setting up gconf-service (3.2.6-7ubuntu2) ...
  Processing triggers for libc-bin (2.34-0ubuntu2) ...
  Processing triggers for sgml-base (1.30) ...
  Setting up libgconf-2-4:amd64 (3.2.6-7ubuntu2) ...
  Setting up gconf-service-backend (3.2.6-7ubuntu2) ...
  Processing triggers for libc-bin (2.34-0ubuntu2) ...
  dpkg: error: unable to read filedescriptor flags for : Bad file descriptor
  ```

  and as the result Discord package is not installed .

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gdebi 0.9.5.7+nmu5ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  Date: Fri Oct  8 18:17:36 2021
  InstallationDate: Installed on 2021-10-08 (0 days ago)
  InstallationMedia: Ubuntu-MATE 21.10 "Impish Indri" - Daily amd64 (20211008)
  PackageArchitecture: all
  SourcePackage: gdebi
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can 

[Touch-packages] [Bug 1946499] Re: installation of deb-packages with gdebi-gtk shows "dpkg: error: unable to read filedescriptor flags for : Bad file descr

2021-10-14 Thread Gunnar Hjalmarsson
Please.. Downgrading VTE for this reason won't happen. Many other
packages are built with the latest version (running "apt rdepends
libvte-2.91-0" gives you a hint).

Rewriting the patch or fix gdebi so the patch isn't needed on Ubuntu are
two reasonable options. If you want to help fix this, please concentrate
on one of those options.

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

Title:
  installation of deb-packages with gdebi-gtk shows "dpkg: error: unable
  to read filedescriptor flags for : Bad file descriptor" in gdebi terminal, package is not
  installed

Status in Ubuntu MATE:
  Confirmed
Status in gdebi package in Ubuntu:
  Confirmed
Status in ubuntu-mate-meta package in Ubuntu:
  Confirmed
Status in vte2.91 package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Install Ubuntu MATE 21.10
  2. Open Firefox, navigate to discord.com
  3. Download deb-file. At time of writing from the 
https://dl.discordapp.net/apps/linux/0.0.16/discord-0.0.16.deb link
  4. Open Caja in ~/Downloads folder and use GDebi to install the 
discord-0.0.16.deb file
  5. In the GDebi window click Install button

  Expected results:
  * Gdebi quietly install discord package, there are no error messages in its 
terminal

  Actual results:
  * Gdebi terminal shows the error in the last line

  ```
  Selecting previously unselected package gconf2-common.
  (Reading database ... 457178 files and directories currently installed.)
  Preparing to unpack .../0-gconf2-common_3.2.6-7ubuntu2_all.deb ...
  Unpacking gconf2-common (3.2.6-7ubuntu2) ...
  Selecting previously unselected package libgconf-2-4:amd64.
  Preparing to unpack .../1-libgconf-2-4_3.2.6-7ubuntu2_amd64.deb ...
  Unpacking libgconf-2-4:amd64 (3.2.6-7ubuntu2) ...
  Selecting previously unselected package gconf-service-backend.
  Preparing to unpack .../2-gconf-service-backend_3.2.6-7ubuntu2_amd64.deb ...
  Unpacking gconf-service-backend (3.2.6-7ubuntu2) ...
  Selecting previously unselected package gconf-service.
  Preparing to unpack .../3-gconf-service_3.2.6-7ubuntu2_amd64.deb ...
  Unpacking gconf-service (3.2.6-7ubuntu2) ...
  Selecting previously unselected package libappindicator1.
  Preparing to unpack 
.../4-libappindicator1_12.10.1+20.10.20200706.1-0ubuntu1_amd64.deb ...
  Unpacking libappindicator1 (12.10.1+20.10.20200706.1-0ubuntu1) ...
  Selecting previously unselected package libunwind-13:amd64.
  Preparing to unpack .../5-libunwind-13_1%3a13.0.0-2_amd64.deb ...
  Unpacking libunwind-13:amd64 (1:13.0.0-2) ...
  Selecting previously unselected package libc++abi1-13:amd64.
  Preparing to unpack .../6-libc++abi1-13_1%3a13.0.0-2_amd64.deb ...
  Unpacking libc++abi1-13:amd64 (1:13.0.0-2) ...
  Selecting previously unselected package libc++1-13:amd64.
  Preparing to unpack .../7-libc++1-13_1%3a13.0.0-2_amd64.deb ...
  Unpacking libc++1-13:amd64 (1:13.0.0-2) ...
  Selecting previously unselected package libc++1:amd64.
  Preparing to unpack .../8-libc++1_1%3a13.0-53~exp1_amd64.deb ...
  Unpacking libc++1:amd64 (1:13.0-53~exp1) ...
  Setting up libappindicator1 (12.10.1+20.10.20200706.1-0ubuntu1) ...
  Setting up gconf2-common (3.2.6-7ubuntu2) ...

  Creating config file /etc/gconf/2/path with new version
  Setting up libunwind-13:amd64 (1:13.0.0-2) ...
  Setting up libc++abi1-13:amd64 (1:13.0.0-2) ...
  Setting up libc++1-13:amd64 (1:13.0.0-2) ...
  Setting up libc++1:amd64 (1:13.0-53~exp1) ...
  Setting up gconf-service (3.2.6-7ubuntu2) ...
  Processing triggers for libc-bin (2.34-0ubuntu2) ...
  Processing triggers for sgml-base (1.30) ...
  Setting up libgconf-2-4:amd64 (3.2.6-7ubuntu2) ...
  Setting up gconf-service-backend (3.2.6-7ubuntu2) ...
  Processing triggers for libc-bin (2.34-0ubuntu2) ...
  dpkg: error: unable to read filedescriptor flags for : Bad file descriptor
  ```

  and as the result Discord package is not installed .

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gdebi 0.9.5.7+nmu5ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  Date: Fri Oct  8 18:17:36 2021
  InstallationDate: Installed on 2021-10-08 (0 days ago)
  InstallationMedia: Ubuntu-MATE 21.10 "Impish Indri" - Daily amd64 (20211008)
  PackageArchitecture: all
  SourcePackage: gdebi
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2021-10-08T15:41:41.001986

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


-- 
Mailing list: 

[Touch-packages] [Bug 1946499] Re: installation of deb-packages with gdebi-gtk shows "dpkg: error: unable to read filedescriptor flags for : Bad file descr

2021-10-14 Thread Gunnar Hjalmarsson
On 2021-10-14 12:31, Norbert wrote:
> Tried to compile package from debian bookworm

That was one of the first things I tried, but IIRC I still got the
"unable to read filedescriptor flags" error. Which is a bit weird,
considering that it works in a Debian environment.

> Then when `gdebi-gtk file.deb` is executed, then terminal shows
> the following
> 
> ```
> (gdebi-gtk:14343): VTE-WARNING **: 13:31:00.005: (../src/vtepty.cc:669):bool 
> _vte_pty_spawn_sync(VtePty*, const char*, const char* const*, const char* 
> const*, GSpawnFlags, GSpawnChildSetupFunc, gpointer, GDestroyNotify, GPid*, 
> int, GCancellable*, GError**): runtime check failed: ((spawn_flags & 
> forbidden_spawn_flags()) == 0)
> ```
> 
> Could it be an issue?

Also that looks familiar.

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

Title:
  installation of deb-packages with gdebi-gtk shows "dpkg: error: unable
  to read filedescriptor flags for : Bad file descriptor" in gdebi terminal, package is not
  installed

Status in Ubuntu MATE:
  Confirmed
Status in gdebi package in Ubuntu:
  Confirmed
Status in ubuntu-mate-meta package in Ubuntu:
  Confirmed
Status in vte2.91 package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Install Ubuntu MATE 21.10
  2. Open Firefox, navigate to discord.com
  3. Download deb-file. At time of writing from the 
https://dl.discordapp.net/apps/linux/0.0.16/discord-0.0.16.deb link
  4. Open Caja in ~/Downloads folder and use GDebi to install the 
discord-0.0.16.deb file
  5. In the GDebi window click Install button

  Expected results:
  * Gdebi quietly install discord package, there are no error messages in its 
terminal

  Actual results:
  * Gdebi terminal shows the error in the last line

  ```
  Selecting previously unselected package gconf2-common.
  (Reading database ... 457178 files and directories currently installed.)
  Preparing to unpack .../0-gconf2-common_3.2.6-7ubuntu2_all.deb ...
  Unpacking gconf2-common (3.2.6-7ubuntu2) ...
  Selecting previously unselected package libgconf-2-4:amd64.
  Preparing to unpack .../1-libgconf-2-4_3.2.6-7ubuntu2_amd64.deb ...
  Unpacking libgconf-2-4:amd64 (3.2.6-7ubuntu2) ...
  Selecting previously unselected package gconf-service-backend.
  Preparing to unpack .../2-gconf-service-backend_3.2.6-7ubuntu2_amd64.deb ...
  Unpacking gconf-service-backend (3.2.6-7ubuntu2) ...
  Selecting previously unselected package gconf-service.
  Preparing to unpack .../3-gconf-service_3.2.6-7ubuntu2_amd64.deb ...
  Unpacking gconf-service (3.2.6-7ubuntu2) ...
  Selecting previously unselected package libappindicator1.
  Preparing to unpack 
.../4-libappindicator1_12.10.1+20.10.20200706.1-0ubuntu1_amd64.deb ...
  Unpacking libappindicator1 (12.10.1+20.10.20200706.1-0ubuntu1) ...
  Selecting previously unselected package libunwind-13:amd64.
  Preparing to unpack .../5-libunwind-13_1%3a13.0.0-2_amd64.deb ...
  Unpacking libunwind-13:amd64 (1:13.0.0-2) ...
  Selecting previously unselected package libc++abi1-13:amd64.
  Preparing to unpack .../6-libc++abi1-13_1%3a13.0.0-2_amd64.deb ...
  Unpacking libc++abi1-13:amd64 (1:13.0.0-2) ...
  Selecting previously unselected package libc++1-13:amd64.
  Preparing to unpack .../7-libc++1-13_1%3a13.0.0-2_amd64.deb ...
  Unpacking libc++1-13:amd64 (1:13.0.0-2) ...
  Selecting previously unselected package libc++1:amd64.
  Preparing to unpack .../8-libc++1_1%3a13.0-53~exp1_amd64.deb ...
  Unpacking libc++1:amd64 (1:13.0-53~exp1) ...
  Setting up libappindicator1 (12.10.1+20.10.20200706.1-0ubuntu1) ...
  Setting up gconf2-common (3.2.6-7ubuntu2) ...

  Creating config file /etc/gconf/2/path with new version
  Setting up libunwind-13:amd64 (1:13.0.0-2) ...
  Setting up libc++abi1-13:amd64 (1:13.0.0-2) ...
  Setting up libc++1-13:amd64 (1:13.0.0-2) ...
  Setting up libc++1:amd64 (1:13.0-53~exp1) ...
  Setting up gconf-service (3.2.6-7ubuntu2) ...
  Processing triggers for libc-bin (2.34-0ubuntu2) ...
  Processing triggers for sgml-base (1.30) ...
  Setting up libgconf-2-4:amd64 (3.2.6-7ubuntu2) ...
  Setting up gconf-service-backend (3.2.6-7ubuntu2) ...
  Processing triggers for libc-bin (2.34-0ubuntu2) ...
  dpkg: error: unable to read filedescriptor flags for : Bad file descriptor
  ```

  and as the result Discord package is not installed .

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gdebi 0.9.5.7+nmu5ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  Date: Fri Oct  8 18:17:36 2021
  InstallationDate: Installed on 2021-10-08 (0 days ago)
  InstallationMedia: Ubuntu-MATE 21.10 "Impish Indri" - Daily amd64 (20211008)
  PackageArchitecture: all
  SourcePackage: gdebi
  UpgradeStatus: No upgrade log present (probably 

[Touch-packages] [Bug 1946499] Re: installation of deb-packages with gdebi-gtk shows "dpkg: error: unable to read filedescriptor flags for : Bad file descr

2021-10-12 Thread Gunnar Hjalmarsson
Probably not. The hirsute version of vte2.91 does not even build on
impish.

For gdebi-gtk to keep working, somebody probably needs to

* rewrite 91_keep_fds.patch, or

* fix gdebi so it works without that patch.

Also I can't stop wondering why gdebi-gtk works on Debian testing
without 91_keep_fds.patch.

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

Title:
  installation of deb-packages with gdebi-gtk shows "dpkg: error: unable
  to read filedescriptor flags for : Bad file descriptor" in gdebi terminal, package is not
  installed

Status in Ubuntu MATE:
  Confirmed
Status in gdebi package in Ubuntu:
  Confirmed
Status in ubuntu-mate-meta package in Ubuntu:
  Confirmed
Status in vte2.91 package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Install Ubuntu MATE 21.10
  2. Open Firefox, navigate to discord.com
  3. Download deb-file. At time of writing from the 
https://dl.discordapp.net/apps/linux/0.0.16/discord-0.0.16.deb link
  4. Open Caja in ~/Downloads folder and use GDebi to install the 
discord-0.0.16.deb file
  5. In the GDebi window click Install button

  Expected results:
  * Gdebi quietly install discord package, there are no error messages in its 
terminal

  Actual results:
  * Gdebi terminal shows the error in the last line

  ```
  Selecting previously unselected package gconf2-common.
  (Reading database ... 457178 files and directories currently installed.)
  Preparing to unpack .../0-gconf2-common_3.2.6-7ubuntu2_all.deb ...
  Unpacking gconf2-common (3.2.6-7ubuntu2) ...
  Selecting previously unselected package libgconf-2-4:amd64.
  Preparing to unpack .../1-libgconf-2-4_3.2.6-7ubuntu2_amd64.deb ...
  Unpacking libgconf-2-4:amd64 (3.2.6-7ubuntu2) ...
  Selecting previously unselected package gconf-service-backend.
  Preparing to unpack .../2-gconf-service-backend_3.2.6-7ubuntu2_amd64.deb ...
  Unpacking gconf-service-backend (3.2.6-7ubuntu2) ...
  Selecting previously unselected package gconf-service.
  Preparing to unpack .../3-gconf-service_3.2.6-7ubuntu2_amd64.deb ...
  Unpacking gconf-service (3.2.6-7ubuntu2) ...
  Selecting previously unselected package libappindicator1.
  Preparing to unpack 
.../4-libappindicator1_12.10.1+20.10.20200706.1-0ubuntu1_amd64.deb ...
  Unpacking libappindicator1 (12.10.1+20.10.20200706.1-0ubuntu1) ...
  Selecting previously unselected package libunwind-13:amd64.
  Preparing to unpack .../5-libunwind-13_1%3a13.0.0-2_amd64.deb ...
  Unpacking libunwind-13:amd64 (1:13.0.0-2) ...
  Selecting previously unselected package libc++abi1-13:amd64.
  Preparing to unpack .../6-libc++abi1-13_1%3a13.0.0-2_amd64.deb ...
  Unpacking libc++abi1-13:amd64 (1:13.0.0-2) ...
  Selecting previously unselected package libc++1-13:amd64.
  Preparing to unpack .../7-libc++1-13_1%3a13.0.0-2_amd64.deb ...
  Unpacking libc++1-13:amd64 (1:13.0.0-2) ...
  Selecting previously unselected package libc++1:amd64.
  Preparing to unpack .../8-libc++1_1%3a13.0-53~exp1_amd64.deb ...
  Unpacking libc++1:amd64 (1:13.0-53~exp1) ...
  Setting up libappindicator1 (12.10.1+20.10.20200706.1-0ubuntu1) ...
  Setting up gconf2-common (3.2.6-7ubuntu2) ...

  Creating config file /etc/gconf/2/path with new version
  Setting up libunwind-13:amd64 (1:13.0.0-2) ...
  Setting up libc++abi1-13:amd64 (1:13.0.0-2) ...
  Setting up libc++1-13:amd64 (1:13.0.0-2) ...
  Setting up libc++1:amd64 (1:13.0-53~exp1) ...
  Setting up gconf-service (3.2.6-7ubuntu2) ...
  Processing triggers for libc-bin (2.34-0ubuntu2) ...
  Processing triggers for sgml-base (1.30) ...
  Setting up libgconf-2-4:amd64 (3.2.6-7ubuntu2) ...
  Setting up gconf-service-backend (3.2.6-7ubuntu2) ...
  Processing triggers for libc-bin (2.34-0ubuntu2) ...
  dpkg: error: unable to read filedescriptor flags for : Bad file descriptor
  ```

  and as the result Discord package is not installed .

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gdebi 0.9.5.7+nmu5ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  Date: Fri Oct  8 18:17:36 2021
  InstallationDate: Installed on 2021-10-08 (0 days ago)
  InstallationMedia: Ubuntu-MATE 21.10 "Impish Indri" - Daily amd64 (20211008)
  PackageArchitecture: all
  SourcePackage: gdebi
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2021-10-08T15:41:41.001986

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post 

[Touch-packages] [Bug 1946499] Re: installation of deb-packages with gdebi-gtk shows "dpkg: error: unable to read filedescriptor flags for : Bad file descr

2021-10-12 Thread Gunnar Hjalmarsson
A related comment in #ubuntu-desktop:

https://irclogs.ubuntu.com/2021/10/12/%23ubuntu-desktop.html#t15:12

** Changed in: vte2.91 (Ubuntu)
 Assignee: Gunnar Hjalmarsson (gunnarhj) => (unassigned)

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

Title:
  installation of deb-packages with gdebi-gtk shows "dpkg: error: unable
  to read filedescriptor flags for : Bad file descriptor" in gdebi terminal, package is not
  installed

Status in Ubuntu MATE:
  Confirmed
Status in gdebi package in Ubuntu:
  Confirmed
Status in ubuntu-mate-meta package in Ubuntu:
  Confirmed
Status in vte2.91 package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Install Ubuntu MATE 21.10
  2. Open Firefox, navigate to discord.com
  3. Download deb-file. At time of writing from the 
https://dl.discordapp.net/apps/linux/0.0.16/discord-0.0.16.deb link
  4. Open Caja in ~/Downloads folder and use GDebi to install the 
discord-0.0.16.deb file
  5. In the GDebi window click Install button

  Expected results:
  * Gdebi quietly install discord package, there are no error messages in its 
terminal

  Actual results:
  * Gdebi terminal shows the error in the last line

  ```
  Selecting previously unselected package gconf2-common.
  (Reading database ... 457178 files and directories currently installed.)
  Preparing to unpack .../0-gconf2-common_3.2.6-7ubuntu2_all.deb ...
  Unpacking gconf2-common (3.2.6-7ubuntu2) ...
  Selecting previously unselected package libgconf-2-4:amd64.
  Preparing to unpack .../1-libgconf-2-4_3.2.6-7ubuntu2_amd64.deb ...
  Unpacking libgconf-2-4:amd64 (3.2.6-7ubuntu2) ...
  Selecting previously unselected package gconf-service-backend.
  Preparing to unpack .../2-gconf-service-backend_3.2.6-7ubuntu2_amd64.deb ...
  Unpacking gconf-service-backend (3.2.6-7ubuntu2) ...
  Selecting previously unselected package gconf-service.
  Preparing to unpack .../3-gconf-service_3.2.6-7ubuntu2_amd64.deb ...
  Unpacking gconf-service (3.2.6-7ubuntu2) ...
  Selecting previously unselected package libappindicator1.
  Preparing to unpack 
.../4-libappindicator1_12.10.1+20.10.20200706.1-0ubuntu1_amd64.deb ...
  Unpacking libappindicator1 (12.10.1+20.10.20200706.1-0ubuntu1) ...
  Selecting previously unselected package libunwind-13:amd64.
  Preparing to unpack .../5-libunwind-13_1%3a13.0.0-2_amd64.deb ...
  Unpacking libunwind-13:amd64 (1:13.0.0-2) ...
  Selecting previously unselected package libc++abi1-13:amd64.
  Preparing to unpack .../6-libc++abi1-13_1%3a13.0.0-2_amd64.deb ...
  Unpacking libc++abi1-13:amd64 (1:13.0.0-2) ...
  Selecting previously unselected package libc++1-13:amd64.
  Preparing to unpack .../7-libc++1-13_1%3a13.0.0-2_amd64.deb ...
  Unpacking libc++1-13:amd64 (1:13.0.0-2) ...
  Selecting previously unselected package libc++1:amd64.
  Preparing to unpack .../8-libc++1_1%3a13.0-53~exp1_amd64.deb ...
  Unpacking libc++1:amd64 (1:13.0-53~exp1) ...
  Setting up libappindicator1 (12.10.1+20.10.20200706.1-0ubuntu1) ...
  Setting up gconf2-common (3.2.6-7ubuntu2) ...

  Creating config file /etc/gconf/2/path with new version
  Setting up libunwind-13:amd64 (1:13.0.0-2) ...
  Setting up libc++abi1-13:amd64 (1:13.0.0-2) ...
  Setting up libc++1-13:amd64 (1:13.0.0-2) ...
  Setting up libc++1:amd64 (1:13.0-53~exp1) ...
  Setting up gconf-service (3.2.6-7ubuntu2) ...
  Processing triggers for libc-bin (2.34-0ubuntu2) ...
  Processing triggers for sgml-base (1.30) ...
  Setting up libgconf-2-4:amd64 (3.2.6-7ubuntu2) ...
  Setting up gconf-service-backend (3.2.6-7ubuntu2) ...
  Processing triggers for libc-bin (2.34-0ubuntu2) ...
  dpkg: error: unable to read filedescriptor flags for : Bad file descriptor
  ```

  and as the result Discord package is not installed .

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gdebi 0.9.5.7+nmu5ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  Date: Fri Oct  8 18:17:36 2021
  InstallationDate: Installed on 2021-10-08 (0 days ago)
  InstallationMedia: Ubuntu-MATE 21.10 "Impish Indri" - Daily amd64 (20211008)
  PackageArchitecture: all
  SourcePackage: gdebi
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2021-10-08T15:41:41.001986

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


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

[Touch-packages] [Bug 1946499] Re: installation of deb-packages with gdebi-gtk shows "dpkg: error: unable to read filedescriptor flags for : Bad file descr

2021-10-12 Thread Gunnar Hjalmarsson
This is an attempt at a fix which does not work:

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

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

Title:
  installation of deb-packages with gdebi-gtk shows "dpkg: error: unable
  to read filedescriptor flags for : Bad file descriptor" in gdebi terminal, package is not
  installed

Status in Ubuntu MATE:
  Confirmed
Status in gdebi package in Ubuntu:
  Confirmed
Status in ubuntu-mate-meta package in Ubuntu:
  Confirmed
Status in vte2.91 package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Install Ubuntu MATE 21.10
  2. Open Firefox, navigate to discord.com
  3. Download deb-file. At time of writing from the 
https://dl.discordapp.net/apps/linux/0.0.16/discord-0.0.16.deb link
  4. Open Caja in ~/Downloads folder and use GDebi to install the 
discord-0.0.16.deb file
  5. In the GDebi window click Install button

  Expected results:
  * Gdebi quietly install discord package, there are no error messages in its 
terminal

  Actual results:
  * Gdebi terminal shows the error in the last line

  ```
  Selecting previously unselected package gconf2-common.
  (Reading database ... 457178 files and directories currently installed.)
  Preparing to unpack .../0-gconf2-common_3.2.6-7ubuntu2_all.deb ...
  Unpacking gconf2-common (3.2.6-7ubuntu2) ...
  Selecting previously unselected package libgconf-2-4:amd64.
  Preparing to unpack .../1-libgconf-2-4_3.2.6-7ubuntu2_amd64.deb ...
  Unpacking libgconf-2-4:amd64 (3.2.6-7ubuntu2) ...
  Selecting previously unselected package gconf-service-backend.
  Preparing to unpack .../2-gconf-service-backend_3.2.6-7ubuntu2_amd64.deb ...
  Unpacking gconf-service-backend (3.2.6-7ubuntu2) ...
  Selecting previously unselected package gconf-service.
  Preparing to unpack .../3-gconf-service_3.2.6-7ubuntu2_amd64.deb ...
  Unpacking gconf-service (3.2.6-7ubuntu2) ...
  Selecting previously unselected package libappindicator1.
  Preparing to unpack 
.../4-libappindicator1_12.10.1+20.10.20200706.1-0ubuntu1_amd64.deb ...
  Unpacking libappindicator1 (12.10.1+20.10.20200706.1-0ubuntu1) ...
  Selecting previously unselected package libunwind-13:amd64.
  Preparing to unpack .../5-libunwind-13_1%3a13.0.0-2_amd64.deb ...
  Unpacking libunwind-13:amd64 (1:13.0.0-2) ...
  Selecting previously unselected package libc++abi1-13:amd64.
  Preparing to unpack .../6-libc++abi1-13_1%3a13.0.0-2_amd64.deb ...
  Unpacking libc++abi1-13:amd64 (1:13.0.0-2) ...
  Selecting previously unselected package libc++1-13:amd64.
  Preparing to unpack .../7-libc++1-13_1%3a13.0.0-2_amd64.deb ...
  Unpacking libc++1-13:amd64 (1:13.0.0-2) ...
  Selecting previously unselected package libc++1:amd64.
  Preparing to unpack .../8-libc++1_1%3a13.0-53~exp1_amd64.deb ...
  Unpacking libc++1:amd64 (1:13.0-53~exp1) ...
  Setting up libappindicator1 (12.10.1+20.10.20200706.1-0ubuntu1) ...
  Setting up gconf2-common (3.2.6-7ubuntu2) ...

  Creating config file /etc/gconf/2/path with new version
  Setting up libunwind-13:amd64 (1:13.0.0-2) ...
  Setting up libc++abi1-13:amd64 (1:13.0.0-2) ...
  Setting up libc++1-13:amd64 (1:13.0.0-2) ...
  Setting up libc++1:amd64 (1:13.0-53~exp1) ...
  Setting up gconf-service (3.2.6-7ubuntu2) ...
  Processing triggers for libc-bin (2.34-0ubuntu2) ...
  Processing triggers for sgml-base (1.30) ...
  Setting up libgconf-2-4:amd64 (3.2.6-7ubuntu2) ...
  Setting up gconf-service-backend (3.2.6-7ubuntu2) ...
  Processing triggers for libc-bin (2.34-0ubuntu2) ...
  dpkg: error: unable to read filedescriptor flags for : Bad file descriptor
  ```

  and as the result Discord package is not installed .

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gdebi 0.9.5.7+nmu5ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  Date: Fri Oct  8 18:17:36 2021
  InstallationDate: Installed on 2021-10-08 (0 days ago)
  InstallationMedia: Ubuntu-MATE 21.10 "Impish Indri" - Daily amd64 (20211008)
  PackageArchitecture: all
  SourcePackage: gdebi
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2021-10-08T15:41:41.001986

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1946499/+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 1946499] Re: installation of deb-packages with gdebi-gtk shows "dpkg: error: unable to read filedescriptor flags for : Bad file descr

2021-10-12 Thread Gunnar Hjalmarsson
Confirmed that gdebi-gtk works on Debian testing (without
91_keep_fds.patch). So the need for that patch is Ubuntu specific
somehow. (Not sure how that helps, but I thought it was worth checking.)

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

Title:
  installation of deb-packages with gdebi-gtk shows "dpkg: error: unable
  to read filedescriptor flags for : Bad file descriptor" in gdebi terminal, package is not
  installed

Status in Ubuntu MATE:
  Confirmed
Status in gdebi package in Ubuntu:
  Confirmed
Status in ubuntu-mate-meta package in Ubuntu:
  Confirmed
Status in vte2.91 package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Install Ubuntu MATE 21.10
  2. Open Firefox, navigate to discord.com
  3. Download deb-file. At time of writing from the 
https://dl.discordapp.net/apps/linux/0.0.16/discord-0.0.16.deb link
  4. Open Caja in ~/Downloads folder and use GDebi to install the 
discord-0.0.16.deb file
  5. In the GDebi window click Install button

  Expected results:
  * Gdebi quietly install discord package, there are no error messages in its 
terminal

  Actual results:
  * Gdebi terminal shows the error in the last line

  ```
  Selecting previously unselected package gconf2-common.
  (Reading database ... 457178 files and directories currently installed.)
  Preparing to unpack .../0-gconf2-common_3.2.6-7ubuntu2_all.deb ...
  Unpacking gconf2-common (3.2.6-7ubuntu2) ...
  Selecting previously unselected package libgconf-2-4:amd64.
  Preparing to unpack .../1-libgconf-2-4_3.2.6-7ubuntu2_amd64.deb ...
  Unpacking libgconf-2-4:amd64 (3.2.6-7ubuntu2) ...
  Selecting previously unselected package gconf-service-backend.
  Preparing to unpack .../2-gconf-service-backend_3.2.6-7ubuntu2_amd64.deb ...
  Unpacking gconf-service-backend (3.2.6-7ubuntu2) ...
  Selecting previously unselected package gconf-service.
  Preparing to unpack .../3-gconf-service_3.2.6-7ubuntu2_amd64.deb ...
  Unpacking gconf-service (3.2.6-7ubuntu2) ...
  Selecting previously unselected package libappindicator1.
  Preparing to unpack 
.../4-libappindicator1_12.10.1+20.10.20200706.1-0ubuntu1_amd64.deb ...
  Unpacking libappindicator1 (12.10.1+20.10.20200706.1-0ubuntu1) ...
  Selecting previously unselected package libunwind-13:amd64.
  Preparing to unpack .../5-libunwind-13_1%3a13.0.0-2_amd64.deb ...
  Unpacking libunwind-13:amd64 (1:13.0.0-2) ...
  Selecting previously unselected package libc++abi1-13:amd64.
  Preparing to unpack .../6-libc++abi1-13_1%3a13.0.0-2_amd64.deb ...
  Unpacking libc++abi1-13:amd64 (1:13.0.0-2) ...
  Selecting previously unselected package libc++1-13:amd64.
  Preparing to unpack .../7-libc++1-13_1%3a13.0.0-2_amd64.deb ...
  Unpacking libc++1-13:amd64 (1:13.0.0-2) ...
  Selecting previously unselected package libc++1:amd64.
  Preparing to unpack .../8-libc++1_1%3a13.0-53~exp1_amd64.deb ...
  Unpacking libc++1:amd64 (1:13.0-53~exp1) ...
  Setting up libappindicator1 (12.10.1+20.10.20200706.1-0ubuntu1) ...
  Setting up gconf2-common (3.2.6-7ubuntu2) ...

  Creating config file /etc/gconf/2/path with new version
  Setting up libunwind-13:amd64 (1:13.0.0-2) ...
  Setting up libc++abi1-13:amd64 (1:13.0.0-2) ...
  Setting up libc++1-13:amd64 (1:13.0.0-2) ...
  Setting up libc++1:amd64 (1:13.0-53~exp1) ...
  Setting up gconf-service (3.2.6-7ubuntu2) ...
  Processing triggers for libc-bin (2.34-0ubuntu2) ...
  Processing triggers for sgml-base (1.30) ...
  Setting up libgconf-2-4:amd64 (3.2.6-7ubuntu2) ...
  Setting up gconf-service-backend (3.2.6-7ubuntu2) ...
  Processing triggers for libc-bin (2.34-0ubuntu2) ...
  dpkg: error: unable to read filedescriptor flags for : Bad file descriptor
  ```

  and as the result Discord package is not installed .

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gdebi 0.9.5.7+nmu5ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  Date: Fri Oct  8 18:17:36 2021
  InstallationDate: Installed on 2021-10-08 (0 days ago)
  InstallationMedia: Ubuntu-MATE 21.10 "Impish Indri" - Daily amd64 (20211008)
  PackageArchitecture: all
  SourcePackage: gdebi
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2021-10-08T15:41:41.001986

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


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

[Touch-packages] [Bug 1946499] Re: installation of deb-packages with gdebi-gtk shows "dpkg: error: unable to read filedescriptor flags for : Bad file descr

2021-10-12 Thread Gunnar Hjalmarsson
Hi!

I can confirm the problem with gdebi-gtk, as already described by
Norbert.

The patch is apparently a workaround since nobody has had the time to
adapt gdebi. My refresh in the latest Ubuntu upload of vte2.91 was a
minimum change to make it still apply after upstream had made changes.
Maybe I did a mistake when doing so.

Wonder if gdebi-gtk works on Debian (which does not have
91_keep_fds.patch.

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

Title:
  installation of deb-packages with gdebi-gtk shows "dpkg: error: unable
  to read filedescriptor flags for : Bad file descriptor" in gdebi terminal, package is not
  installed

Status in Ubuntu MATE:
  Confirmed
Status in gdebi package in Ubuntu:
  Confirmed
Status in ubuntu-mate-meta package in Ubuntu:
  Confirmed
Status in vte2.91 package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Install Ubuntu MATE 21.10
  2. Open Firefox, navigate to discord.com
  3. Download deb-file. At time of writing from the 
https://dl.discordapp.net/apps/linux/0.0.16/discord-0.0.16.deb link
  4. Open Caja in ~/Downloads folder and use GDebi to install the 
discord-0.0.16.deb file
  5. In the GDebi window click Install button

  Expected results:
  * Gdebi quietly install discord package, there are no error messages in its 
terminal

  Actual results:
  * Gdebi terminal shows the error in the last line

  ```
  Selecting previously unselected package gconf2-common.
  (Reading database ... 457178 files and directories currently installed.)
  Preparing to unpack .../0-gconf2-common_3.2.6-7ubuntu2_all.deb ...
  Unpacking gconf2-common (3.2.6-7ubuntu2) ...
  Selecting previously unselected package libgconf-2-4:amd64.
  Preparing to unpack .../1-libgconf-2-4_3.2.6-7ubuntu2_amd64.deb ...
  Unpacking libgconf-2-4:amd64 (3.2.6-7ubuntu2) ...
  Selecting previously unselected package gconf-service-backend.
  Preparing to unpack .../2-gconf-service-backend_3.2.6-7ubuntu2_amd64.deb ...
  Unpacking gconf-service-backend (3.2.6-7ubuntu2) ...
  Selecting previously unselected package gconf-service.
  Preparing to unpack .../3-gconf-service_3.2.6-7ubuntu2_amd64.deb ...
  Unpacking gconf-service (3.2.6-7ubuntu2) ...
  Selecting previously unselected package libappindicator1.
  Preparing to unpack 
.../4-libappindicator1_12.10.1+20.10.20200706.1-0ubuntu1_amd64.deb ...
  Unpacking libappindicator1 (12.10.1+20.10.20200706.1-0ubuntu1) ...
  Selecting previously unselected package libunwind-13:amd64.
  Preparing to unpack .../5-libunwind-13_1%3a13.0.0-2_amd64.deb ...
  Unpacking libunwind-13:amd64 (1:13.0.0-2) ...
  Selecting previously unselected package libc++abi1-13:amd64.
  Preparing to unpack .../6-libc++abi1-13_1%3a13.0.0-2_amd64.deb ...
  Unpacking libc++abi1-13:amd64 (1:13.0.0-2) ...
  Selecting previously unselected package libc++1-13:amd64.
  Preparing to unpack .../7-libc++1-13_1%3a13.0.0-2_amd64.deb ...
  Unpacking libc++1-13:amd64 (1:13.0.0-2) ...
  Selecting previously unselected package libc++1:amd64.
  Preparing to unpack .../8-libc++1_1%3a13.0-53~exp1_amd64.deb ...
  Unpacking libc++1:amd64 (1:13.0-53~exp1) ...
  Setting up libappindicator1 (12.10.1+20.10.20200706.1-0ubuntu1) ...
  Setting up gconf2-common (3.2.6-7ubuntu2) ...

  Creating config file /etc/gconf/2/path with new version
  Setting up libunwind-13:amd64 (1:13.0.0-2) ...
  Setting up libc++abi1-13:amd64 (1:13.0.0-2) ...
  Setting up libc++1-13:amd64 (1:13.0.0-2) ...
  Setting up libc++1:amd64 (1:13.0-53~exp1) ...
  Setting up gconf-service (3.2.6-7ubuntu2) ...
  Processing triggers for libc-bin (2.34-0ubuntu2) ...
  Processing triggers for sgml-base (1.30) ...
  Setting up libgconf-2-4:amd64 (3.2.6-7ubuntu2) ...
  Setting up gconf-service-backend (3.2.6-7ubuntu2) ...
  Processing triggers for libc-bin (2.34-0ubuntu2) ...
  dpkg: error: unable to read filedescriptor flags for : Bad file descriptor
  ```

  and as the result Discord package is not installed .

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gdebi 0.9.5.7+nmu5ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  Date: Fri Oct  8 18:17:36 2021
  InstallationDate: Installed on 2021-10-08 (0 days ago)
  InstallationMedia: Ubuntu-MATE 21.10 "Impish Indri" - Daily amd64 (20211008)
  PackageArchitecture: all
  SourcePackage: gdebi
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2021-10-08T15:41:41.001986

To manage notifications about this bug go to:

[Touch-packages] [Bug 1945817] Re: Change default Amharic font from Abyssinica SIL to Noto Serif Ethiopic

2021-10-06 Thread Gunnar Hjalmarsson
** Changed in: language-selector (Ubuntu)
   Status: In Progress => Fix Committed

** No longer affects: ubuntu-meta (Ubuntu)

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

Title:
  Change default Amharic font from Abyssinica SIL to Noto Serif Ethiopic

Status in language-selector package in Ubuntu:
  Fix Committed

Bug description:
  Description of problem:

  Abyssinica SIL is an old font. It's barely legible and breaks in most
  apps. Noto Serif Ethiopic, on the other hand, is a modern and well
  designed font.

  Noto Serif Ethiopic is distributed with the Open Font License, so
  packaging it won't be a problem.

  Link
  
https://fonts.google.com/noto/specimen/Noto+Serif+Ethiopic?noto.query=Amharic=Ethi

  Version: 20.04.3

  How reproducible:
  always

  Steps to Reproduce:
  1. Pretty much using the the Amharic language anywhere on Ubuntu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1945817/+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 1945817] Re: Change default Amharic font from Abyssinica SIL to Noto Serif Ethiopic

2021-10-05 Thread Gunnar Hjalmarsson
Hey @carnage-mode, where did you go? ;)

I have looked a bit more into this, and my understanding is that there
are two packages — fonts-sil-abyssinica and fonts-freefont-ttf — with
fonts which can render Amharic and which are installed by default on
Ubuntu.

But only by installing fonts-noto-core, without uninstalling any of the
others, I notice a significant difference at e.g.

since it makes use of "Noto Sans Ethiopic".

Final freeze for Ubuntu 21.10 is tomorrow, but if you confirm very soon
that it would be helpful, I can change it so that fonts-noto-core is
automatically installed if you install the Amharic language. If you
would like to see more extensive tweaks, it will need to be discussed
further after the Ubuntu 21.10 release.

Let me know.

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

Title:
  Change default Amharic font from Abyssinica SIL to Noto Serif Ethiopic

Status in language-selector package in Ubuntu:
  In Progress
Status in ubuntu-meta package in Ubuntu:
  In Progress

Bug description:
  Description of problem:

  Abyssinica SIL is an old font. It's barely legible and breaks in most
  apps. Noto Serif Ethiopic, on the other hand, is a modern and well
  designed font.

  Noto Serif Ethiopic is distributed with the Open Font License, so
  packaging it won't be a problem.

  Link
  
https://fonts.google.com/noto/specimen/Noto+Serif+Ethiopic?noto.query=Amharic=Ethi

  Version: 20.04.3

  How reproducible:
  always

  Steps to Reproduce:
  1. Pretty much using the the Amharic language anywhere on Ubuntu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1945817/+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 1945894] Re: Translated strings not imported from damned lies

2021-10-04 Thread Gunnar Hjalmarsson
@Ask: If you want to talk more about the translation related workflow,
please feel free to post to the ubuntu-translators mailing list.

https://lists.ubuntu.com/mailman/listinfo/ubuntu-translators

** Changed in: ubuntu-translations
   Status: Incomplete => Invalid

-- 
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/1945894

Title:
  Translated strings not imported from damned lies

Status in Ubuntu Translations:
  Invalid
Status in gtk+3.0 package in Ubuntu:
  Invalid

Bug description:
  The newly translated strings in GTK does not seem to be imported from
  Damned Lies. GTK in Ubuntu has 50 untranslated strings in Danish but
  is fully translated in Damned Lies.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-translations/+bug/1945894/+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 1945817] Re: Change default Amharic font from Abyssinica SIL to Noto Serif Ethiopic

2021-10-04 Thread Gunnar Hjalmarsson
Hi carnage-mode,

Thanks for your report. We could make it install fonts-noto-core by
default when you install the Amharic language. That package provides
both "Noto Serif Ethiopic" and "Noto Sans Ethiopic".

As a test, can you please run these commands:

sudo apt purge fonts-sil-abyssinica
sudo apt install fonts-noto-core

and let us know if the result is an improved rendering of Amharic.

** Also affects: ubuntu-meta (Ubuntu)
   Importance: Undecided
   Status: New

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

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

** Changed in: ubuntu-meta (Ubuntu)
   Importance: Undecided => Wishlist

** Changed in: ubuntu-meta (Ubuntu)
   Status: New => In Progress

** Changed in: ubuntu-meta (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 ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1945817

Title:
  Change default Amharic font from Abyssinica SIL to Noto Serif Ethiopic

Status in language-selector package in Ubuntu:
  In Progress
Status in ubuntu-meta package in Ubuntu:
  In Progress

Bug description:
  Description of problem:

  Abyssinica SIL is an old font. It's barely legible and breaks in most
  apps. Noto Serif Ethiopic, on the other hand, is a modern and well
  designed font.

  Noto Serif Ethiopic is distributed with the Open Font License, so
  packaging it won't be a problem.

  Link
  
https://fonts.google.com/noto/specimen/Noto+Serif+Ethiopic?noto.query=Amharic=Ethi

  Version: 20.04.3

  How reproducible:
  always

  Steps to Reproduce:
  1. Pretty much using the the Amharic language anywhere on Ubuntu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1945817/+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 1945894] Re: Translated strings not imported from damned lies

2021-10-03 Thread Gunnar Hjalmarsson
Thanks for your report!

We don't import translations directly from Damned Lies, but via the PO
files in upstream's tarballs. The latest gtk3 version in Ubuntu is
3.24.30 which was released on July 8.

So if those strings were translated after July 8, they are not yet in
Ubuntu due to the workflow, but will show up later (probably only in
22.04).

Please let us know whether you still think there is a bug.

** Also affects: ubuntu-translations
   Importance: Undecided
   Status: New

** Changed in: ubuntu-translations
   Status: New => Incomplete

** Changed in: gtk+3.0 (Ubuntu)
   Status: New => Incomplete

-- 
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/1945894

Title:
  Translated strings not imported from damned lies

Status in Ubuntu Translations:
  Incomplete
Status in gtk+3.0 package in Ubuntu:
  Incomplete

Bug description:
  The newly translated strings in GTK does not seem to be imported from
  Damned Lies. GTK in Ubuntu has 50 untranslated strings in Danish but
  is fully translated in Damned Lies.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-translations/+bug/1945894/+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 1921781] Re: Build-depends on qt5-default which is obsolete and dropped in hirsute

2021-09-29 Thread Gunnar Hjalmarsson
** Changed in: indicator-sound (Ubuntu)
   Status: Confirmed => Fix Committed

-- 
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:
  Fix Committed
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:
  Invalid

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 1921781] Re: Build-depends on qt5-default which is obsolete and dropped in hirsute

2021-09-29 Thread Gunnar Hjalmarsson
@Khurshid: Please see comment on the merge request.

-- 
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:
  Invalid

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 1944430] Re: ibus-extension-gtk3 crashed with SIGABRT in g_assertion_message_expr()

2021-09-21 Thread Gunnar Hjalmarsson
Thanks for your report. The information is somewhat contradictory,
though:

On 2021-09-21 14:42, Christian Kirbach wrote:
> Crash information appeared at Ubuntu Unity desktop startup
---^

> CurrentDesktop: ubuntu:GNOME
-^

So this does not seem to be a Unity session. Can you please let us know
which desktop environment this actually relates to, and which steps you
took before the ibus crash.

** 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/1944430

Title:
  ibus-extension-gtk3 crashed with SIGABRT in g_assertion_message_expr()

Status in ibus package in Ubuntu:
  Incomplete

Bug description:
  Crash information appeared at Ubuntu Unity desktop startup

  ProblemType: Crash
  DistroRelease: Ubuntu 21.10
  Package: ibus 1.5.25-2
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 21 14:39:19 2021
  ExecutablePath: /usr/libexec/ibus-extension-gtk3
  InstallationDate: Installed on 2021-04-27 (146 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210331.1)
  ProcCmdline: /usr/libexec/ibus-extension-gtk3
  ProcEnviron:
   LANG=de_DE.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  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
   g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: ibus-extension-gtk3 crashed with SIGABRT in g_assertion_message_expr()
  UpgradeStatus: Upgraded to impish on 2021-09-21 (0 days ago)
  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/1944430/+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 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


  1   2   3   4   5   6   7   8   9   10   >