[Touch-packages] [Bug 1895454] Re: ibus indicator is unreadable, and the dropdown doesn't clarify what option is selected

2020-09-15 Thread Gunnar Hjalmarsson
On 2020-09-15 18:26, php4fan wrote:
> Most icon have bright colors, which seems to suggest that if there is
> an expectation about the background color, it's that it is dark,
> which my current panel background is.

Dark blue is probably not an optimal default.

I would suggest that you file an upstream issue about it:

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

If you do, please post the URL to it here. We can keep this bug open for
now for tracking purposes.

-- 
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 package in Ubuntu:
  Confirmed

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/ubuntu/+source/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 1895454] Re: ibus indicator is unreadable, and the dropdown doesn't clarify what option is selected

2020-09-13 Thread Gunnar Hjalmarsson
It can also be that the desktop environment you are using was designed
with an "idiotic" background color, right?

Anyway, the icon color can be changed:

gsettings set org.freedesktop.ibus.panel xkb-icon-rgba '#ff'


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

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

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

Status in ibus package in Ubuntu:
  Invalid

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/ubuntu/+source/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 1892014] Re: 18.04.14.7 regression: no alt_shift_toggle in XKBOPTIONS

2020-09-01 Thread Gunnar Hjalmarsson
Hi again,

On 2020-08-27 08:25, Alkis Georgopoulos wrote:
>> Possibly console-setup could be modified again, so the default
>> shortcut depends on XDG_CURRENT_DESKTOP ("No toggling" for GNOME
>> and "Alt+Shift" for others). That way there wouldn't be a need to
>> involve ubiquity or other desktops.
> 
> When launching a console, XDG_CURRENT_DESKTOP isn't guaranteed to be
> set. E.g. one can just switch to vt2 and login there, or one can run
> `sudo -i` which doesn't preserve the XDG_* environment variables.
> Losing the ability to type Greek because I used `sudo -i` wouldn't
> be appropriate.

The configuration typically does not happen when you launch a console;
with that approach /etc/default/keyboard would be already changed on
non-GNOME machines. So I don't think the absence of XDG_CURRENT_DESKTOP
in those situations matters.

>> Right. Super+Space is default on GNOME.
> 
> Up to now, /etc/default/keyboard allowed for defining a shortcut
> GLOBALLY, and the console, the display managers, and all the desktop
> environments respected that. Is supporting "a global shortcut" no
> longer a Debian/Ubuntu goal?

It's not unsupported. "dpkg-reconfigure keyboard-configuration" can be
run whenever you like.

What we know is that a global shortcut isn't compatible with the way
gnome-control-center currently works, since it may easily be overwritten
as soon as the user makes changes via Settings.

We also know that setting Alt+Shift prevents a user (at least on GNOME)
from using Alt+Shift+ shortcuts. So the previous default
came with that issue (which itself is a very old bug; see bug #36812).

And it's not obvious that just Alt+Shift is the best choice for a global
shortcut; many users would prefer Ctrl+Shift, CapsLock, or something
else.

Those three reasons make up the background for the changes made in
response to bug #1762952.

>> As regards the console, is there a use case which would be worth
>> to take into consideration where there is a need to switch to a
>> non-latin keyboard layout?
> 
> Normal PC usage is impossible without it. Some examples:
> 
> # Change directory to Desktop cd "Επιφάνεια εργασίας"
> 
> # Edit a file nano Αρχείο.txt
> 
> # Set a user's name usermod -c Άλκης alkisg

Those are tasks which I would accomplish with a terminal emulator such
as gnome-terminal, not a TTY console.

But I think the approach I propose (i.e. special case GNOME) may be a
bit complex code wise, and I'm disinclined to propose the actual code
changes. It didn't fall out well last time I tried to change the
console-setup package. :/

So we would need some involvement from Adam or someone else in the
~canonical-foundations team to evaluate whether the idea is sensible and
doable. Pinging some of them on IRC about this bug report might help
moving it forward.

-- 
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:
  New
Status in ubiquity package in Ubuntu:
  New

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 1756547] Re: LP refuses to import plural strings where e.g. msgstr[0] entries in PO file miss %d

2020-08-27 Thread Gunnar Hjalmarsson
@Marco: The issue was caused by the fact that LP used an older (xenial)
version of gettext. So as soon as they upgrade, it should be possible to
drop the workaround. Can't tell if they have done that yet; easiest to
ask Colin or William.

-- 
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:
  Fix Released

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 1892014] Re: 18.04.14.7 regression: no alt_shift_toggle in XKBOPTIONS

2020-08-26 Thread Gunnar Hjalmarsson
If you really read the comments at bug #1762952, you see that the
initially proposed change was limited in scope. However, it proved to
come with various regressions, so it landed in a solution where the
default shortcut for switching keyboard layout was changed in console-
setup from "Alt+Shift" to "No toggling".

But it did address incompatibility issues on Ubuntu/GNOME, so reverting
it to the old behavior would be bad.

Possibly console-setup could be modified again, so the default shortcut
depends on XDG_CURRENT_DESKTOP ("No toggling" for GNOME and "Alt+Shift"
for others). That way there wouldn't be a need to involve ubiquity or
other desktops.

@Adam: Do you think that would make sense?

On 2020-08-20 11:10, Alkis Georgopoulos wrote:
> I just tested on Ubuntu GNOME and I can't switch the layout with
> Alt+Shift.

Right. Super+Space is default on GNOME.

> I can switch it with Win+Space, which isn't appropriate for
> Greece.

That's reasonably about personal preferences rather than geographical.
Many users are used to something else but Super+Space, and on GNOME they
can either change it to something else or add some XKB based shortcut
via Tweaks.

> Also, I can't type Greek in neither the console nor in GDM.

Super+Space works for me in GDM. A prerequisite is that
/etc/default/keyboard includes more than one XKB layouts.

As regards the console, is there a use case which would be worth to take
into consideration where there is a need to switch to a non-latin
keyboard layout?

** Also affects: console-setup (Ubuntu)
   Importance: Undecided
   Status: New

-- 
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:
  New
Status in ubiquity package in Ubuntu:
  New

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 1890854] Re: Conflict with python2

2020-08-18 Thread Gunnar Hjalmarsson
Yeah, so it seems (or rather 4.20200804ubuntu2)

** Changed in: dh-python (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Conflict with python2

Status in dh-python package in Ubuntu:
  Fix Released
Status in dh-python package in Debian:
  Unknown

Bug description:
  During a package update in groovy I got this error message:

  Unpacking dh-python (4.20200804ubuntu1) over (4.20200315ubuntu1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-JUlowz/00-dh-python_4.20200804ubuntu1_all.deb (--unpack):
   trying to overwrite '/usr/share/debhelper/autoscripts/postinst-pycompile', 
which is also in package python2 2.7.17-2ubuntu4
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)

  +++

  Errors were encountered while processing:
   /tmp/apt-dpkg-install-JUlowz/00-dh-python_4.20200804ubuntu1_all.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dh-python/+bug/1890854/+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 1762952] Re: Alternative shortcut for layout switching Alt+Shift unexpectedly set by default

2020-08-18 Thread Gunnar Hjalmarsson
@Alkis: I added a comment on the new bug. Let's talk there. This one is
closed.

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

Title:
  Alternative shortcut for layout switching Alt+Shift unexpectedly set
  by default

Status in console-setup package in Ubuntu:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in console-setup source package in Bionic:
  Fix Released
Status in gnome-control-center source package in Bionic:
  Invalid

Bug description:
  [Impact]

  The keyboard-configuration package provides a tool for configuring the
  keyboard via /etc/default/keyboard. However, there are desktop GUIs
  which provide such tools as well, and in the case of gnome-control-
  center it has another idea of what /etc/default/keyboard should
  contain. In short: The different tools don't play well together.

  The proposed upload does not claim to fix all issues with this
  incompatibility. But one of the annoyances is that a pure upgrade of
  the keyboard-configuration package may result in a changed keyboard
  configuration without the user asking for it. The proposed upload does
  address that particular issue on desktop systems.

  [Test Case]

  1. On an Ubuntu 18.04 system, make sure that the contents of
 /etc/default/keyboard is 'the g-c-c style', for instance:

 XKBLAYOUT=se,us
 BACKSPACE=guess
 XKBVARIANT=,

  2. Reboot.

  3. Upgrade to the version of the keyboard-configuration package in
 bionic-proposed.

  => Find that /etc/default/keyboard was not changed through the
  upgrade.

  4. Run the command

 sudo dpkg-reconfigure keyboard-configuration

  => Find that you are now offered to change your keyboard
  configuration.

  [Regression Potential]

  As a result of this upload, and unlike before, no keyboard
  configuration will happen behind the scenes on a desktop system due to
  an upgrade of the keyboard-configuration package. This is the desired
  change, and I can't think of a case when a user would want the
  configuration to be changed without having asked for it.

  [Original description]

  Version: Ubuntu 18.04 Final Beta with default Gnome Shell included in
  18.04

  Steps to reproduce:
  1. Define two keyboard input methods in Settings -> Region & Language -> 
Input Sources
  2. Open several applications
  3. Observe that application windows can be iterated with Alt + Tab
  4. Once application window iteration was begun with Alt + Tab, try to iterate 
backwards with Alt + Shift + Tab.
  5. Try to change keyboard input method switching hotkeys in Settings -> 
Region & Language -> Input Sources -> Options.
  6. Observe that Keyboard shortcut for "Alternative switch to next source" is 
set to "Alt + Shift" and that keyboard shortcuts can only be changed in 
Settings -> Devices -> Keyboard -> Keyboard Shortcuts.
  7. Observe that the shortcut for "Alternative switch to next source" is not 
available for configuration in Settings -> Devices -> Keyboard -> Keyboard 
Shortcuts.

  Actual state:
  * Performing step 4 does not select the previous app in application switcher 
but instead changes  keyboard input method.

  Expected state:
  * The shortcut for "Alternative switch to next source" can be changed and / 
or deactivated in Settings -> Devices -> Keyboard -> Keyboard Shortcuts.

  Notes:
  * The above was working fine in Ubuntu 17.10. I assume "Alternative switch to 
next source" did not exist in that version of Gnome Shell.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1762952/+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 1716205] Re: slovak keyboard does not work in kde

2020-08-10 Thread Gunnar Hjalmarsson
This is a bit late, but can you please provide some additional info:

1. What's the output of this command:

   im-config -m

2. Can you create an additional user for test purposes, log in as that
   user, and let us know whether the problem is present also for that
   user.

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

Title:
  slovak keyboard does not work in kde

Status in ibus package in Ubuntu:
  Incomplete

Bug description:
  KDE Plasma 5.9.5. I have the Slovak QWERTY keyboard as the secondary
  one. However when I switch to SK keyboard I am not able to input
  slovak-based keys. It is as if the keyboard was not switched at all
  and the layout stays at US-EN. For example pressing + c should yield č
  but it instead prints +c. Previously this randomly failed in some
  apps, e.g. it worked in Libre Office Writer but did not work in
  Konsole; now it doesn't work at all. Pressing 3 should yield š but
  instead types 3.

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: ibus 1.5.14-2ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sun Sep 10 10:28:48 2017
  InstallationDate: Installed on 2014-03-07 (1282 days ago)
  InstallationMedia: Ubuntu-Server 13.04 "Raring Ringtail" - Release amd64 
(20130423.1)
  SourcePackage: ibus
  UpgradeStatus: Upgraded to zesty on 2017-03-29 (165 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1716205/+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 1882415] Re: Graphical artifact in top-right corner, owned by ibus-ui-gtk3

2020-08-08 Thread Gunnar Hjalmarsson
Keeping im-config out of launching and configuring IBus was reported in
comment #20 to be one way to get rid of the issue. Through im-config
0.45-1 we do just that, i.e. for GNOME desktops we leave the launch and
configuration of IBus to GNOME.

** Changed in: im-config (Ubuntu)
   Status: New => Fix Released

** No longer affects: gnome-shell (Ubuntu)

** No longer affects: ibus (Ubuntu)

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

Title:
  Graphical artifact in top-right corner, owned by ibus-ui-gtk3

Status in im-config package in Ubuntu:
  Fix Released

Bug description:
  Ubuntu 20.04, Gnome 3.36.2, Nvidia

  Small gray line in top-right corner.
  More precisely, it happens to be in the corner in 1920x1080 resolution. Not 
present in smaller resolutions. In panning mode it's fixed to panel, not screen.
  Present on the panel and on fullscreen windows but not in overview.
  Not clickable (prevents me from clicking button underneath it).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2014-11-12 (2037 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 
(20141022.1)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-37.41-lowlatency 5.4.41
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
  Tags:  focal
  Uname: Linux 5.4.0-37-lowlatency x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-01 (40 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1882415/+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 1890854] [NEW] Conflict with python2

2020-08-07 Thread Gunnar Hjalmarsson
Public bug reported:

During a package update in groovy I got this error message:

Unpacking dh-python (4.20200804ubuntu1) over (4.20200315ubuntu1) ...
dpkg: error processing archive 
/tmp/apt-dpkg-install-JUlowz/00-dh-python_4.20200804ubuntu1_all.deb (--unpack):
 trying to overwrite '/usr/share/debhelper/autoscripts/postinst-pycompile', 
which is also in package python2 2.7.17-2ubuntu4
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)

+++

Errors were encountered while processing:
 /tmp/apt-dpkg-install-JUlowz/00-dh-python_4.20200804ubuntu1_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

** Affects: dh-python (Ubuntu)
 Importance: High
 Status: New

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

Title:
  Conflict with python2

Status in dh-python package in Ubuntu:
  New

Bug description:
  During a package update in groovy I got this error message:

  Unpacking dh-python (4.20200804ubuntu1) over (4.20200315ubuntu1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-JUlowz/00-dh-python_4.20200804ubuntu1_all.deb (--unpack):
   trying to overwrite '/usr/share/debhelper/autoscripts/postinst-pycompile', 
which is also in package python2 2.7.17-2ubuntu4
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)

  +++

  Errors were encountered while processing:
   /tmp/apt-dpkg-install-JUlowz/00-dh-python_4.20200804ubuntu1_all.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dh-python/+bug/1890854/+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 1863080] Re: Unable to use dead keys in Java apps

2020-08-05 Thread Gunnar Hjalmarsson
Upstream didn't acknowledge it as a valid bug, so we are back at square
one.

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

Title:
  Unable to use dead keys in Java apps

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

Bug description:
  This is same bug as #540751, as it happens again in Ubuntu 19.10 with
  Java 11. Way of reproduce it:

  - Fresh Ubuntu 19.10 install.
  - Install default-jre.
  - Download (for example) lastest NetBeans version.
  - Edit a file in NetBeans, you can't insert characters like 'á'.

  The workaround is the same, define XMODIFIERS='' before launching the
  app.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ibus/+bug/1863080/+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 1580463] Re: Snap blocks access to system input methods (ibus, fcitx, ...)

2020-08-04 Thread Gunnar Hjalmarsson
@Rüdiger: Quite some water has passed under the bridge since the
submission of this bug. It mostly came to be about the method for
achieving a distinguishable abstract path for IBus, and is now closed.

I would suggest that you file a new bug about the issue you now
encounter. It sounds like an apparmor issue to me, and bug #1856738 is
possibly related.

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

Title:
  Snap blocks access to system input methods (ibus, fcitx, ...)

Status in ibus:
  Fix Released
Status in apparmor package in Ubuntu:
  Fix Released
Status in ibus package in Ubuntu:
  Fix Released
Status in im-config package in Ubuntu:
  Fix Released
Status in snapd package in Ubuntu:
  Fix Released
Status in apparmor source package in Xenial:
  Fix Released
Status in im-config source package in Xenial:
  Fix Released
Status in snapd source package in Xenial:
  Fix Released
Status in apparmor source package in Yakkety:
  Fix Released
Status in im-config source package in Yakkety:
  Fix Released
Status in snapd source package in Yakkety:
  Fix Released

Bug description:
  = SRU im-config =
  [Impact]
  ibus-daemon by default uses a unix socket name of /tmp/dbus-... that is 
indistinguishable from dbus-daemon abstract sockets. While dbus-daemon has 
AppArmor mediation, ibus-daemon does not so it is important that its abstract 
socket not be confused with dbus-daemon's. By modifying ibus-daemon's start 
arguments to use "--address 'unix:tmpdir=/tmp/ibus'" AppArmor can continue 
mediating DBus abstract sockets like normal and also mediate access to the 
ibus-daemon-specific abstract socket via unix rules. This also tidies up the 
abstract socket paths so that it is clear which are for ibus-daemon, which for 
dbus-daemon, etc.

  The upload simply adjusts 21_ibus.rc to start ibus-daemon with "--
  address 'unix:tmpdir=/tmp/ibus'" and adds a comment. No compiled code
  changes are required.

  [Test Case]
  1. start a unity session before updating to the package in -proposed

  2. $ grep IBUS_ADDRESS ~/.config/ibus/bus/*-unix-0
  
IBUS_ADDRESS=unix:abstract=/tmp/dbus-Vyx8fGFA,guid=28e8e7e89f902c8d4e9d77c5557add76

  3. $ lsof -p $(pidof ibus-daemon) | grep '/dbus'
  ibus-daem 2973 jamie8u unix 0x  0t0   29606 
@/tmp/dbus-oxKYpN30 type=STREAM

  4. update the package in -proposed and perform '2' and '3'. The
  IBUS_ADDRESSES should be the same as before

  5. logout of unity, then log back in

  6. $ grep IBUS_ADDRESS ~/.config/ibus/bus/*-unix-0
  
IBUS_ADDRESS=unix:abstract=/tmp/ibus/dbus-SpxOl8Fc,guid=06d4bbeb07614c6dffbf221c57473f4e

  (notice '/tmp/ibus/' in the path)

  7. $ lsof -p $(pidof ibus-daemon) | grep '/dbus'
  ibus-daem 3471 jamie8u unix 0x  0t0  26107 
@/tmp/ibus/dbus-SpxOl8Fc type=STREAM
  ...

  (notice '@/tmp/ibus/' in the path)

  In addition to the above, you can test for regressions by opening
  'System Settings' under the 'gear' icon in the panel and selecting
  'Text Entry'. From there, add an input source on the right, make sure
  'Show current input source in the menu bar' is checked, then use the
  input source panel indicator to change input sources.

  Extended test case to verify input support still works in unconfined
  and confined applications:

  1. Systems Settings Language Support, if prompted install the complete 
language support
  2. Install Chinese (simple and traditional)
  3. sudo apt-get install ibus-pinyin ibus-sunpinyin
  4. logout / login
  5. System Settings / Text Entry - add Chinese (Pinyin) (IBus)
  6. select pinyin from the indicator
  7. sudo lsof | grep ibus | grep @ # will use @/tmp/dbus-...
  8. open gnome-calculator and try to type something in (should get a pop-up)
  9. open evince and try to search a pdf (should get a pop up)
  10. upgrade apparmor and im-config from xenial-proposed
  11. logout and back in
  12. sudo lsof | grep ibus | grep @ # will use @/tmp/ibus/...
  13. open gnome-calculator and try to type something in (should get a pop-up)
  14. open evince and try to search a pdf (should get a pop up)
  15. verify no new apparmor denials

  [Regression Potential]

  The regression potential is considered low because there are no
  compiled code changes and because the changes only occur after ibus-
  daemon is restarted, which is upon session start, not package upgrade.
  When it is restarted, the files in ~/.config/ibus/bus/*-unix-0 are
  updated accordingly for other applications to pick up.

  This change intentionally requires a change to the unity7 snapd
  interface, which is in already done.

  This change intentionally requires a change to apparmor to add a unix
  rule for communicating with the new ibus address. This is in xenial-
  proposed 2.10.95-0ubuntu2.3 (and 2.10.95-0ubuntu2.4). The packages
  changes to im-config use 'Breaks: apparmor (<< 

[Touch-packages] [Bug 1888092] Re: package ibus-data 1.5.22-2ubuntu2 failed to install/upgrade: unable to make backup link of './usr/share/ibus/dicts/emoji-af.dict' before installing new version: Inpu

2020-07-18 Thread Gunnar Hjalmarsson
That sounds as a hardware glitch. If you haven't already, can you please
try:

sudo apt install --reinstall ibus-data

and let us know if it 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/1888092

Title:
  package ibus-data 1.5.22-2ubuntu2 failed to install/upgrade: unable to
  make backup link of './usr/share/ibus/dicts/emoji-af.dict' before
  installing new version: Input/output error

Status in ibus package in Ubuntu:
  Incomplete

Bug description:
  I have problems while install ubuntu 20.04

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: ibus-data 1.5.22-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sat Jul 18 22:43:47 2020
  DuplicateSignature:
   package:ibus-data:1.5.22-2ubuntu2
   Unpacking ibus-data (1.5.22-2ubuntu2.1) over (1.5.22-2ubuntu2) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-W4DEHL/31-ibus-data_1.5.22-2ubuntu2.1_all.deb (--unpack):
unable to make backup link of './usr/share/ibus/dicts/emoji-af.dict' before 
installing new version: Input/output error
  ErrorMessage: unable to make backup link of 
'./usr/share/ibus/dicts/emoji-af.dict' before installing new version: 
Input/output error
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: ibus
  Title: package ibus-data 1.5.22-2ubuntu2 failed to install/upgrade: unable to 
make backup link of './usr/share/ibus/dicts/emoji-af.dict' before installing 
new version: Input/output error
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1888092/+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 1863080] Re: Unable to use dead keys in Java apps

2020-07-13 Thread Gunnar Hjalmarsson
** Also affects: ibus via
   https://github.com/ibus/ibus/issues/2237
   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/1863080

Title:
  Unable to use dead keys in Java apps

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

Bug description:
  This is same bug as #540751, as it happens again in Ubuntu 19.10 with
  Java 11. Way of reproduce it:

  - Fresh Ubuntu 19.10 install.
  - Install default-jre.
  - Download (for example) lastest NetBeans version.
  - Edit a file in NetBeans, you can't insert characters like 'á'.

  The workaround is the same, define XMODIFIERS='' before launching the
  app.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ibus/+bug/1863080/+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 1887252] Re: lightdm config-error-dialog.sh should pass --no-markup

2020-07-11 Thread Gunnar Hjalmarsson
Second thoughts...

The --no-markup option prevents zenity from interpreting \n which makes
the dialog hard to read in most cases. So only adding --no-markup is not
a viable solution.

As a possible alternative I played with sed() a bit. The script includes
this line:

TEXT="$PARA1\n\n$(fold -s $ERR)\n\n$PARA2"

My thought is to add a new line right after that. Something along these
lines:

TEXT=$(printf '%s' "$TEXT" | sed 's/ Incomplete

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

** Summary changed:

- lightdm config-error-dialog.sh should pass --no-markup
+ config-error-dialog.sh should pass --no-markup

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

Title:
  config-error-dialog.sh should pass --no-markup

Status in gdm3 package in Ubuntu:
  Incomplete
Status in lightdm package in Ubuntu:
  Incomplete

Bug description:
  I modified my ~/.profile to call "logger". This resulted in in
  producing some output on stderr like

  ```
  <13>Jul 11 13:02:46 /usr/sbin/lightdm-session[1408]: profile sourced ...
  ```

  This showed an empty zenity prompt.

  Logs suggest zenity was failing because it was treating `<13>` as
  pango markup.

  ```
   from markup due to error parsing markup: Error on line 3 char 6: “13” is not 
a valid 
  ```

  We should not assume the error message strings contain valid markup,
  since their source is unknown.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1887252/+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 1887252] Re: lightdm config-error-dialog.sh should pass --no-markup

2020-07-11 Thread Gunnar Hjalmarsson
Thanks for your report. Using the --no-markup option sounds reasonable
to me.

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

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

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

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

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

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

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

Title:
  lightdm config-error-dialog.sh should pass --no-markup

Status in gdm3 package in Ubuntu:
  In Progress
Status in lightdm package in Ubuntu:
  In Progress

Bug description:
  I modified my ~/.profile to call "logger". This resulted in in
  producing some output on stderr like

  ```
  <13>Jul 11 13:02:46 /usr/sbin/lightdm-session[1408]: profile sourced ...
  ```

  This showed an empty zenity prompt.

  Logs suggest zenity was failing because it was treating `<13>` as
  pango markup.

  ```
   from markup due to error parsing markup: Error on line 3 char 6: “13” is not 
a valid 
  ```

  We should not assume the error message strings contain valid markup,
  since their source is unknown.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1887252/+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 1885914] Re: Drop obsolete Unicode patch

2020-07-08 Thread Gunnar Hjalmarsson
I verified the test case using version 1.5.22-2ubuntu2.1 of the ibus
packages from focal-proposed.

Also confirmed that Ctrl+Shift+u works as expected when the unicode-
hotkey dconf value is set to default.


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

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

Title:
  Drop obsolete Unicode patch

Status in ibus package in Ubuntu:
  Fix Released
Status in ibus source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  The Ubuntu 20.04 IBus version includes a patch, which was necessary in
  18.04 to make the Ctrl+Shift+u shortcut work, but which has become
  obsolete later. Currently it prevents users from replacing
  Ctrl+Shift+u with some other shortcut to avoid conflicts with other
  applications.

  See also:
  * Bug #1885749
  * https://github.com/ibus/ibus/issues/2163

  In the proposed upload that patch has been dropped.

  [Test Case]

  1. Launch ibus-setup and navigate to the Emoji tab.
  2. Change the Unicode code point shortcut to something else.
  3. Find that the original shortcut is still effective.
  4. Install the ibus packages from focal-proposed.
  5. Repeat 1. and 2.
  6. Find that the new shortcut works while the original
 shortcut no longer works.

  [Regression Potential]

  Important to confirm that the default Ctrl+Shift+u shortcut works as
  intended without the patch. Otherwise the regression risk should be
  low.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1885914/+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 1885749] Re: Enhancement: Remove default Emoji shortcuts

2020-07-01 Thread Gunnar Hjalmarsson
I submitted bug #1885914, which is somewhat related to this one.

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

Title:
  Enhancement: Remove default Emoji shortcuts

Status in ibus package in Ubuntu:
  Won't Fix

Bug description:
  Current Situation
  ===

  (1) 
  Per default ibus preferences are hidden in Ubuntu
  (I would say it's very difficult to reach ibus feature)

  (2) 
  ibus has two default shortcuts, apparently for Emoji-something: 
 - Ctrl+shift+e 
 - Ctrl+shift+u

  (2.1) 
  These shortcuts can prevent shortcuts from other applications being used (one 
example: VSCode's "show files"

  (2.2) 
  Because of (1) it's extremely difficult to change these shortcuts, if they 
cause any problems - Especially because of (2.3).

  (2.3) 
  The user has no way of knowing that ibus introduced these shortcuts (because 
they would only use Settings->Region & Language, which does not show any 
shortcut options)

  (3)
  I guess the Emoji shortcuts ( (2) ) have no benefit for a normal user. Reason 
(guess): The normal user would not understand what to do after pressing the 
shortcut)

  
  Suggestion
  
  Remove shortcuts as a default setting

  
  Misc
  
  - Why is this bug not filed in github.com/ibus/ibus/issues?
-> Because in ibus as standalone, where the user has a direction connection 
to it, it might make sense to keep the shortcuts. For the moment I would say 
this is a Ubuntu related issue, as ubuntu is hiding the dialog. (... why is the 
dialog gui even installed, if we don't was to show it? ...)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ibus 1.5.22-2ubuntu2 [modified: 
usr/share/applications/org.freedesktop.IBus.Setup.desktop]
  ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41
  Uname: Linux 5.4.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul  1 00:55:25 2020
  InstallationDate: Installed on 2020-06-29 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  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/1885749/+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 1885914] Re: Drop obsolete Unicode patch

2020-07-01 Thread Gunnar Hjalmarsson
** Patch added: "ibus_lp1885914_focal.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1885914/+attachment/5388729/+files/ibus_lp1885914_focal.debdiff

** Tags added: patch

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

Title:
  Drop obsolete Unicode patch

Status in ibus package in Ubuntu:
  Fix Released
Status in ibus source package in Focal:
  In Progress

Bug description:
  [Impact]

  The Ubuntu 20.04 IBus version includes a patch, which was necessary in
  18.04 to make the Ctrl+Shift+u shortcut work, but which has become
  obsolete later. Currently it prevents users from replacing
  Ctrl+Shift+u with some other shortcut to avoid conflicts with other
  applications.

  See also:
  * Bug #1885749
  * https://github.com/ibus/ibus/issues/2163

  In the proposed upload that patch has been dropped.

  [Test Case]

  1. Launch ibus-setup and navigate to the Emoji tab.
  2. Change the Unicode code point shortcut to something else.
  3. Find that the original shortcut is still effective.
  4. Install the ibus packages from focal-proposed.
  5. Repeat 1. and 2.
  6. Find that the new shortcut works while the original
 shortcut no longer works.

  [Regression Potential]

  Important to confirm that the default Ctrl+Shift+u shortcut works as
  intended without the patch. Otherwise the regression risk should be
  low.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1885914/+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 1885914] [NEW] Drop obsolete Unicode patch

2020-07-01 Thread Gunnar Hjalmarsson
Public bug reported:

[Impact]

The Ubuntu 20.04 IBus version includes a patch, which was necessary in
18.04 to make the Ctrl+Shift+u shortcut work, but which has become
obsolete later. Currently it prevents users from replacing Ctrl+Shift+u
with some other shortcut to avoid conflicts with other applications.

See also:
* Bug #1885749
* https://github.com/ibus/ibus/issues/2163

In the proposed upload that patch has been dropped.

[Test Case]

1. Launch ibus-setup and navigate to the Emoji tab.
2. Change the Unicode code point shortcut to something else.
3. Find that the original shortcut is still effective.
4. Install the ibus packages from focal-proposed.
5. Repeat 1. and 2.
6. Find that the new shortcut works while the original
   shortcut no longer works.

[Regression Potential]

Important to confirm that the default Ctrl+Shift+u shortcut works as
intended without the patch. Otherwise the regression risk should be low.

** Affects: ibus (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Affects: ibus (Ubuntu Focal)
 Importance: Medium
 Assignee: Gunnar Hjalmarsson (gunnarhj)
 Status: In Progress

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

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

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

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

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

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

Title:
  Drop obsolete Unicode patch

Status in ibus package in Ubuntu:
  Fix Released
Status in ibus source package in Focal:
  In Progress

Bug description:
  [Impact]

  The Ubuntu 20.04 IBus version includes a patch, which was necessary in
  18.04 to make the Ctrl+Shift+u shortcut work, but which has become
  obsolete later. Currently it prevents users from replacing
  Ctrl+Shift+u with some other shortcut to avoid conflicts with other
  applications.

  See also:
  * Bug #1885749
  * https://github.com/ibus/ibus/issues/2163

  In the proposed upload that patch has been dropped.

  [Test Case]

  1. Launch ibus-setup and navigate to the Emoji tab.
  2. Change the Unicode code point shortcut to something else.
  3. Find that the original shortcut is still effective.
  4. Install the ibus packages from focal-proposed.
  5. Repeat 1. and 2.
  6. Find that the new shortcut works while the original
 shortcut no longer works.

  [Regression Potential]

  Important to confirm that the default Ctrl+Shift+u shortcut works as
  intended without the patch. Otherwise the regression risk should be
  low.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1885914/+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 1885749] Re: Enhancement: Remove default Emoji shortcuts

2020-07-01 Thread Gunnar Hjalmarsson
@Sebastien: Hmm.. That upstream issue talks about Ctrl+. which is a
shortcut I was unaware of. It's apparently something else but
Ctrl+Shift+e, where IBus is involved somehow, and which just as
Ctrl+Shift+u conflicts with shortcuts in certain applications as the OP
pointed out in the bug description.

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

Title:
  Enhancement: Remove default Emoji shortcuts

Status in ibus package in Ubuntu:
  Won't Fix

Bug description:
  Current Situation
  ===

  (1) 
  Per default ibus preferences are hidden in Ubuntu
  (I would say it's very difficult to reach ibus feature)

  (2) 
  ibus has two default shortcuts, apparently for Emoji-something: 
 - Ctrl+shift+e 
 - Ctrl+shift+u

  (2.1) 
  These shortcuts can prevent shortcuts from other applications being used (one 
example: VSCode's "show files"

  (2.2) 
  Because of (1) it's extremely difficult to change these shortcuts, if they 
cause any problems - Especially because of (2.3).

  (2.3) 
  The user has no way of knowing that ibus introduced these shortcuts (because 
they would only use Settings->Region & Language, which does not show any 
shortcut options)

  (3)
  I guess the Emoji shortcuts ( (2) ) have no benefit for a normal user. Reason 
(guess): The normal user would not understand what to do after pressing the 
shortcut)

  
  Suggestion
  
  Remove shortcuts as a default setting

  
  Misc
  
  - Why is this bug not filed in github.com/ibus/ibus/issues?
-> Because in ibus as standalone, where the user has a direction connection 
to it, it might make sense to keep the shortcuts. For the moment I would say 
this is a Ubuntu related issue, as ubuntu is hiding the dialog. (... why is the 
dialog gui even installed, if we don't was to show it? ...)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ibus 1.5.22-2ubuntu2 [modified: 
usr/share/applications/org.freedesktop.IBus.Setup.desktop]
  ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41
  Uname: Linux 5.4.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul  1 00:55:25 2020
  InstallationDate: Installed on 2020-06-29 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  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/1885749/+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 1885749] Re: Enhancement: Remove default Emoji shortcuts

2020-07-01 Thread Gunnar Hjalmarsson
$ gsettings get org.freedesktop.ibus.panel.emoji unicode-hotkey
['u']
$ gsettings get org.freedesktop.ibus.panel.emoji hotkey
['e']

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

Title:
  Enhancement: Remove default Emoji shortcuts

Status in ibus package in Ubuntu:
  Won't Fix

Bug description:
  Current Situation
  ===

  (1) 
  Per default ibus preferences are hidden in Ubuntu
  (I would say it's very difficult to reach ibus feature)

  (2) 
  ibus has two default shortcuts, apparently for Emoji-something: 
 - Ctrl+shift+e 
 - Ctrl+shift+u

  (2.1) 
  These shortcuts can prevent shortcuts from other applications being used (one 
example: VSCode's "show files"

  (2.2) 
  Because of (1) it's extremely difficult to change these shortcuts, if they 
cause any problems - Especially because of (2.3).

  (2.3) 
  The user has no way of knowing that ibus introduced these shortcuts (because 
they would only use Settings->Region & Language, which does not show any 
shortcut options)

  (3)
  I guess the Emoji shortcuts ( (2) ) have no benefit for a normal user. Reason 
(guess): The normal user would not understand what to do after pressing the 
shortcut)

  
  Suggestion
  
  Remove shortcuts as a default setting

  
  Misc
  
  - Why is this bug not filed in github.com/ibus/ibus/issues?
-> Because in ibus as standalone, where the user has a direction connection 
to it, it might make sense to keep the shortcuts. For the moment I would say 
this is a Ubuntu related issue, as ubuntu is hiding the dialog. (... why is the 
dialog gui even installed, if we don't was to show it? ...)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ibus 1.5.22-2ubuntu2 [modified: 
usr/share/applications/org.freedesktop.IBus.Setup.desktop]
  ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41
  Uname: Linux 5.4.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul  1 00:55:25 2020
  InstallationDate: Installed on 2020-06-29 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  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/1885749/+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 1885749] Re: Enhancement: Remove default Emoji shortcuts

2020-06-30 Thread Gunnar Hjalmarsson
Thanks for your report.

The conflict you point at is unfortunate. Nevertheless, removing those
shortcuts is not an option. Especially Ctrl+Shift+u is a well
established method on Linux to type characters which are not available
via the keyboard layout you are using:

https://help.ubuntu.com/stable/ubuntu-help/tips-
specialchars.html#ctrlshiftu

Ctrl+Shift+e is newer, but probably used and appreciated by many users.

Your bug makes me think of this IBus issue:

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

That proved to be an Ubuntu specific bug which has been fixed in groovy
but not (yet) in focal. Fixing it in focal would be a way to improve the
situation. If you want that to happen, please file an ibus bug as I
suggested in my latest comment at that issue.

I think you make a too big deal of the fact that ibus-setup is not
searchable in Ubuntu. It's not an Ubuntu specific thing, btw, but it's
the same for GNOME irrespective of distro:

https://github.com/ibus/ibus/commit/66141bbc

Alt+F2 followed by ibus-setup is not "extremely difficult". But indeed,
you need be aware of the possibility to change it that way.

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

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

Title:
  Enhancement: Remove default Emoji shortcuts

Status in ibus package in Ubuntu:
  New

Bug description:
  Current Situation
  ===

  (1) 
  Per default ibus preferences are hidden in Ubuntu
  (I would say it's very difficult to reach ibus feature)

  (2) 
  ibus has two default shortcuts, apparently for Emoji-something: 
 - Ctrl+shift+e 
 - Ctrl+shift+u

  (2.1) 
  These shortcuts can prevent shortcuts from other applications being used (one 
example: VSCode's "show files"

  (2.2) 
  Because of (1) it's extremely difficult to change these shortcuts, if they 
cause any problems - Especially because of (2.3).

  (2.3) 
  The user has no way of knowing that ibus introduced these shortcuts (because 
they would only use Settings->Region & Language, which does not show any 
shortcut options)

  (3)
  I guess the Emoji shortcuts ( (2) ) have no benefit for a normal user. Reason 
(guess): The normal user would not understand what to do after pressing the 
shortcut)

  
  Suggestion
  
  Remove shortcuts as a default setting

  
  Misc
  
  - Why is this bug not filed in github.com/ibus/ibus/issues?
-> Because in ibus as standalone, where the user has a direction connection 
to it, it might make sense to keep the shortcuts. For the moment I would say 
this is a Ubuntu related issue, as ubuntu is hiding the dialog. (... why is the 
dialog gui even installed, if we don't was to show it? ...)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ibus 1.5.22-2ubuntu2 [modified: 
usr/share/applications/org.freedesktop.IBus.Setup.desktop]
  ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41
  Uname: Linux 5.4.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul  1 00:55:25 2020
  InstallationDate: Installed on 2020-06-29 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  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/1885749/+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 1855514] Re: ibus preferences do not show up in search or indicator bar

2020-06-29 Thread Gunnar Hjalmarsson
Ubuntu is a distribution, and most software included in Ubuntu is
originally developed and maintained elsewhere ("upstream").

An IBus bug would be filed at . If
you do, you may want to refer to the issue I mentioned and which was
closed by the upstream maintainer.

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

Title:
  ibus preferences do not show up in search or indicator bar

Status in ibus package in Ubuntu:
  Opinion

Bug description:
  This might be two separate bugs. But I feel like they have the same
  root, so I reported them as one.

  Remarks:
  [1] This report is *not* related to bug 1854610 in ibus-anthy (Ubuntu) "No 
Japanese input possible after upgrade from 19.04 to 19.10" [Undecided,New] 
https://launchpad.net/bugs/1854610

  [2] This report might be related to
  https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1580463, but I'm
  not sure. Someone with more technical knowledge should look into this.

   1 ---
  steps to reproduce:
  1) Have a fresh ubuntu 19.10 installation
  2) install ibus and ibus-anthy
  3) press windows key to open all applications
  4) type in ibus

  Actual:
  5) ibus settings will not show up

  Expected:
  5) ibus settings show up

  Workaround:
  6) open Software center
  7) search for ibus
  8) click "launch there"

   2 --
  steps to reproduce:
  1) Have a fresh Ubuntu 19.10 installation
  2) install ibus and ibus-anthy
  3) Set input method to "ibus"
  4) restart

  Actual:
  5) ibus preferences do not show up in the top bar at the indicators

  Expected
  6) "ibus preferences" is visible at the top bar inside the indicators area.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ibus 1.5.21-1~exp2ubuntu2
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec  7 13:10:27 2019
  SourcePackage: ibus
  UpgradeStatus: no upgrade log present

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1855514/+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 1855514] Re: ibus preferences do not show up in search or indicator bar

2020-06-29 Thread Gunnar Hjalmarsson
It's not that ibus-setup is disabled, but since its core functionality
is replaced by Settings on an Ubuntu desktop, we have chosen to hide it
to prevent confusion.

I would consider the examples you mention as advanced configuration. You
can still open it using e.g. + and enter ibus-setup. Ideally
there should be a GNOME specific ibus-setup GUI with a limited set of
components. I proposed that recently, but was turned down:

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

Nevertheless, the way to change it would be to make upstream change
their mind.

But as regards this bug report, i.e. the fact that ibus-setup is
excluded in Activities searches and not visible in the top bar, they are
not Ubuntu bugs but intended behavior. Re-closing.

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

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

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

Title:
  ibus preferences do not show up in search or indicator bar

Status in ibus package in Ubuntu:
  Opinion

Bug description:
  This might be two separate bugs. But I feel like they have the same
  root, so I reported them as one.

  Remarks:
  [1] This report is *not* related to bug 1854610 in ibus-anthy (Ubuntu) "No 
Japanese input possible after upgrade from 19.04 to 19.10" [Undecided,New] 
https://launchpad.net/bugs/1854610

  [2] This report might be related to
  https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1580463, but I'm
  not sure. Someone with more technical knowledge should look into this.

   1 ---
  steps to reproduce:
  1) Have a fresh ubuntu 19.10 installation
  2) install ibus and ibus-anthy
  3) press windows key to open all applications
  4) type in ibus

  Actual:
  5) ibus settings will not show up

  Expected:
  5) ibus settings show up

  Workaround:
  6) open Software center
  7) search for ibus
  8) click "launch there"

   2 --
  steps to reproduce:
  1) Have a fresh Ubuntu 19.10 installation
  2) install ibus and ibus-anthy
  3) Set input method to "ibus"
  4) restart

  Actual:
  5) ibus preferences do not show up in the top bar at the indicators

  Expected
  6) "ibus preferences" is visible at the top bar inside the indicators area.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ibus 1.5.21-1~exp2ubuntu2
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec  7 13:10:27 2019
  SourcePackage: ibus
  UpgradeStatus: no upgrade log present

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1855514/+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 1882415] Re: Graphical artifact in top-right corner, owned by ibus-ui-gtk3

2020-06-17 Thread Gunnar Hjalmarsson
On 2020-06-17 15:31, vasdi wrote:
> It does not affect new users.

That's important (and explains why I failed to reproduce the issue). So
it's something in your $HOME which causes it.

It may be some subtle thing somewhere in e.g. your ~/.cache folder. If
you like, you can rename that folder:

mv ~/.cache ~/.cache.old

and relogin.

The issue you experienced is probably some sort of bug. I'm not sure,
though, if it's practicable to figure out exactly what the problem is
and how it happened.

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

Title:
  Graphical artifact in top-right corner, owned by ibus-ui-gtk3

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

Bug description:
  Ubuntu 20.04, Gnome 3.36.2, Nvidia

  Small gray line in top-right corner.
  More precisely, it happens to be in the corner in 1920x1080 resolution. Not 
present in smaller resolutions. In panning mode it's fixed to panel, not screen.
  Present on the panel and on fullscreen windows but not in overview.
  Not clickable (prevents me from clicking button underneath it).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2014-11-12 (2037 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 
(20141022.1)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-37.41-lowlatency 5.4.41
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
  Tags:  focal
  Uname: Linux 5.4.0-37-lowlatency x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-01 (40 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1882415/+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 1882415] Re: Graphical artifact in top-right corner, owned by ibus-ui-gtk3

2020-06-16 Thread Gunnar Hjalmarsson
Good. That discussion appears to be held above my head, so I'm going to
keep quiet there. All I can say is that I was able to reproduce the
issue in groovy.

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

Title:
  Graphical artifact in top-right corner, owned by ibus-ui-gtk3

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

Bug description:
  Ubuntu 20.04, Gnome 3.36.2, Nvidia

  Small gray line in top-right corner.
  More precisely, it happens to be in the corner in 1920x1080 resolution. Not 
present in smaller resolutions. In panning mode it's fixed to panel, not screen.
  Present on the panel and on fullscreen windows but not in overview.
  Not clickable (prevents me from clicking button underneath it).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2014-11-12 (2037 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 
(20141022.1)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-37.41-lowlatency 5.4.41
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
  Tags:  focal
  Uname: Linux 5.4.0-37-lowlatency x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-01 (40 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1882415/+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 1882415] Re: Graphical artifact in top-right corner, owned by ibus-ui-gtk3

2020-06-16 Thread Gunnar Hjalmarsson
https://gitlab.gnome.org/GNOME/mutter/-/issues/948

** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #948
   https://gitlab.gnome.org/GNOME/mutter/-/issues/948

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

Title:
  Graphical artifact in top-right corner, owned by ibus-ui-gtk3

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

Bug description:
  Ubuntu 20.04, Gnome 3.36.2, Nvidia

  Small gray line in top-right corner.
  More precisely, it happens to be in the corner in 1920x1080 resolution. Not 
present in smaller resolutions. In panning mode it's fixed to panel, not screen.
  Present on the panel and on fullscreen windows but not in overview.
  Not clickable (prevents me from clicking button underneath it).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2014-11-12 (2037 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 
(20141022.1)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-37.41-lowlatency 5.4.41
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
  Tags:  focal
  Uname: Linux 5.4.0-37-lowlatency x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-01 (40 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1882415/+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 1882415] Re: Graphical artifact in top-right corner, owned by ibus-ui-gtk3

2020-06-16 Thread Gunnar Hjalmarsson
@Daniel: The regression caused by the mutter MR I mentioned in comment
#21 is bad for ibus-hangul users (Korean input). Any chance you can take
a look at it?

Besides fixing that ibus-hangul issue, doing so would make it possible
to stop setting GTK_IM_MODULE=ibus on GNOME desktops, which is something
I believe would be desirable for other reasons but this bug.

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

Title:
  Graphical artifact in top-right corner, owned by ibus-ui-gtk3

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

Bug description:
  Ubuntu 20.04, Gnome 3.36.2, Nvidia

  Small gray line in top-right corner.
  More precisely, it happens to be in the corner in 1920x1080 resolution. Not 
present in smaller resolutions. In panning mode it's fixed to panel, not screen.
  Present on the panel and on fullscreen windows but not in overview.
  Not clickable (prevents me from clicking button underneath it).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2014-11-12 (2037 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 
(20141022.1)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-37.41-lowlatency 5.4.41
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
  Tags:  focal
  Uname: Linux 5.4.0-37-lowlatency x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-01 (40 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1882415/+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 1882415] Re: Graphical artifact in top-right corner, owned by ibus-ui-gtk3

2020-06-16 Thread Gunnar Hjalmarsson
Interesting. That speaks for two possible ways to fix the issue:

1. Fix it in the IBus source somehow.

2. Stop setting GTK_IM_MODULE also on Xorg (we already don't set it on Wayland)
   in case of a GNOME desktop, which would be a change to the im-config package.

Doing 2. may come with other issues for IM users, though. GNOME's
integration of IBus may not be mature enough to rely on it 100%. The
regression caused by
 is one
example of the latter.

So the issue is a bit complex. Adding the rls-gg-incoming tag to call
the desktop team's attention to it.

** Tags added: rls-gg-incoming

** Also affects: im-config (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Graphical artifact in top-right corner, owned by ibus-ui-gtk3

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

Bug description:
  Ubuntu 20.04, Gnome 3.36.2, Nvidia

  Small gray line in top-right corner.
  More precisely, it happens to be in the corner in 1920x1080 resolution. Not 
present in smaller resolutions. In panning mode it's fixed to panel, not screen.
  Present on the panel and on fullscreen windows but not in overview.
  Not clickable (prevents me from clicking button underneath it).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2014-11-12 (2037 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 
(20141022.1)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-37.41-lowlatency 5.4.41
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
  Tags:  focal
  Uname: Linux 5.4.0-37-lowlatency x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-01 (40 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1882415/+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 1882415] Re: Graphical artifact in top-right corner, owned by ibus-ui-gtk3

2020-06-15 Thread Gunnar Hjalmarsson
@vasdi: Thanks. Then, as an experiment, can you please open Language
Support, select "none" as the "Keyboard input method system" instead if
"IBus", and reboot. That will make fewer of those variables being set -
most importantly GTK_IM_MODULE will be unset - which makes GNOME handle
IBus slightly different behind the scenes.

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

Title:
  Graphical artifact in top-right corner, owned by ibus-ui-gtk3

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

Bug description:
  Ubuntu 20.04, Gnome 3.36.2, Nvidia

  Small gray line in top-right corner.
  More precisely, it happens to be in the corner in 1920x1080 resolution. Not 
present in smaller resolutions. In panning mode it's fixed to panel, not screen.
  Present on the panel and on fullscreen windows but not in overview.
  Not clickable (prevents me from clicking button underneath it).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2014-11-12 (2037 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 
(20141022.1)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-37.41-lowlatency 5.4.41
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
  Tags:  focal
  Uname: Linux 5.4.0-37-lowlatency x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-01 (40 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1882415/+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 1882415] Re: Graphical artifact in top-right corner, owned by ibus-ui-gtk3

2020-06-15 Thread Gunnar Hjalmarsson
@Daniel: I'm not sure either. Thought it could be wise to keep an open
mind until we are.

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

Title:
  Graphical artifact in top-right corner, owned by ibus-ui-gtk3

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

Bug description:
  Ubuntu 20.04, Gnome 3.36.2, Nvidia

  Small gray line in top-right corner.
  More precisely, it happens to be in the corner in 1920x1080 resolution. Not 
present in smaller resolutions. In panning mode it's fixed to panel, not screen.
  Present on the panel and on fullscreen windows but not in overview.
  Not clickable (prevents me from clicking button underneath it).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2014-11-12 (2037 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 
(20141022.1)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-37.41-lowlatency 5.4.41
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
  Tags:  focal
  Uname: Linux 5.4.0-37-lowlatency x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-01 (40 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1882415/+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 1882415] Re: Graphical artifact in top-right corner, owned by ibus-ui-gtk3

2020-06-14 Thread Gunnar Hjalmarsson
Well, GNOME integrates IBus, and is supposed to suppress related UI
components in favor of equivalent Settings controls, so adding gnome-
shell as additional affecting package for now.

@vasdi: Can you please show us the output of this command:

env | grep -E 'XMOD|_IM'

** Also affects: gnome-shell (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/1882415

Title:
  Graphical artifact in top-right corner, owned by ibus-ui-gtk3

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

Bug description:
  Ubuntu 20.04, Gnome 3.36.2, Nvidia

  Small gray line in top-right corner.
  More precisely, it happens to be in the corner in 1920x1080 resolution. Not 
present in smaller resolutions. In panning mode it's fixed to panel, not screen.
  Present on the panel and on fullscreen windows but not in overview.
  Not clickable (prevents me from clicking button underneath it).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2014-11-12 (2037 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 
(20141022.1)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-37.41-lowlatency 5.4.41
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
  Tags:  focal
  Uname: Linux 5.4.0-37-lowlatency x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-01 (40 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1882415/+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 1881437] Re: IBus right click on system tray shows in top left corner hindering screen edges on KDE desktop

2020-05-31 Thread Gunnar Hjalmarsson
Thanks for your report. It does not sound as an ibus bug to me, though,
but rather a KDE one. Or sddm. Or a support request..

On KDE you should be able to add the "Input Method Panel" widget and
relogin. That will replace the IBus icon with a better-loooking KDE one.
Can you try that and let us know if it helps?

** Package changed: ibus (Ubuntu) => kde-runtime (Ubuntu)

** Changed in: kde-runtime (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/1881437

Title:
  IBus right click on system tray shows in top left corner hindering
  screen edges on KDE desktop

Status in kde-runtime package in Ubuntu:
  Incomplete

Bug description:
  Right-clicking IBus on system tray shows options on the top left
  corner of the desktop taking up space and hindering screen edges to be
  executed on KDE desktop.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kde-runtime/+bug/1881437/+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 1727908] Re: Software & Updates application does not permit changes on the "Other Software" tab

2020-05-26 Thread Gunnar Hjalmarsson
Verified the test case using software-properties-gtk 0.96.24.32.13 from
bionic-proposed.

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

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

Title:
  Software & Updates application does not permit changes on the "Other
  Software" tab

Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties source package in Bionic:
  Fix Committed

Bug description:
  * Impact
  Changes on the 'Other Software tab' sometime fail to ask for credential and 
fail to apply as a consequence

  * Test Case
  - start software-properties-gtk
  - got to the 'Other Software Tab'
  - try to change the value of a checkbox

  The change should prompt for a password and be active

  * Regression potential
  the change is a small sleep workaround to avoid trying to get the focus while 
GTK still has it, outside of a tiny delay in the active it should have no 
consequence

  ---

  
  On the "Other Software" tab, I am unable to select "Canonical Partners".
  Similarly, the other checkboxes on the "Other Software" can not be clicked.
  Clicking on a checkbox has no effect, and a dialog requesting the admin 
password is not presented.

  However, activating or deactivating checkboxes on other tabs causes an
  authorization dialog to be presented to the user.

  I experience this bug in an an Xorg session.

  sources.list and sources.list.d have the following permissions:
  -rw-r--r--   1 root root  2897 Oct 26 22:35 sources.list
  drwxr-xr-x   2 root root  4096 Oct 26 21:29 sources.list.d

  All files in sources.list.d have the following permissions as this example:
  -rw-r--r-- 1 root root  189 Oct 25 21:50 google-chrome.list

  $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  $ apt-cache policy software-properties-gtk
  software-properties-gtk:
    Installed: 0.96.24.17
    Candidate: 0.96.24.17
    Version table:
   *** 0.96.24.17 500
  500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu artful/main i386 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: software-properties-gtk 0.96.24.17
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Oct 26 22:45:09 2017
  InstallationDate: Installed on 2017-10-26 (1 days ago)
  InstallationMedia: Ubuntu 17.10.0 2017.10.25 amd64 "Custom Artful Aardvark"
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1727908/+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 1870945] Re: ubuntu-disable-trigger.patch is effectively not enabled

2020-05-24 Thread Gunnar Hjalmarsson
Rejected upstream, so re-closing. Upstream mentioned the idea to add a
warning dialog instead, which sounds good to me.

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

Title:
  ubuntu-disable-trigger.patch is effectively not enabled

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

Bug description:
  ubuntu-disable-trigger.patch has effectively not been enabled since
  XDG_CURRENT_DESKTOP was turned into a list of values instead of a
  single value.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ibus/+bug/1870945/+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 1669156] Re: Fails writing with Caps Lock

2020-05-24 Thread Gunnar Hjalmarsson
Please run the terminal command

cat /etc/default/keyboard

and show us what it outputs.

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

Title:
  Fails writing with Caps Lock

Status in lightdm package in Ubuntu:
  Incomplete

Bug description:
  On Ubuntu 16.04:

  When clicking on the following 3 keyboard keys simultaneously: 
  Left-CTRL + Left-ALT + F1
  Then you get to a textual terminal (CLI) where you can type commands.
  But there is a problem when typing English letters with Caps Lock turned on:
  Instead of English capital letters - you see squares, 
  so actually you can't login to your user that way
  if the username/password has Capital letters.

  The only method which allows you to write capital English letters
  is to simultaneously click Left-Shift + 'a letter'. 
  That is the only method that works well.

  Note that the Caps Lock key works well with the graphical terminal (pseudo / 
pts)
  that appears on Ubuntu when hitting simultaneously:
  Left-CTRL + Left-ALT + T

  ---

  I assumed the bug report is relevant to "shadow" package because that
  the "/bin/login" binary comes from that package.
  Package version of 'shadow' is: 1:4.2-3.1ubuntu5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1669156/+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 1880262] Re: package ibus 1.5.22-2ubuntu2 failed to install/upgrade: installed ibus package pre-removal script subprocess returned error exit status 127

2020-05-23 Thread Gunnar Hjalmarsson
** 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/1880262

Title:
  package ibus 1.5.22-2ubuntu2 failed to install/upgrade: installed ibus
  package pre-removal script subprocess returned error exit status 127

Status in ibus package in Ubuntu:
  Invalid

Bug description:
  Was installing Xubuntu Desktop via tasksel

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: ibus 1.5.22-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri May 22 23:29:17 2020
  DuplicateSignature:
   package:ibus:1.5.22-2ubuntu2
   Removing ibus (1.5.22-2ubuntu2) ...
   /var/lib/dpkg/info/ibus.prerm: 7: dconf: not found
   dpkg: error processing package ibus (--remove):
installed ibus package pre-removal script subprocess returned error exit 
status 127
  ErrorMessage: installed ibus package pre-removal script subprocess returned 
error exit status 127
  InstallationDate: Installed on 2020-05-21 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: ibus
  Title: package ibus 1.5.22-2ubuntu2 failed to install/upgrade: installed ibus 
package pre-removal script subprocess returned error exit status 127
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1880262/+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 1880262] Re: package ibus 1.5.22-2ubuntu2 failed to install/upgrade: installed ibus package pre-removal script subprocess returned error exit status 127

2020-05-23 Thread Gunnar Hjalmarsson
That sounds as a hardware glitch to me. What happens if you simply
reinstall ibus?

sudo apt install --reinstall ibus

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

Title:
  package ibus 1.5.22-2ubuntu2 failed to install/upgrade: installed ibus
  package pre-removal script subprocess returned error exit status 127

Status in ibus package in Ubuntu:
  Incomplete

Bug description:
  Was installing Xubuntu Desktop via tasksel

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: ibus 1.5.22-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri May 22 23:29:17 2020
  DuplicateSignature:
   package:ibus:1.5.22-2ubuntu2
   Removing ibus (1.5.22-2ubuntu2) ...
   /var/lib/dpkg/info/ibus.prerm: 7: dconf: not found
   dpkg: error processing package ibus (--remove):
installed ibus package pre-removal script subprocess returned error exit 
status 127
  ErrorMessage: installed ibus package pre-removal script subprocess returned 
error exit status 127
  InstallationDate: Installed on 2020-05-21 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: ibus
  Title: package ibus 1.5.22-2ubuntu2 failed to install/upgrade: installed ibus 
package pre-removal script subprocess returned error exit status 127
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1880262/+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 1879778] Re: "in future" phrasing in "Remember this in future" is chiefly British; bad localization

2020-05-20 Thread Gunnar Hjalmarsson
Thanks for your report.

You suggest a change to the original string, so it's not a
localization/translation issue, but a plain apport bug.

** Summary changed:

- "in future" phrasing in "Remember this in future" is chiefly British; bad 
localization
+ "in future" phrasing in "Remember this in future" is chiefly British; bad 
grammar

** No longer affects: ubuntu-translations

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

Title:
  "in future" phrasing in "Remember this in future" is chiefly British;
  bad grammar

Status in apport package in Ubuntu:
  New

Bug description:
  Crash an app in a development version of Ubuntu.

  
  What happens:

  Dialog appears with option: "Remember this in future"

  Expected result:

  "Remember this in the future."

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: apport-gtk 2.20.11-0ubuntu35
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu35
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashReports:
   600:120:125:37:2020-05-20 15:13:07.723688177 -0400:2020-05-20 
15:13:07.723688177 -0400:/var/crash/_usr_bin_gnome-boxes.1000.uploaded
   664:1000:125:0:2020-05-20 15:13:06.287707830 -0400:2020-05-20 
15:13:06.287707830 -0400:/var/crash/_usr_bin_gnome-boxes.1000.upload
   640:1000:125:31798483:2020-05-20 15:18:27.111421346 -0400:2020-05-20 
15:18:28.111421346 -0400:/var/crash/_usr_bin_gnome-boxes.1000.crash
  CurrentDesktop: GNOME
  Date: Wed May 20 15:18:58 2020
  InstallationDate: Installed on 2020-05-20 (0 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200518)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1879778/+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 1879015] Re: Autologin doesn't work (Lubuntu 18.04)

2020-05-15 Thread Gunnar Hjalmarsson
Please show what exactly the config file looks like.

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

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

Title:
  Autologin doesn't work (Lubuntu 18.04)

Status in lightdm package in Ubuntu:
  Incomplete

Bug description:
  I tried everything.

  3) I expected a working autologin once I set autologin-user=myusername in 
/etc/lightdm/lightdm.conf. Also I tried to change default session option. After 
I set "Do not ask password" in Users and Groups GUI autologin didn't work 
either. I needed to press "Login" button anyway. I don't know where the problem 
is. The only way to make autologin work I know is to set "Autologin" option 
while system installation. I don't want to reinstall to change just one option.
  Currently I use slim desktop manager. It's simpler and works. I have all 
possible options in /etc/slim.conf, I just need to uncomment something and 
edit. No need of reading docs and forums to just know what it can do. I hope 
someday lightdm will be changed in the same KISS way as slim.

  4) For some reason autologin doesn't work. Looks like lightdm just
  ignores its config files. It either shouldn't ignore these files or
  should provide a tool for configuring. The GUI tools I found doesn't
  provide an autologin option.

  (lightdm-autologin-greeter package doesn't help (I've edited
  /etc/lightdm/lightdm.conf.d/lightdm-autologin-greeter.conf properly),
  lightdm package doesn't have /etc/lightdm/lightdm.conf file)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: lightdm 1.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18
  Uname: Linux 5.3.0-51-generic i686
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: i386
  CurrentDesktop: LXDE
  Date: Sat May 16 04:05:25 2020
  InstallationDate: Installed on 2020-05-09 (6 days ago)
  InstallationMedia: Lubuntu 18.04.4 LTS "Bionic Beaver" - Release i386 
(20200203)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no username)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1879015/+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 1878611] Re: accountsservice 0.6.55-0ubuntu12~20.04.1 update crashes into greeter

2020-05-14 Thread Gunnar Hjalmarsson
** Tags added: focal regression-proposed

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

Title:
  accountsservice 0.6.55-0ubuntu12~20.04.1 update crashes into  greeter

Status in accountsservice package in Ubuntu:
  New

Bug description:
  When updating Ubuntu 20.04 to the current proposed updates with the
  accountsservice 0.6.55-0ubuntu12~20.04.1 update, the current gnome
  session crashes out reproducibly into the the gdm3 greeter. At that
  point, when you try to log back in, only the background color is
  displayed but no desktop or menus ever appears. One has to perform a
  hard reboot at this point to get back to a greeter that will
  successfully login.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1878611/+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 1878611] Re: accountsservice 0.6.55-0ubuntu12~20.04.1 update crashes into greeter

2020-05-14 Thread Gunnar Hjalmarsson
Thanks for your report. Can you please add a comment to bug #1843982
too. What you observed might be a regression, and important for the
decision whether to let 0.6.55-0ubuntu12 migrate to focal-updates.

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

Title:
  accountsservice 0.6.55-0ubuntu12~20.04.1 update crashes into  greeter

Status in accountsservice package in Ubuntu:
  New

Bug description:
  When updating Ubuntu 20.04 to the current proposed updates with the
  accountsservice 0.6.55-0ubuntu12~20.04.1 update, the current gnome
  session crashes out reproducibly into the the gdm3 greeter. At that
  point, when you try to log back in, only the background color is
  displayed but no desktop or menus ever appears. One has to perform a
  hard reboot at this point to get back to a greeter that will
  successfully login.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1878611/+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 1867090] Re: IBus 1.5.21 Chinese input in Ubuntu 19.10 not working with Atom 1.45.0 as snap

2020-05-09 Thread Gunnar Hjalmarsson
Yeah, it's easier to install the deb on 20.04 now than it was when I
made the 'experiment'. The explanation is the package python-is-python2
which was added to 20.04 right before the release.

But they should still port atom to python3 - python2 is obsolete and
will soon disappear from the Ubuntu archive.

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

Title:
  IBus 1.5.21 Chinese input in Ubuntu 19.10 not working with Atom 1.45.0
  as snap

Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  OS: Ubuntu 19.10
  IBus version: 1.5.21
  Atom version: 1.45.0

  When I switch to Chinese input mode (Intelligent Pinyin) and try to type 
Chinese into Atom 1.45.0 (snap version), it simply doesn't work.
  When I type the letters into the window, it shall bring up the candidate list 
for me to pick words. But instead, the letters are directly typed into the 
window, but not Chinese characters.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1867090/+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 1800012] Re: ogg vorbis corruption

2020-05-07 Thread Gunnar Hjalmarsson
** Also affects: taglib (Ubuntu Groovy)
   Importance: Undecided
   Status: Confirmed

** Also affects: taglib (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: taglib (Ubuntu Eoan)
   Importance: Undecided
   Status: New

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

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

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

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

** Changed in: taglib (Ubuntu Focal)
 Assignee: (unassigned) => Boyuan Yang (hosiet)

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

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

** Description changed:

+ [Impact]
+ 
+ TagLib 1.11.1 corrupts ogg vorbis files. The proposed uploads fix the
+ problem.
+ 
+ [Test Case]
+ 
+ 
+ [Regression Potential]
+ 
+ 
+ [Original description]
+ 
  TagLib 1.11.1 corrupts ogg vorbis files. See
  https://github.com/taglib/taglib/issues/775 It would be good to apply
  attached patch for released distributions.
  
  See upstream bugs for more details:
  https://github.com/taglib/taglib/issues/775
  https://github.com/taglib/taglib/issues/864

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

** Also affects: taglib (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915281
   Importance: Unknown
   Status: Unknown

** Bug watch added: github.com/taglib/taglib/issues #775
   https://github.com/taglib/taglib/issues/775

** Also affects: taglib via
   https://github.com/taglib/taglib/issues/775
   Importance: Unknown
   Status: Unknown

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

Title:
  ogg vorbis corruption

Status in TagLib:
  Fix Released
Status in taglib package in Ubuntu:
  Fix Released
Status in taglib source package in Bionic:
  Confirmed
Status in taglib source package in Eoan:
  Confirmed
Status in taglib source package in Focal:
  In Progress
Status in taglib source package in Groovy:
  Fix Released
Status in taglib package in Debian:
  Unknown

Bug description:
  [Impact]

  TagLib 1.11.1 corrupts ogg vorbis files. The proposed uploads fix the
  problem.

  [Test Case]

  
  [Regression Potential]

  
  [Original description]

  TagLib 1.11.1 corrupts ogg vorbis files. See
  https://github.com/taglib/taglib/issues/775 It would be good to apply
  attached patch for released distributions.

  See upstream bugs for more details:
  https://github.com/taglib/taglib/issues/775
  https://github.com/taglib/taglib/issues/864

To manage notifications about this bug go to:
https://bugs.launchpad.net/taglib/+bug/1800012/+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 1870945] Re: ubuntu-disable-trigger.patch is effectively not enabled

2020-05-02 Thread Gunnar Hjalmarsson
While the non-working patch was dropped, I have proposed equivalent
(working) code upstream:

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

Awaiting upstream's reaction to that, I re-open this bug for now.

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

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

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

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

** No longer affects: unity

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

Title:
  ubuntu-disable-trigger.patch is effectively not enabled

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

Bug description:
  ubuntu-disable-trigger.patch has effectively not been enabled since
  XDG_CURRENT_DESKTOP was turned into a list of values instead of a
  single value.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ibus/+bug/1870945/+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 1870945] Re: ubuntu-disable-trigger.patch is effectively not enabled

2020-04-29 Thread Gunnar Hjalmarsson
On Xenial the patch serves its intended purpose. I built IBus for Xenial
with ubuntu-disable-trigger.patch disabled and then installed. That made
the UI component show up for setting shortcut for "Next input method".
It defaults to Space, but changing it to e.g. Space affects
this dconf value:

$ gsettings get org.freedesktop.ibus.general.hotkey triggers
['space']

But on Unity that shortcut is not effective. It's overridden by the
shortcut set in Text Entry:

$ gsettings get org.gnome.desktop.wm.keybindings switch-input-source
['space']

So it's indeed a dead-end for users who happen to play with ibus-setup.

OTOH, that UI component is shown on GNOME too, and it's just as much a
dead-end there. If we think the issue is important enough, we should
figure out a smarter way to hide that UI component IMO. Also on GNOME.
And preferably upstream.

Let's drop the patch.

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

Title:
  ubuntu-disable-trigger.patch is effectively not enabled

Status in Unity:
  New
Status in ibus package in Ubuntu:
  In Progress

Bug description:
  ubuntu-disable-trigger.patch has effectively not been enabled since
  XDG_CURRENT_DESKTOP was turned into a list of values instead of a
  single value.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1870945/+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 1875805] Re: ibus 1.5.22 freezes when switching input method

2020-04-29 Thread Gunnar Hjalmarsson
Thanks for your report.

I added the sources you mentioned on my Ubuntu 20.04 (not Kubuntu), and
can switch between them without problem, both via the +
shortcut and the input source menu. So there is not much for us to work
on.

Can you please add some other Chinese input method, e.g. ibus-libpinyin,
and let us know if you can reproduce the problem with ibus 1.5.22 when
switching between "Intelligent Pinyin" and English.

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

Title:
  ibus 1.5.22 freezes when switching input method

Status in ibus package in Ubuntu:
  Incomplete

Bug description:
  ibus 1.5.22 freezes when switching input method. I have rime installed
  in addition to my keyboard layout (US AltGr dead keys). When I try to
  switch from rime to US Altgr, ibus freezes and input is not usable.

  Downgrading 1.5.22 to 1.5.21 solves this issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ibus 1.5.21-1~exp2ubuntu2.1
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Wed Apr 29 15:33:07 2020
  InstallationDate: Installed on 2016-10-03 (1304 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: ibus
  UpgradeStatus: Upgraded to focal on 2019-10-25 (186 days ago)

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

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


[Touch-packages] [Bug 1871625] Re: ibus-ui-gtk3 crashed with SIGSEGV in __vfprintf_internal()

2020-04-27 Thread Gunnar Hjalmarsson
Ouch. We should indeed dig deeper into it. Don't think I can help much
with interpreting stacktrace logs, though.

Want to remind of this attempt to get help from upstream:

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

Can't tell if Takao's hints are helpful.

Also, I noticed a comment Takao made as late as today at
 (i.e. the issue I would like
you to look at for another reason):

"IBus no longer uses the binding in IBus GtkIMModule but moved the
feature to ibus-extension-gtk3 which can customize the shortcut keys
with ibus-setup."

So upstream has done something with the code for UI and Gtk3, and most
of these latest crash reports are related to just that.

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

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

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

Title:
  ibus-ui-gtk3 crashed with SIGSEGV in __vfprintf_internal()

Status in ibus package in Ubuntu:
  New

Bug description:
  There is a similar bug but it is on 19.10. I got this on 20.04 after I
  closed and reopened my session.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: ibus 1.5.22-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr  8 14:46:26 2020
  ExecutablePath: /usr/libexec/ibus-ui-gtk3
  InstallationDate: Installed on 2018-04-07 (732 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180403)
  ProcCmdline: /usr/libexec/ibus-ui-gtk3
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fdcf7d9b9e1 <__vfprintf_internal+1>:nop
%edx
   PC (0x7fdcf7d9b9e1) ok
   source "%edx" ok
   Stack memory exhausted (SP below stack segment)
   SP (0x7fff10ee8da0) not located in a known VMA region (needed readable 
region)!
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: ibus
  StacktraceTop: __vfprintf_internal (s=0x7fff10ee9340, format=0x7fdcf818e0e9 
"%s\n", ap=0x7fff10eeba00, mode_flags=2) at vfprintf-internal.c:1289
  Title: ibus-ui-gtk3 crashed with SIGSEGV in __vfprintf_internal()
  UpgradeStatus: Upgraded to focal on 2020-04-04 (3 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark
  separator:

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

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


[Touch-packages] [Bug 1872200] Re: apt does not accept globs and regexes in some cases

2020-04-17 Thread Gunnar Hjalmarsson
I stumbled upon this when trying to install gnome-user-docs with all the
available languages:

$ sudo apt install gnome-user-docs*
Reading package lists... Done
Building dependency tree   
Reading state information... Done
E: Unable to locate package gnome-user-docs*

So far I can do what I want by using apt-get:

sudo apt-get install gnome-user-docs*

But I read in NEWS that the change is planned to propagate to apt-* ...
Is there no less intrusive way to deal with package names such as g++?

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

Title:
  apt does not accept globs and regexes in some cases

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  Observed with Ubuntu 20.04 Beta.

  apt remove 'mypackage*' does not remove all installed packages
  starting with “mypackage”.  Instead:

  $ sudo apt remove 'mypackage*'
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  E: Unable to locate package mypackage*

  However:

  $ sudo apt list --installed 'mypackage*'
  Listing... Done
  mypackage-data-v1/focal,focal,now 0.3.2-5build1 all [installed,automatic]
  mypackage1/focal,now 0.3.2-5build1 amd64 [installed]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1872200/+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 1870930] Re: systemctl crashed with SIGSEGV

2020-04-14 Thread Gunnar Hjalmarsson
Thanks for letting me know, Balint. Then it was no confusion on my side,
after all. :)

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

Title:
  systemctl crashed with SIGSEGV

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Logged in to an updated focal, entered a few unrelated commands in
  gnome-terminal, and then the crash message showed up.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.2-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sun Apr  5 16:26:11 2020
  Disassembly: => 0x0:  Cannot access memory at address 0x0
  ExecutablePath: /usr/bin/systemctl
  InstallationDate: Installed on 2019-11-10 (147 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Notebook P64_HJ,HK1
  ProcCmdline: systemctl --user start --wait unity-session.target
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=a8fd6652-86e7-4e1a-8259-809e0a4abd2b ro quiet splash
  SegvAnalysis:
   Segfault happened at: 0x0:   Cannot access memory at address 0x0
   PC (0x) not located in a known VMA region (needed executable region)!
  SegvReason: executing NULL VMA
  Signal: 11
  SourcePackage: systemd
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  SystemdDelta:
   [EXTENDED]   /usr/lib/systemd/system/rc-local.service → 
/usr/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /usr/lib/systemd/system/systemd-timesyncd.service → 
/usr/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /usr/lib/systemd/system/user@.service → 
/usr/lib/systemd/system/user@.service.d/timeout.conf
   
   3 overridden configuration files found.
  Title: systemctl crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  dmi.bios.date: 07/06/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.08
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P64_HJ,HK1
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.08:bd07/06/2017:svnNotebook:pnP64_HJ,HK1:pvrNotApplicable:rvnNotebook:rnP64_HJ,HK1:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P64_HJ,HK1
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1870930/+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 1800965] Re: Browsers don't display Devanagari script correctly

2020-04-13 Thread Gunnar Hjalmarsson
Closing the "fontconfig (Ubuntu)" task, since I have the experience that
upstream is disinclined to change /etc/fonts/conf.avail/65-nonlatin.conf
at the request of a distro, and carrying patches for the purpose is
inconvenient.

** Changed in: fontconfig (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  Browsers don't display Devanagari script correctly

Status in fontconfig package in Ubuntu:
  Won't Fix
Status in language-selector package in Ubuntu:
  Fix Released

Bug description:
  In the file /etc/fonts/conf.avail/65-nonlatin.conf the "Raghindi" font family 
is specified for devanagari script in Serif and Sans-serif style while "Lohit 
Hindi" in monospace. On the other hand, the Raghindi font is not installed by 
default. Because of this, the web browsers including Chrome and Firefox don't 
display the script correctly. A lot of people struggle to correct it by 
manually changing the settings in the browsers and partially succeed.
  The problem can be completely solved by replacing "Raghindi" in 
/etc/fonts/conf.avail/65-nonlatin.conf with "Lohit Hindi" or any other 
pre-installed font.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: fontconfig-config 2.13.0-5ubuntu3
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov  1 07:38:12 2018
  InstallationDate: Installed on 2018-10-22 (9 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  PackageArchitecture: all
  SourcePackage: fontconfig
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.fonts.conf.avail.65-nonlatin.conf: 
2018-10-26T14:54:05.700607

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1800965/+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 1869814] Re: ubuntu-docs build failure - possible solution

2020-04-10 Thread Gunnar Hjalmarsson
** Bug watch added: gitlab.gnome.org/GNOME/libxml2/issues #64
   https://gitlab.gnome.org/GNOME/libxml2/issues/64

** Changed in: libxml2
 Remote watch: bugzilla.gnome.org/ #789714 => 
gitlab.gnome.org/GNOME/libxml2/issues #64

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

Title:
  ubuntu-docs build failure - possible solution

Status in libxml2:
  Unknown
Status in libxml2 package in Ubuntu:
  In Progress
Status in ubuntu-docs package in Ubuntu:
  Fix Released

Bug description:
  ubuntu-docs failed to build during the second Focal Fossa test
  rebuild:

  https://launchpad.net/ubuntu/+archive/test-
  rebuild-20200327-focal/+build/18982738

  It was itstool which failed to generate the localized zh_CN pages. If
  dropping zh_CN from ubuntu-help/Makefile.am, ubuntu-docs builds. But
  excluding the Chinese pages is apparently not an acceptable solution.

  The itstool package in focal {build-,}depends on python3. I built
  itstool in a PPA with python2 instead, and in that PPA ubuntu-docs
  built fine without modifications:

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

  So the root cause seems to lie neither in ubuntu-docs nor itstool. I
  would suspect that python3-libxml2 is buggy, but since itstool was
  built against python2 in eoan, it's hard to tell if it's a regression.

  Would building itstool against python2 be an acceptable workaround in
  focal?

To manage notifications about this bug go to:
https://bugs.launchpad.net/libxml2/+bug/1869814/+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 1869814] Re: ubuntu-docs build failure - possible solution

2020-04-10 Thread Gunnar Hjalmarsson
To the sponsor:

libxml2 2.9.10+dfsg-5, including the patch, is now available in Debian
unstable. So please sync libxml2.

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

Title:
  ubuntu-docs build failure - possible solution

Status in itstool package in Ubuntu:
  Invalid
Status in libxml2 package in Ubuntu:
  In Progress
Status in ubuntu-docs package in Ubuntu:
  Fix Released

Bug description:
  ubuntu-docs failed to build during the second Focal Fossa test
  rebuild:

  https://launchpad.net/ubuntu/+archive/test-
  rebuild-20200327-focal/+build/18982738

  It was itstool which failed to generate the localized zh_CN pages. If
  dropping zh_CN from ubuntu-help/Makefile.am, ubuntu-docs builds. But
  excluding the Chinese pages is apparently not an acceptable solution.

  The itstool package in focal {build-,}depends on python3. I built
  itstool in a PPA with python2 instead, and in that PPA ubuntu-docs
  built fine without modifications:

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

  So the root cause seems to lie neither in ubuntu-docs nor itstool. I
  would suspect that python3-libxml2 is buggy, but since itstool was
  built against python2 in eoan, it's hard to tell if it's a regression.

  Would building itstool against python2 be an acceptable workaround in
  focal?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/itstool/+bug/1869814/+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 1727908] Re: Software & Updates application does not permit changes on the "Other Software" tab

2020-04-10 Thread Gunnar Hjalmarsson
@Sebastien: I can confirm that your workaround fixes it for me. (Race
condition?)

Would be nice if it could be uploaded to focal to start with...

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

Title:
  Software & Updates application does not permit changes on the "Other
  Software" tab

Status in gnome-shell package in Ubuntu:
  Invalid
Status in software-properties package in Ubuntu:
  Confirmed
Status in gnome-shell source package in Bionic:
  Invalid
Status in software-properties source package in Bionic:
  Confirmed

Bug description:
  
  On the "Other Software" tab, I am unable to select "Canonical Partners".
  Similarly, the other checkboxes on the "Other Software" can not be clicked.
  Clicking on a checkbox has no effect, and a dialog requesting the admin 
password is not presented.

  However, activating or deactivating checkboxes on other tabs causes an
  authorization dialog to be presented to the user.

  I experience this bug in an an Xorg session.

  sources.list and sources.list.d have the following permissions:
  -rw-r--r--   1 root root  2897 Oct 26 22:35 sources.list
  drwxr-xr-x   2 root root  4096 Oct 26 21:29 sources.list.d

  All files in sources.list.d have the following permissions as this example:
  -rw-r--r-- 1 root root  189 Oct 25 21:50 google-chrome.list

  $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  $ apt-cache policy software-properties-gtk
  software-properties-gtk:
Installed: 0.96.24.17
Candidate: 0.96.24.17
Version table:
   *** 0.96.24.17 500
  500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu artful/main i386 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: software-properties-gtk 0.96.24.17
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Oct 26 22:45:09 2017
  InstallationDate: Installed on 2017-10-26 (1 days ago)
  InstallationMedia: Ubuntu 17.10.0 2017.10.25 amd64 "Custom Artful Aardvark"
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: software-properties
  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/1727908/+subscriptions

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


[Touch-packages] [Bug 1872071] Re: ibus-x11 crashed with SIGSEGV in __GI___poll()

2020-04-10 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/1872071

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

Status in ibus package in Ubuntu:
  New

Bug description:
  This happened at start up after software updater requested a restart.I 
attached 
  unattended-upgrades.log
  unattended-upgrades-dpkg.log
  dpkg.log
  to show what packages were installed before the restart.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: ibus 1.5.22-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Apr 10 07:16:32 2020
  ExecutablePath: /usr/libexec/ibus-x11
  InstallationDate: Installed on 2020-03-14 (26 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309)
  ProcCmdline: /usr/libexec/ibus-x11 --kill-daemon
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   SHELL=/bin/false
  SegvAnalysis:
   Segfault happened at: 0x7f6b2b2919f6 <__run_exit_handlers+198>:  mov
0x10(%rax),%rdx
   PC (0x7f6b2b2919f6) ok
   source "0x10(%rax)" (0x1042f359537650) not located in a known VMA region 
(needed readable region)!
   destination "%rdx" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: ibus
  StacktraceTop:
   __GI___poll (fds=0x7f6af80067e0, nfds=3, timeout=1766) at 
../sysdeps/unix/sysv/linux/poll.c:29
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ibus_main () from /lib/x86_64-linux-gnu/libibus-1.0.so.5
   ?? ()
  Title: ibus-x11 crashed with SIGSEGV in __GI___poll()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  separator:

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

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


[Touch-packages] [Bug 1800965] Re: Browsers don't display Devanagari script correctly

2020-04-08 Thread Gunnar Hjalmarsson
I made an attempt to address this bug via another package. The language-
selector-common package installs /etc/fonts/conf.avail/64-language-
selector-prefer.conf, and I added "Lohit Devanagari" (installed by
default) to that file.

https://git.launchpad.net/~ubuntu-desktop/ubuntu/+source/language-
selector/commit/?id=0496ecdc

It has not been uploaded yet, and it would be great if you could confirm
that the change fixes the issue in this bug.

** Also affects: language-selector (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: language-selector (Ubuntu)
   Importance: Undecided => Low

** 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 fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/1800965

Title:
  Browsers don't display Devanagari script correctly

Status in fontconfig package in Ubuntu:
  Confirmed
Status in language-selector package in Ubuntu:
  In Progress

Bug description:
  In the file /etc/fonts/conf.avail/65-nonlatin.conf the "Raghindi" font family 
is specified for devanagari script in Serif and Sans-serif style while "Lohit 
Hindi" in monospace. On the other hand, the Raghindi font is not installed by 
default. Because of this, the web browsers including Chrome and Firefox don't 
display the script correctly. A lot of people struggle to correct it by 
manually changing the settings in the browsers and partially succeed.
  The problem can be completely solved by replacing "Raghindi" in 
/etc/fonts/conf.avail/65-nonlatin.conf with "Lohit Hindi" or any other 
pre-installed font.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: fontconfig-config 2.13.0-5ubuntu3
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov  1 07:38:12 2018
  InstallationDate: Installed on 2018-10-22 (9 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  PackageArchitecture: all
  SourcePackage: fontconfig
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.fonts.conf.avail.65-nonlatin.conf: 
2018-10-26T14:54:05.700607

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

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


[Touch-packages] [Bug 1871625] Re: ibus-ui-gtk3 crashed with SIGSEGV in __vfprintf_internal()

2020-04-08 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/1871625

Title:
  ibus-ui-gtk3 crashed with SIGSEGV in __vfprintf_internal()

Status in ibus package in Ubuntu:
  New

Bug description:
  There is a similar bug but it is on 19.10. I got this on 20.04 after I
  closed and reopened my session.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: ibus 1.5.22-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr  8 14:46:26 2020
  ExecutablePath: /usr/libexec/ibus-ui-gtk3
  InstallationDate: Installed on 2018-04-07 (732 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180403)
  ProcCmdline: /usr/libexec/ibus-ui-gtk3
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fdcf7d9b9e1 <__vfprintf_internal+1>:nop
%edx
   PC (0x7fdcf7d9b9e1) ok
   source "%edx" ok
   Stack memory exhausted (SP below stack segment)
   SP (0x7fff10ee8da0) not located in a known VMA region (needed readable 
region)!
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: ibus
  StacktraceTop: __vfprintf_internal (s=0x7fff10ee9340, format=0x7fdcf818e0e9 
"%s\n", ap=0x7fff10eeba00, mode_flags=2) at vfprintf-internal.c:1289
  Title: ibus-ui-gtk3 crashed with SIGSEGV in __vfprintf_internal()
  UpgradeStatus: Upgraded to focal on 2020-04-04 (3 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark
  separator:

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

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


[Touch-packages] [Bug 1870747] Re: ibus-ui-gtk3 crashed with SIGABRT in raise()

2020-04-07 Thread Gunnar Hjalmarsson
@Sebastien: Takao Fujiwara provided some hints about this and other
similar crash reports at the upstream issue I submitted. I'm thinking
that this may be something to look into post-release.

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

Title:
  ibus-ui-gtk3 crashed with SIGABRT in raise()

Status in ibus package in Ubuntu:
  Incomplete

Bug description:
  ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message_expr()

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: ibus 1.5.22-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 13:27:38 2020
  ExecutablePath: /usr/libexec/ibus-ui-gtk3
  InstallationDate: Installed on 2020-04-03 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcCmdline: /usr/libexec/ibus-ui-gtk3
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: ibus
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   ?? ()
   ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message_expr()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

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

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


[Touch-packages] [Bug 1870930] Re: systemctl crashed with SIGSEGV

2020-04-05 Thread Gunnar Hjalmarsson
Hmm.. I did enter Unity sessions a couple of times, but if I recall it
correctly, this crash happened in a standard Ubuntu session. Not 100%
sure, though...

** 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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1870930

Title:
  systemctl crashed with SIGSEGV

Status in systemd package in Ubuntu:
  New

Bug description:
  Logged in to an updated focal, entered a few unrelated commands in
  gnome-terminal, and then the crash message showed up.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.2-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sun Apr  5 16:26:11 2020
  Disassembly: => 0x0:  Cannot access memory at address 0x0
  ExecutablePath: /usr/bin/systemctl
  InstallationDate: Installed on 2019-11-10 (147 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Notebook P64_HJ,HK1
  ProcCmdline: systemctl --user start --wait unity-session.target
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=a8fd6652-86e7-4e1a-8259-809e0a4abd2b ro quiet splash
  SegvAnalysis:
   Segfault happened at: 0x0:   Cannot access memory at address 0x0
   PC (0x) not located in a known VMA region (needed executable region)!
  SegvReason: executing NULL VMA
  Signal: 11
  SourcePackage: systemd
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  SystemdDelta:
   [EXTENDED]   /usr/lib/systemd/system/rc-local.service → 
/usr/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /usr/lib/systemd/system/systemd-timesyncd.service → 
/usr/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /usr/lib/systemd/system/user@.service → 
/usr/lib/systemd/system/user@.service.d/timeout.conf
   
   3 overridden configuration files found.
  Title: systemctl crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  dmi.bios.date: 07/06/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.08
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P64_HJ,HK1
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.08:bd07/06/2017:svnNotebook:pnP64_HJ,HK1:pvrNotApplicable:rvnNotebook:rnP64_HJ,HK1:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P64_HJ,HK1
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1870930/+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 1870945] Re: ubuntu-disable-trigger.patch is effectively not enabled

2020-04-05 Thread Gunnar Hjalmarsson
I tried to fix this by replacing:

if os.getenv("XDG_CURRENT_DESKTOP") == "Unity":

with:

desktop = os.environ.get('XDG_CURRENT_DESKTOP')
if desktop and 'Unity' in desktop.split(':'):

But then ibus-setup didn't start at all under Unity:

$ ibus-setup
Traceback (most recent call last):
  File "/usr/share/ibus/setup/main.py", line 710, in 
setup = Setup()
  File "/usr/share/ibus/setup/main.py", line 120, in __init__
self.__init_ui()
  File "/usr/share/ibus/setup/main.py", line 413, in __init_ui
self.__init_hotkeys()
  File "/usr/share/ibus/setup/main.py", line 130, in __init_hotkeys
self.__init_hotkey(name, label)
  File "/usr/share/ibus/setup/main.py", line 144, in __init_hotkey
entry.set_text("; ".join(shortcuts))
AttributeError: 'NoneType' object has no attribute 'set_text'
$

Probably the affected upstream files have changed since the patch was
written.

So does anyone have time/interest to maintain this patch? Or should we
simply drop it? After all IBus seems to work fine (in focal) without it.

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

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

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

Title:
  ubuntu-disable-trigger.patch is effectively not enabled

Status in Unity:
  New
Status in ibus package in Ubuntu:
  In Progress

Bug description:
  ubuntu-disable-trigger.patch has effectively not been enabled since
  XDG_CURRENT_DESKTOP was turned into a list of values instead of a
  single value.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1870945/+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 1870945] [NEW] ubuntu-disable-trigger.patch is effectively not enabled

2020-04-05 Thread Gunnar Hjalmarsson
Public bug reported:

ubuntu-disable-trigger.patch has effectively not been enabled since
XDG_CURRENT_DESKTOP was turned into a list of values instead of a single
value.

** Affects: ibus (Ubuntu)
 Importance: Medium
 Assignee: Gunnar Hjalmarsson (gunnarhj)
 Status: 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/1870945

Title:
  ubuntu-disable-trigger.patch is effectively not enabled

Status in ibus package in Ubuntu:
  In Progress

Bug description:
  ubuntu-disable-trigger.patch has effectively not been enabled since
  XDG_CURRENT_DESKTOP was turned into a list of values instead of a
  single value.

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

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


[Touch-packages] [Bug 1870843] Re: ibus-ui-gtk3 crashed with SIGSEGV in ibus_bus_call_sync()

2020-04-04 Thread Gunnar Hjalmarsson
Called upstream's attention to this via:

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

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

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

Title:
  ibus-ui-gtk3 crashed with SIGSEGV in ibus_bus_call_sync()

Status in ibus package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: ibus 1.5.22-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 13:03:51 2020
  ExecutablePath: /usr/libexec/ibus-ui-gtk3
  ProcCmdline: /usr/libexec/ibus-ui-gtk3
  ProcEnviron:
   LANGUAGE=es_AR:es
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_AR.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fee4f4e8f5b : orq
$0x0,(%rsp)
   PC (0x7fee4f4e8f5b) ok
   source "$0x0" ok
   destination "(%rsp)" (0x7ffe02368d40) not located in a known VMA region 
(needed writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: ibus
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libibus-1.0.so.5
   ibus_bus_get_engines_by_names () from /lib/x86_64-linux-gnu/libibus-1.0.so.5
   ?? ()
   ?? ()
   g_cclosure_marshal_VOID__STRINGv () from 
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: ibus-ui-gtk3 crashed with SIGSEGV in ibus_bus_get_engines_by_names()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

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

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


[Touch-packages] [Bug 1849399] Re: ibus in 19.10 misinterprets ~/.XCompose, somehow maps to the Delete key

2020-04-04 Thread Gunnar Hjalmarsson
Plus, of course: Delete key affected.

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

Title:
  ibus in 19.10 misinterprets ~/.XCompose, somehow maps to the Delete
  key

Status in ibus package in Ubuntu:
  Triaged

Bug description:
  After upgrade to 19.10, I found that my Delete key was not working as
  a Delete key, but that instead if I hit Delete twice it would print
  the character ☭.

  Since others were not reporting this issue, I had a look around at my
  input config and remembered that I had ibus configured from a long
  time ago in order to support Chinese input.

  If I disable ibus (either by unsetting the environment variables; or
  by killing ibus-daemon), then the Delete key works again as expected.

  This is a regression in behavior since Ubuntu 19.04, where I had the
  same input setup on my desktop but the Delete key worked without
  problems.

  I'm also not sure how to disable ibus, now that I am in this
  situation; or if ibus is expected to always be running.

  The problem persists if I run ibus-setup and remove Chinese SunPinyin
  from the list of input methods, leaving only "English - English (US)".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1849399/+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 1849399] Re: ibus in 19.10 misinterprets ~/.XCompose, somehow maps to the Delete key

2020-04-04 Thread Gunnar Hjalmarsson
Just stumbled upon this issue:

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

Common denominators are:

* Error in ~/.XCompose

* Upgrade to ibus 1.5.21

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

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

Title:
  ibus in 19.10 misinterprets ~/.XCompose, somehow maps to the Delete
  key

Status in ibus package in Ubuntu:
  Triaged

Bug description:
  After upgrade to 19.10, I found that my Delete key was not working as
  a Delete key, but that instead if I hit Delete twice it would print
  the character ☭.

  Since others were not reporting this issue, I had a look around at my
  input config and remembered that I had ibus configured from a long
  time ago in order to support Chinese input.

  If I disable ibus (either by unsetting the environment variables; or
  by killing ibus-daemon), then the Delete key works again as expected.

  This is a regression in behavior since Ubuntu 19.04, where I had the
  same input setup on my desktop but the Delete key worked without
  problems.

  I'm also not sure how to disable ibus, now that I am in this
  situation; or if ibus is expected to always be running.

  The problem persists if I run ibus-setup and remove Chinese SunPinyin
  from the list of input methods, leaving only "English - English (US)".

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

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


[Touch-packages] [Bug 1870843] Re: ibus-ui-gtk3 crashed with SIGSEGV in ibus_bus_call_sync()

2020-04-04 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/1870843

Title:
  ibus-ui-gtk3 crashed with SIGSEGV in ibus_bus_call_sync()

Status in ibus package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: ibus 1.5.22-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 13:03:51 2020
  ExecutablePath: /usr/libexec/ibus-ui-gtk3
  ProcCmdline: /usr/libexec/ibus-ui-gtk3
  ProcEnviron:
   LANGUAGE=es_AR:es
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_AR.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fee4f4e8f5b : orq
$0x0,(%rsp)
   PC (0x7fee4f4e8f5b) ok
   source "$0x0" ok
   destination "(%rsp)" (0x7ffe02368d40) not located in a known VMA region 
(needed writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: ibus
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libibus-1.0.so.5
   ibus_bus_get_engines_by_names () from /lib/x86_64-linux-gnu/libibus-1.0.so.5
   ?? ()
   ?? ()
   g_cclosure_marshal_VOID__STRINGv () from 
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: ibus-ui-gtk3 crashed with SIGSEGV in ibus_bus_get_engines_by_names()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

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

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


[Touch-packages] [Bug 1864561] Re: For GDK_HYPER_MASK, gtk_im_context_filter_keypress() falsely reports that IM handled the event

2020-04-04 Thread Gunnar Hjalmarsson
** Bug watch added: github.com/ibus/ibus/issues #2187
   https://github.com/ibus/ibus/issues/2187

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

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

Title:
  For GDK_HYPER_MASK, gtk_im_context_filter_keypress() falsely reports
  that IM handled the event

Status in ibus:
  Unknown
Status in gtk+3.0 package in Ubuntu:
  New
Status in ibus package in Ubuntu:
  New

Bug description:
  If the keypress event contains GDK_HYPER_MASK as a modifier,
  gtk_im_context_filter_keypress() returns true, reporting that the IM
  handled the event, even though it did not, therefore it should return
  false.

  Background: We are working on modifying Gnome-Terminal / libvte-2.91.so.0 to 
enable Terminal-bespoke remapping of modifier keys. This is to facilitate OS X 
users to migrate to Ubuntu. (Discussion here: #220. Background and unsuccessful 
alternative approaches detailed here: 
https://github.com/bjohas/Ubuntu-keyboard-map-like-OS-X/blob/master/README.md).
  When we replace GDK_CONTROL_MASK by GDK_HYPER_MASK, the input method (ibus) 
reports that it handled the event that had Hyper as the modifier. When we use 
export GTK_IM_MODULE=xim, the Hyper modifier is passed as expected. 

  We believe that this is a bug in ibus XOR gtk. Unfortunately I'm not
  sure whether this is an issue in ibus or gtk, so I'm reporting it in
  both places (as well as upstream). Apologies for the inconvenience
  caused by this. Many thanks for looking at this.

  I'll track updates here
  https://gitlab.gnome.org/GNOME/gnome-terminal/issues/220
  and here
  
https://github.com/bjohas/Ubuntu-keyboard-map-like-OS-X/blob/master/Building%20a%20Gnome-Hyper-Terminal.md
  so that people compinging Gnonme Terminal are aware of the status.

  Many thanks!

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

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


[Touch-packages] [Bug 1829297] Re: ibus-ui-gtk3 crashed with SIGSEGV in tcache_get()

2020-04-04 Thread Gunnar Hjalmarsson
Called upstream's attention to this via:

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

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

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

Title:
  ibus-ui-gtk3 crashed with SIGSEGV in tcache_get()

Status in ibus package in Ubuntu:
  New

Bug description:
  browser reading and listening to a yutube-stream, suddeny this bug
  message pops up

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-50.54-lowlatency 4.15.18
  Uname: Linux 4.15.0-50-lowlatency x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  Date: Wed May 15 23:10:18 2019
  ExecutablePath: /usr/lib/ibus/ibus-ui-gtk3
  InstallationDate: Installed on 2018-08-08 (280 days ago)
  InstallationMedia: Ubuntu-Studio 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  ProcCmdline: /usr/lib/ibus/ibus-ui-gtk3
  SegvAnalysis:
   Segfault happened at: 0x7f550a55f207 <__GI___libc_malloc+407>:   mov
(%rdx),%rdi
   PC (0x7f550a55f207) ok
   source "(%rdx)" (0x6e6f662f6374652f) not located in a known VMA region 
(needed readable region)!
   destination "%rdi" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: ibus
  StacktraceTop:
   tcache_get (tc_idx=2) at malloc.c:2943
   __GI___libc_malloc (bytes=48) at malloc.c:3050
   ?? () from /usr/lib/x86_64-linux-gnu/libfontconfig.so.1
   FcStrSetAdd () from /usr/lib/x86_64-linux-gnu/libfontconfig.so.1
   FcConfigParseAndLoad () from /usr/lib/x86_64-linux-gnu/libfontconfig.so.1
  Title: ibus-ui-gtk3 crashed with SIGSEGV in tcache_get()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio avahi avahi-autoipd backup bin bluetooth cdrom colord 
crontab daemon dialout dip disk fax floppy games geoclue gnats input irc kmem 
lightdm list lp lpadmin mail man messagebus mlocate netdev news nopasswdlogin 
operator plugdev proxy pulse pulse-access root rtkit sambashare saned sasl 
scanner shadow src ssh ssl-cert staff sudo sys tape video

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

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


[Touch-packages] [Bug 1869484] Re: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message.cold()

2020-04-04 Thread Gunnar Hjalmarsson
Called upstream's attention to this via:

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

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

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

Title:
  ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message.cold()

Status in ibus package in Ubuntu:
  Incomplete

Bug description:
  i don't know what's happened

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: ibus 1.5.22-2ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 27 23:00:56 2020
  ExecutablePath: /usr/libexec/ibus-ui-gtk3
  InstallationDate: Installed on 2018-08-07 (598 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcCmdline: /usr/libexec/ibus-ui-gtk3
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: ibus
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message_expr()
  UpgradeStatus: Upgraded to focal on 2020-03-08 (19 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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

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


[Touch-packages] [Bug 1843958] Re: ibus-ui-gtk3 crashed with SIGSEGV in ibus_bus_get_engines_by_names()

2020-04-04 Thread Gunnar Hjalmarsson
Called upstream's attention to this via:

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

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

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

Title:
  ibus-ui-gtk3 crashed with SIGSEGV in ibus_bus_get_engines_by_names()

Status in ibus package in Ubuntu:
  New

Bug description:
  I was adding a new user in system settings in the liveusb version of
  Ubuntu 19.10 alpha when the error message appeared bellow the other
  windows. I didn't notice anything crashing, AFAICR

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: ibus 1.5.19-4ubuntu2
  ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9
  Uname: Linux 5.2.0-15-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CasperVersion: 1.415
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 13 22:16:39 2019
  ExecutablePath: /usr/lib/ibus/ibus-ui-gtk3
  LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190909)
  ProcCmdline: /usr/lib/ibus/ibus-ui-gtk3
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fac162ecf3e :movl   
$0xfbad8004,0x20(%rsp)
   PC (0x7fac162ecf3e) ok
   source "$0xfbad8004" ok
   destination "0x20(%rsp)" (0x7ffdf646afd0) not located in a known VMA region 
(needed writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: ibus
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libibus-1.0.so.5
   ibus_bus_get_engines_by_names () from /lib/x86_64-linux-gnu/libibus-1.0.so.5
   ?? ()
   ?? ()
   g_cclosure_marshal_VOID__STRINGv () from 
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: ibus-ui-gtk3 crashed with SIGSEGV in ibus_bus_get_engines_by_names()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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

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


[Touch-packages] [Bug 1870747] Re: ibus-ui-gtk3 crashed with SIGABRT in raise()

2020-04-04 Thread Gunnar Hjalmarsson
Called upstream's attention to this via:

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

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

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

Title:
  ibus-ui-gtk3 crashed with SIGABRT in raise()

Status in ibus package in Ubuntu:
  New

Bug description:
  ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message_expr()

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: ibus 1.5.22-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 13:27:38 2020
  ExecutablePath: /usr/libexec/ibus-ui-gtk3
  InstallationDate: Installed on 2020-04-03 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcCmdline: /usr/libexec/ibus-ui-gtk3
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: ibus
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   ?? ()
   ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message_expr()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

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

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


[Touch-packages] [Bug 1843195] Re: ibus-ui-gtk3 crashed with SIGSEGV in __vfprintf_internal()

2020-04-04 Thread Gunnar Hjalmarsson
Called upstream's attention to this via:

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

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

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

Title:
  ibus-ui-gtk3 crashed with SIGSEGV in __vfprintf_internal()

Status in ibus package in Ubuntu:
  New

Bug description:
  switch user not working.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: ibus 1.5.19-4ubuntu2
  ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9
  Uname: Linux 5.2.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep  2 18:03:59 2019
  ExecutablePath: /usr/lib/ibus/ibus-ui-gtk3
  InstallationDate: Installed on 2019-08-27 (12 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190819)
  ProcCmdline: /usr/lib/ibus/ibus-ui-gtk3
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: ibus
  StacktraceTop:
   __vfprintf_internal (s=0x7f84e5081f5f, format=0x25 , ap=0x7ffe1ea7fc20, mode_flags=2) at 
vfprintf-internal.c:1289
   __vfprintf_internal (s=0x4, format=0x7ffe1ea7fc20 "\030", ap=0x2, 
mode_flags=) at ../libio/libioP.h:947
  Title: ibus-ui-gtk3 crashed with SIGSEGV in __vfprintf_internal()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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

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


[Touch-packages] [Bug 1843195] Re: ibus-ui-gtk3 crashed with SIGSEGV in __vfprintf_internal()

2020-04-04 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/1843195

Title:
  ibus-ui-gtk3 crashed with SIGSEGV in __vfprintf_internal()

Status in ibus package in Ubuntu:
  New

Bug description:
  switch user not working.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: ibus 1.5.19-4ubuntu2
  ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9
  Uname: Linux 5.2.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep  2 18:03:59 2019
  ExecutablePath: /usr/lib/ibus/ibus-ui-gtk3
  InstallationDate: Installed on 2019-08-27 (12 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190819)
  ProcCmdline: /usr/lib/ibus/ibus-ui-gtk3
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: ibus
  StacktraceTop:
   __vfprintf_internal (s=0x7f84e5081f5f, format=0x25 , ap=0x7ffe1ea7fc20, mode_flags=2) at 
vfprintf-internal.c:1289
   __vfprintf_internal (s=0x4, format=0x7ffe1ea7fc20 "\030", ap=0x2, 
mode_flags=) at ../libio/libioP.h:947
  Title: ibus-ui-gtk3 crashed with SIGSEGV in __vfprintf_internal()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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

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


[Touch-packages] [Bug 1843958] Re: ibus-ui-gtk3 crashed with SIGSEGV in ibus_bus_get_engines_by_names()

2020-04-04 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/1843958

Title:
  ibus-ui-gtk3 crashed with SIGSEGV in ibus_bus_get_engines_by_names()

Status in ibus package in Ubuntu:
  New

Bug description:
  I was adding a new user in system settings in the liveusb version of
  Ubuntu 19.10 alpha when the error message appeared bellow the other
  windows. I didn't notice anything crashing, AFAICR

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: ibus 1.5.19-4ubuntu2
  ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9
  Uname: Linux 5.2.0-15-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CasperVersion: 1.415
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 13 22:16:39 2019
  ExecutablePath: /usr/lib/ibus/ibus-ui-gtk3
  LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190909)
  ProcCmdline: /usr/lib/ibus/ibus-ui-gtk3
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fac162ecf3e :movl   
$0xfbad8004,0x20(%rsp)
   PC (0x7fac162ecf3e) ok
   source "$0xfbad8004" ok
   destination "0x20(%rsp)" (0x7ffdf646afd0) not located in a known VMA region 
(needed writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: ibus
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libibus-1.0.so.5
   ibus_bus_get_engines_by_names () from /lib/x86_64-linux-gnu/libibus-1.0.so.5
   ?? ()
   ?? ()
   g_cclosure_marshal_VOID__STRINGv () from 
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: ibus-ui-gtk3 crashed with SIGSEGV in ibus_bus_get_engines_by_names()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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

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


[Touch-packages] [Bug 1829297] Re: ibus-ui-gtk3 crashed with SIGSEGV in tcache_get()

2020-04-04 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/1829297

Title:
  ibus-ui-gtk3 crashed with SIGSEGV in tcache_get()

Status in ibus package in Ubuntu:
  New

Bug description:
  browser reading and listening to a yutube-stream, suddeny this bug
  message pops up

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-50.54-lowlatency 4.15.18
  Uname: Linux 4.15.0-50-lowlatency x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  Date: Wed May 15 23:10:18 2019
  ExecutablePath: /usr/lib/ibus/ibus-ui-gtk3
  InstallationDate: Installed on 2018-08-08 (280 days ago)
  InstallationMedia: Ubuntu-Studio 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  ProcCmdline: /usr/lib/ibus/ibus-ui-gtk3
  SegvAnalysis:
   Segfault happened at: 0x7f550a55f207 <__GI___libc_malloc+407>:   mov
(%rdx),%rdi
   PC (0x7f550a55f207) ok
   source "(%rdx)" (0x6e6f662f6374652f) not located in a known VMA region 
(needed readable region)!
   destination "%rdi" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: ibus
  StacktraceTop:
   tcache_get (tc_idx=2) at malloc.c:2943
   __GI___libc_malloc (bytes=48) at malloc.c:3050
   ?? () from /usr/lib/x86_64-linux-gnu/libfontconfig.so.1
   FcStrSetAdd () from /usr/lib/x86_64-linux-gnu/libfontconfig.so.1
   FcConfigParseAndLoad () from /usr/lib/x86_64-linux-gnu/libfontconfig.so.1
  Title: ibus-ui-gtk3 crashed with SIGSEGV in tcache_get()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio avahi avahi-autoipd backup bin bluetooth cdrom colord 
crontab daemon dialout dip disk fax floppy games geoclue gnats input irc kmem 
lightdm list lp lpadmin mail man messagebus mlocate netdev news nopasswdlogin 
operator plugdev proxy pulse pulse-access root rtkit sambashare saned sasl 
scanner shadow src ssh ssl-cert staff sudo sys tape video

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

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


[Touch-packages] [Bug 1870747] Re: ibus-ui-gtk3 crashed with SIGABRT in raise()

2020-04-04 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/1870747

Title:
  ibus-ui-gtk3 crashed with SIGABRT in raise()

Status in ibus package in Ubuntu:
  New

Bug description:
  ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message_expr()

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: ibus 1.5.22-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 13:27:38 2020
  ExecutablePath: /usr/libexec/ibus-ui-gtk3
  InstallationDate: Installed on 2020-04-03 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcCmdline: /usr/libexec/ibus-ui-gtk3
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: ibus
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   ?? ()
   ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message_expr()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

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

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


[Touch-packages] [Bug 1869484] Re: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message.cold()

2020-04-03 Thread Gunnar Hjalmarsson
On 2020-04-03 21:52, Michael wrote:
> Was a mistake, miss-clicked and wouldn't let me revert. sorry!

N.p., thanks for explaining.

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

Title:
  ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message.cold()

Status in ibus package in Ubuntu:
  Incomplete

Bug description:
  i don't know what's happened

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: ibus 1.5.22-2ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 27 23:00:56 2020
  ExecutablePath: /usr/libexec/ibus-ui-gtk3
  InstallationDate: Installed on 2018-08-07 (598 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcCmdline: /usr/libexec/ibus-ui-gtk3
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: ibus
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message_expr()
  UpgradeStatus: Upgraded to focal on 2020-03-08 (19 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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

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


[Touch-packages] [Bug 1869484] Re: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message.cold()

2020-04-03 Thread Gunnar Hjalmarsson
@Michael: Why did you close the bug with "Fix Released" without
justification?

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

Title:
  ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message.cold()

Status in ibus package in Ubuntu:
  Incomplete

Bug description:
  i don't know what's happened

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: ibus 1.5.22-2ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 27 23:00:56 2020
  ExecutablePath: /usr/libexec/ibus-ui-gtk3
  InstallationDate: Installed on 2018-08-07 (598 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcCmdline: /usr/libexec/ibus-ui-gtk3
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: ibus
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message_expr()
  UpgradeStatus: Upgraded to focal on 2020-03-08 (19 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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

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


[Touch-packages] [Bug 1824724] Re: aa-logprof: german translation: ERROR: PromptUser: Ungültiges Tastenkürzel für V: Änderungen ansehen

2020-04-02 Thread Gunnar Hjalmarsson
This seems to have been fixed in eoan; disco is EOL. Closing.

** Changed in: apparmor
   Status: New => Invalid

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

** Changed in: language-pack-de (Ubuntu)
   Status: Confirmed => Fix Released

** Changed in: language-pack-de-base (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  aa-logprof: german translation: ERROR: PromptUser: Ungültiges
  Tastenkürzel für V: Änderungen ansehen

Status in AppArmor:
  Invalid
Status in Ubuntu Translations:
  Fix Released
Status in language-pack-de package in Ubuntu:
  Fix Released
Status in language-pack-de-base package in Ubuntu:
  Fix Released

Bug description:
  after the last Erl(a)uben [Allow] theres an errormessage:
  "ERROR: PromptUser: Ungültiges Tastenkürzel für V: Änderungen ansehen"
  see here:

  Profil:  /usr/bin/snap
  Pfad:/sys/kernel/security/apparmor/features/policy/versions/v5
  Neuer Modus: r
  Schweregrad: 4

   [1 - /sys/kernel/security/apparmor/features/policy/versions/v5 r,]
  Erl(a)uben / [A(b)lehnen] / (I)gnorieren / (G)lob / Glob with (E)xtension / 
(N)eu / Audi(t) / Abb(r)echen / En(d)e
  /sys/kernel/security/apparmor/features/policy/versions/v5 r, wird zum Profil 
hinzugefügt.

  ERROR: PromptUser: Ungültiges Tastenkürzel für V: Änderungen ansehen
  [view changes]

  imho it's a translation error.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1824724/+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 1869814] Re: ubuntu-docs build failure - possible solution

2020-04-01 Thread Gunnar Hjalmarsson
@Sebastien: Indeed, it's the very same thing. Then I spent several hours
on an issue that was already spotted and fixed. :(

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

Title:
  ubuntu-docs build failure - possible solution

Status in itstool package in Ubuntu:
  Invalid
Status in libxml2 package in Ubuntu:
  In Progress
Status in ubuntu-docs package in Ubuntu:
  Fix Released

Bug description:
  ubuntu-docs failed to build during the second Focal Fossa test
  rebuild:

  https://launchpad.net/ubuntu/+archive/test-
  rebuild-20200327-focal/+build/18982738

  It was itstool which failed to generate the localized zh_CN pages. If
  dropping zh_CN from ubuntu-help/Makefile.am, ubuntu-docs builds. But
  excluding the Chinese pages is apparently not an acceptable solution.

  The itstool package in focal {build-,}depends on python3. I built
  itstool in a PPA with python2 instead, and in that PPA ubuntu-docs
  built fine without modifications:

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

  So the root cause seems to lie neither in ubuntu-docs nor itstool. I
  would suspect that python3-libxml2 is buggy, but since itstool was
  built against python2 in eoan, it's hard to tell if it's a regression.

  Would building itstool against python2 be an acceptable workaround in
  focal?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/itstool/+bug/1869814/+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 1869814] Re: ubuntu-docs build failure - possible solution

2020-03-31 Thread Gunnar Hjalmarsson
Thanks Shaun! It's indeed that bug. Why am I not surprised when seeing
that you filed it? :)

I grabbed a Fedora patch and submitted a Debian merge request:

https://salsa.debian.org/xml-sgml-team/libxml2/-/merge_requests/3

It looks pretty spot on, don't you think? At least, with that patch
applied I can build ubuntu-docs 19.10.2 successfully again. A syntax
error in one of the Chinese translations is reported as warnings as
expected.

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

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

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

Title:
  ubuntu-docs build failure - possible solution

Status in itstool package in Ubuntu:
  Invalid
Status in libxml2 package in Ubuntu:
  In Progress
Status in ubuntu-docs package in Ubuntu:
  Fix Committed

Bug description:
  ubuntu-docs failed to build during the second Focal Fossa test
  rebuild:

  https://launchpad.net/ubuntu/+archive/test-
  rebuild-20200327-focal/+build/18982738

  It was itstool which failed to generate the localized zh_CN pages. If
  dropping zh_CN from ubuntu-help/Makefile.am, ubuntu-docs builds. But
  excluding the Chinese pages is apparently not an acceptable solution.

  The itstool package in focal {build-,}depends on python3. I built
  itstool in a PPA with python2 instead, and in that PPA ubuntu-docs
  built fine without modifications:

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

  So the root cause seems to lie neither in ubuntu-docs nor itstool. I
  would suspect that python3-libxml2 is buggy, but since itstool was
  built against python2 in eoan, it's hard to tell if it's a regression.

  Would building itstool against python2 be an acceptable workaround in
  focal?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/itstool/+bug/1869814/+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 1727908] Re: Software & Updates application does not permit changes on the "Other Software" tab

2020-03-31 Thread Gunnar Hjalmarsson
I see this issue in focal. Nothing happens if I try to enable or disable
a source in the "Other Software" tab by clicking a checkbox. I get the
same error message as mentioned in comment #2 if I start software-
properties-gtk in terminal.

Adding or removing sources works, but not enabling/disabling them.

** Tags added: focal

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

Title:
  Software & Updates application does not permit changes on the "Other
  Software" tab

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in software-properties package in Ubuntu:
  Confirmed
Status in gnome-shell source package in Bionic:
  Confirmed
Status in software-properties source package in Bionic:
  Confirmed

Bug description:
  
  On the "Other Software" tab, I am unable to select "Canonical Partners".
  Similarly, the other checkboxes on the "Other Software" can not be clicked.
  Clicking on a checkbox has no effect, and a dialog requesting the admin 
password is not presented.

  However, activating or deactivating checkboxes on other tabs causes an
  authorization dialog to be presented to the user.

  I experience this bug in an an Xorg session.

  sources.list and sources.list.d have the following permissions:
  -rw-r--r--   1 root root  2897 Oct 26 22:35 sources.list
  drwxr-xr-x   2 root root  4096 Oct 26 21:29 sources.list.d

  All files in sources.list.d have the following permissions as this example:
  -rw-r--r-- 1 root root  189 Oct 25 21:50 google-chrome.list

  $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  $ apt-cache policy software-properties-gtk
  software-properties-gtk:
Installed: 0.96.24.17
Candidate: 0.96.24.17
Version table:
   *** 0.96.24.17 500
  500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu artful/main i386 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: software-properties-gtk 0.96.24.17
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Oct 26 22:45:09 2017
  InstallationDate: Installed on 2017-10-26 (1 days ago)
  InstallationMedia: Ubuntu 17.10.0 2017.10.25 amd64 "Custom Artful Aardvark"
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: software-properties
  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/1727908/+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 1869814] Re: ubuntu-docs build failure - possible solution

2020-03-31 Thread Gunnar Hjalmarsson
Thanks Sebastien!

Or https://gitlab.gnome.org/GNOME/libxml2/issues/64 (which is not yet
closed).

@Boyuan: Well, it does scream loudly in the sense that the build fails.

I wouldn't blame the build system in this case. It has worked in a
sensible and robust way for many years. The segfault issue only happens
with python3-libxml2, not with python-libxml2. And I have the impression
(not yet confirmed) that the segfault only happens for XML syntax errors
in Chinese translations; for similar errors in non-Chinese translations
it only prints a warning and moves on (which is the desired behavior).

** Bug watch added: gitlab.gnome.org/GNOME/libxml2/issues #64
   https://gitlab.gnome.org/GNOME/libxml2/issues/64

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

Title:
  ubuntu-docs build failure - possible solution

Status in itstool package in Ubuntu:
  Invalid
Status in libxml2 package in Ubuntu:
  New
Status in ubuntu-docs package in Ubuntu:
  Fix Committed

Bug description:
  ubuntu-docs failed to build during the second Focal Fossa test
  rebuild:

  https://launchpad.net/ubuntu/+archive/test-
  rebuild-20200327-focal/+build/18982738

  It was itstool which failed to generate the localized zh_CN pages. If
  dropping zh_CN from ubuntu-help/Makefile.am, ubuntu-docs builds. But
  excluding the Chinese pages is apparently not an acceptable solution.

  The itstool package in focal {build-,}depends on python3. I built
  itstool in a PPA with python2 instead, and in that PPA ubuntu-docs
  built fine without modifications:

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

  So the root cause seems to lie neither in ubuntu-docs nor itstool. I
  would suspect that python3-libxml2 is buggy, but since itstool was
  built against python2 in eoan, it's hard to tell if it's a regression.

  Would building itstool against python2 be an acceptable workaround in
  focal?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/itstool/+bug/1869814/+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 1869814] Re: ubuntu-docs build failure - possible solution

2020-03-31 Thread Gunnar Hjalmarsson
Uploaded a new version of ubuntu-docs, which builds on focal despite the
issue discussed in this bug report.

** Changed in: ubuntu-docs (Ubuntu)
   Status: New => Fix Committed

** Changed in: ubuntu-docs (Ubuntu)
 Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

** Tags added: focal regression-release

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

Title:
  ubuntu-docs build failure - possible solution

Status in itstool package in Ubuntu:
  New
Status in libxml2 package in Ubuntu:
  New
Status in ubuntu-docs package in Ubuntu:
  Fix Committed

Bug description:
  ubuntu-docs failed to build during the second Focal Fossa test
  rebuild:

  https://launchpad.net/ubuntu/+archive/test-
  rebuild-20200327-focal/+build/18982738

  It was itstool which failed to generate the localized zh_CN pages. If
  dropping zh_CN from ubuntu-help/Makefile.am, ubuntu-docs builds. But
  excluding the Chinese pages is apparently not an acceptable solution.

  The itstool package in focal {build-,}depends on python3. I built
  itstool in a PPA with python2 instead, and in that PPA ubuntu-docs
  built fine without modifications:

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

  So the root cause seems to lie neither in ubuntu-docs nor itstool. I
  would suspect that python3-libxml2 is buggy, but since itstool was
  built against python2 in eoan, it's hard to tell if it's a regression.

  Would building itstool against python2 be an acceptable workaround in
  focal?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/itstool/+bug/1869814/+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 1869814] Re: ubuntu-docs build failure - possible solution

2020-03-30 Thread Gunnar Hjalmarsson
@Shaun: Have you possibly stumbled into anything similar when building
e.g. gnome-user-docs?

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

Title:
  ubuntu-docs build failure - possible solution

Status in itstool package in Ubuntu:
  New
Status in libxml2 package in Ubuntu:
  New
Status in ubuntu-docs package in Ubuntu:
  New

Bug description:
  ubuntu-docs failed to build during the second Focal Fossa test
  rebuild:

  https://launchpad.net/ubuntu/+archive/test-
  rebuild-20200327-focal/+build/18982738

  It was itstool which failed to generate the localized zh_CN pages. If
  dropping zh_CN from ubuntu-help/Makefile.am, ubuntu-docs builds. But
  excluding the Chinese pages is apparently not an acceptable solution.

  The itstool package in focal {build-,}depends on python3. I built
  itstool in a PPA with python2 instead, and in that PPA ubuntu-docs
  built fine without modifications:

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

  So the root cause seems to lie neither in ubuntu-docs nor itstool. I
  would suspect that python3-libxml2 is buggy, but since itstool was
  built against python2 in eoan, it's hard to tell if it's a regression.

  Would building itstool against python2 be an acceptable workaround in
  focal?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/itstool/+bug/1869814/+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 1869814] Re: ubuntu-docs build failure - possible solution

2020-03-30 Thread Gunnar Hjalmarsson
Hmm.. I saw in the buildlog from the successful build that it skipped
the Chinese translation of a particular string. The reason proved to be
a missing '<' character, i.e. the translated string contains an instance
of '/em>' instead of ''. And that's the correct behavior; it should
check the Mallard syntax and skip translations with invalid syntax.

Anyway, I added the missing '<', and then ubuntu-docs built with the
itstool version in focal.

So the direct reason for the build failure is a syntactically incorrect
translation. OTOH, translators make mistakes, and a bad translation
*should not* make the whole package build to fail.

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

Title:
  ubuntu-docs build failure - possible solution

Status in itstool package in Ubuntu:
  New
Status in libxml2 package in Ubuntu:
  New
Status in ubuntu-docs package in Ubuntu:
  New

Bug description:
  ubuntu-docs failed to build during the second Focal Fossa test
  rebuild:

  https://launchpad.net/ubuntu/+archive/test-
  rebuild-20200327-focal/+build/18982738

  It was itstool which failed to generate the localized zh_CN pages. If
  dropping zh_CN from ubuntu-help/Makefile.am, ubuntu-docs builds. But
  excluding the Chinese pages is apparently not an acceptable solution.

  The itstool package in focal {build-,}depends on python3. I built
  itstool in a PPA with python2 instead, and in that PPA ubuntu-docs
  built fine without modifications:

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

  So the root cause seems to lie neither in ubuntu-docs nor itstool. I
  would suspect that python3-libxml2 is buggy, but since itstool was
  built against python2 in eoan, it's hard to tell if it's a regression.

  Would building itstool against python2 be an acceptable workaround in
  focal?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/itstool/+bug/1869814/+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 1869814] Re: ubuntu-docs build failure - possible solution

2020-03-30 Thread Gunnar Hjalmarsson
@Boyuan: Do you have any thoughts on the above?

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

Title:
  ubuntu-docs build failure - possible solution

Status in itstool package in Ubuntu:
  New
Status in libxml2 package in Ubuntu:
  New
Status in ubuntu-docs package in Ubuntu:
  New

Bug description:
  ubuntu-docs failed to build during the second Focal Fossa test
  rebuild:

  https://launchpad.net/ubuntu/+archive/test-
  rebuild-20200327-focal/+build/18982738

  It was itstool which failed to generate the localized zh_CN pages. If
  dropping zh_CN from ubuntu-help/Makefile.am, ubuntu-docs builds. But
  excluding the Chinese pages is apparently not an acceptable solution.

  The itstool package in focal {build-,}depends on python3. I built
  itstool in a PPA with python2 instead, and in that PPA ubuntu-docs
  built fine without modifications:

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

  So the root cause seems to lie neither in ubuntu-docs nor itstool. I
  would suspect that python3-libxml2 is buggy, but since itstool was
  built against python2 in eoan, it's hard to tell if it's a regression.

  Would building itstool against python2 be an acceptable workaround in
  focal?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/itstool/+bug/1869814/+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 1869814] [NEW] ubuntu-docs build failure - possible solution

2020-03-30 Thread Gunnar Hjalmarsson
Public bug reported:

ubuntu-docs failed to build during the second Focal Fossa test rebuild:

https://launchpad.net/ubuntu/+archive/test-
rebuild-20200327-focal/+build/18982738

It was itstool which failed to generate the localized zh_CN pages. If
dropping zh_CN from ubuntu-help/Makefile.am, ubuntu-docs builds. But
excluding the Chinese pages is apparently not an acceptable solution.

The itstool package in focal {build-,}depends on python3. I built
itstool in a PPA with python2 instead, and in that PPA ubuntu-docs built
fine without modifications:

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

So the root cause seems to lie neither in ubuntu-docs nor itstool. I
would suspect that python3-libxml2 is buggy, but since itstool was built
against python2 in eoan, it's hard to tell if it's a regression.

Would building itstool against python2 be an acceptable workaround in
focal?

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

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

** Affects: ubuntu-docs (Ubuntu)
 Importance: Undecided
 Status: New

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

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

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

Title:
  ubuntu-docs build failure - possible solution

Status in itstool package in Ubuntu:
  New
Status in libxml2 package in Ubuntu:
  New
Status in ubuntu-docs package in Ubuntu:
  New

Bug description:
  ubuntu-docs failed to build during the second Focal Fossa test
  rebuild:

  https://launchpad.net/ubuntu/+archive/test-
  rebuild-20200327-focal/+build/18982738

  It was itstool which failed to generate the localized zh_CN pages. If
  dropping zh_CN from ubuntu-help/Makefile.am, ubuntu-docs builds. But
  excluding the Chinese pages is apparently not an acceptable solution.

  The itstool package in focal {build-,}depends on python3. I built
  itstool in a PPA with python2 instead, and in that PPA ubuntu-docs
  built fine without modifications:

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

  So the root cause seems to lie neither in ubuntu-docs nor itstool. I
  would suspect that python3-libxml2 is buggy, but since itstool was
  built against python2 in eoan, it's hard to tell if it's a regression.

  Would building itstool against python2 be an acceptable workaround in
  focal?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/itstool/+bug/1869814/+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 1869641] Re: Failed to launch ibus daemon in Xwayland + gnome-shell 3.36.0

2020-03-30 Thread Gunnar Hjalmarsson
Thanks for your report and your investigation! Attached a debdiff which
adds that upstream commit.

** Patch added: "ibus_lp1869641.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1869641/+attachment/5343294/+files/ibus_lp1869641.debdiff

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

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

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

** Tags added: patch

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

Title:
  Failed to launch ibus daemon in Xwayland + gnome-shell 3.36.0

Status in ibus package in Ubuntu:
  In Progress

Bug description:
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  ibus 1.5.22-2ubuntu1

  Steps to reproduce

1. Upgrade to GNOME 3.36.0.
2. Restart Ubuntu 20.04 daily with Wayland

  What did you expect to happen
The ibus daemon is launched.

  What happened
The ibus daemon is not running.

  
  I can confirm I have an exact same issue in 
https://gitlab.gnome.org/GNOME/gnome-shell/issues/2341 when login with wayland 
selected.

  After applying this:
  https://github.com/ibus/ibus/commit/8ce25208c3f4adfd290a032c6aa739d2b7580eb1
  patch locally I can confirm it fixed my issue.

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

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


[Touch-packages] [Bug 1869484] Re: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message.cold()

2020-03-28 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/1869484

Title:
  ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message.cold()

Status in ibus package in Ubuntu:
  New

Bug description:
  i don't know what's happened

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: ibus 1.5.22-2ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 27 23:00:56 2020
  ExecutablePath: /usr/libexec/ibus-ui-gtk3
  InstallationDate: Installed on 2018-08-07 (598 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcCmdline: /usr/libexec/ibus-ui-gtk3
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: ibus
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message_expr()
  UpgradeStatus: Upgraded to focal on 2020-03-08 (19 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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

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


[Touch-packages] [Bug 1867090] Re: IBus 1.5.21 Chinese input in Ubuntu 19.10 not working with Atom 1.45.0 as snap

2020-03-27 Thread Gunnar Hjalmarsson
Thanks!

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

** No longer affects: snappy

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

Title:
  IBus 1.5.21 Chinese input in Ubuntu 19.10 not working with Atom 1.45.0
  as snap

Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  OS: Ubuntu 19.10
  IBus version: 1.5.21
  Atom version: 1.45.0

  When I switch to Chinese input mode (Intelligent Pinyin) and try to type 
Chinese into Atom 1.45.0 (snap version), it simply doesn't work.
  When I type the letters into the window, it shall bring up the candidate list 
for me to pick words. But instead, the letters are directly typed into the 
window, but not Chinese characters.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1867090/+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 1865907] Re: Loading IM context type 'ibus' failed

2020-03-24 Thread Gunnar Hjalmarsson
** Package changed: glib2.0 (Debian) => ibus (Debian)

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

Title:
  Loading IM context type 'ibus' failed

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in ibus package in Ubuntu:
  Fix Released
Status in ibus package in Debian:
  Unknown

Bug description:
  Regression issue caused by recent system updates on Ubuntu 20.04 Focal
  Fossa (development branch)

  Many(or to say, most) applications,like eclipse,lazarus,gnome-shell,gedit... 
reported below error in syslog or console as,
  ...
  (lazarus-ide:20387): Gtk-WARNING **: 00:11:55.562: Loading IM context type 
'ibus' failed
  (lazarus-ide:20387): Gtk-WARNING **: 00:11:55.566: GModule 
(/usr/lib/x86_64-linux-gnu/gtk-2.0/2.10.0/immodules/im-ibus.so) initialization 
check failed: GLib version too old (micro mismatch)
  ...

  and Pinyin input method does not work in these applications.

  Symptom occurs since I updated below 17 packages some hours before,
  gir1.2-ibus-1.0
  gvfs
  gvfs-backends
  gvfs-bin
  gvfs-common
  gvfs-daemons
  gvfs-fuse
  gvfs-libs
  ibus
  ibus-data
  ibus-gtk
  ibus-gtk3
  libglib2.0-0
  libgtk-3-0
  libgtk2.0-0
  libibus-1.0-5
  python3-ibus-1.0

  current versions of above packages are,
  gir1.2-ibus-1.0/focal,now 1.5.22-1~exp1ubuntu1 amd64 [installed]
  gvfs/focal,now 1.43.92-1ubuntu1 amd64 [installed]
  gvfs-backends/focal,now 1.43.92-1ubuntu1 amd64 [installed,automatic]
  gvfs-bin/focal,now 1.43.92-1ubuntu1 amd64 [installed]
  gvfs-common/focal,focal,now 1.43.92-1ubuntu1 all [installed]
  gvfs-daemons/focal,now 1.43.92-1ubuntu1 amd64 [installed]
  gvfs-fuse/focal,now 1.43.92-1ubuntu1 amd64 [installed]
  gvfs-libs/focal,now 1.43.92-1ubuntu1 amd64 [installed]
  ibus/focal,now 1.5.22-1~exp1ubuntu1 amd64 [installed,automatic]
  ibus-data/focal,focal,now 1.5.22-1~exp1ubuntu1 all [installed,automatic]
  ibus-gtk/focal,now 1.5.22-1~exp1ubuntu1 amd64 [installed]
  ibus-gtk3/focal,now 1.5.22-1~exp1ubuntu1 amd64 [installed]
  libglib2.0-0/focal,now 2.63.5-2 amd64 [installed]
  libgtk-3-0/focal,now 3.24.13-1ubuntu1 amd64 [installed]
  libgtk2.0-0/focal,now 2.24.32-4ubuntu4 amd64 [installed]
  libibus-1.0-5/focal,now 1.5.22-1~exp1ubuntu1 amd64 [installed]
  python3-ibus-1.0/focal,focal,now 1.5.22-1~exp1ubuntu1 all 
[installed,automatic]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1865907/+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 1865907] Re: Loading IM context type 'ibus' failed

2020-03-21 Thread Gunnar Hjalmarsson
Reopening the ibus task, since there is a fix in Debian which will
prevent this issue from showing up going forward.

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

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

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

** Also affects: glib2.0 (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954207
   Importance: Unknown
   Status: Unknown

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

Title:
  Loading IM context type 'ibus' failed

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in ibus package in Ubuntu:
  In Progress
Status in glib2.0 package in Debian:
  Unknown

Bug description:
  Regression issue caused by recent system updates on Ubuntu 20.04 Focal
  Fossa (development branch)

  Many(or to say, most) applications,like eclipse,lazarus,gnome-shell,gedit... 
reported below error in syslog or console as,
  ...
  (lazarus-ide:20387): Gtk-WARNING **: 00:11:55.562: Loading IM context type 
'ibus' failed
  (lazarus-ide:20387): Gtk-WARNING **: 00:11:55.566: GModule 
(/usr/lib/x86_64-linux-gnu/gtk-2.0/2.10.0/immodules/im-ibus.so) initialization 
check failed: GLib version too old (micro mismatch)
  ...

  and Pinyin input method does not work in these applications.

  Symptom occurs since I updated below 17 packages some hours before,
  gir1.2-ibus-1.0
  gvfs
  gvfs-backends
  gvfs-bin
  gvfs-common
  gvfs-daemons
  gvfs-fuse
  gvfs-libs
  ibus
  ibus-data
  ibus-gtk
  ibus-gtk3
  libglib2.0-0
  libgtk-3-0
  libgtk2.0-0
  libibus-1.0-5
  python3-ibus-1.0

  current versions of above packages are,
  gir1.2-ibus-1.0/focal,now 1.5.22-1~exp1ubuntu1 amd64 [installed]
  gvfs/focal,now 1.43.92-1ubuntu1 amd64 [installed]
  gvfs-backends/focal,now 1.43.92-1ubuntu1 amd64 [installed,automatic]
  gvfs-bin/focal,now 1.43.92-1ubuntu1 amd64 [installed]
  gvfs-common/focal,focal,now 1.43.92-1ubuntu1 all [installed]
  gvfs-daemons/focal,now 1.43.92-1ubuntu1 amd64 [installed]
  gvfs-fuse/focal,now 1.43.92-1ubuntu1 amd64 [installed]
  gvfs-libs/focal,now 1.43.92-1ubuntu1 amd64 [installed]
  ibus/focal,now 1.5.22-1~exp1ubuntu1 amd64 [installed,automatic]
  ibus-data/focal,focal,now 1.5.22-1~exp1ubuntu1 all [installed,automatic]
  ibus-gtk/focal,now 1.5.22-1~exp1ubuntu1 amd64 [installed]
  ibus-gtk3/focal,now 1.5.22-1~exp1ubuntu1 amd64 [installed]
  libglib2.0-0/focal,now 2.63.5-2 amd64 [installed]
  libgtk-3-0/focal,now 3.24.13-1ubuntu1 amd64 [installed]
  libgtk2.0-0/focal,now 2.24.32-4ubuntu4 amd64 [installed]
  libibus-1.0-5/focal,now 1.5.22-1~exp1ubuntu1 amd64 [installed]
  python3-ibus-1.0/focal,focal,now 1.5.22-1~exp1ubuntu1 all 
[installed,automatic]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1865907/+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 1848202] Re: Use after free in gdbus leads to eds segfaults

2020-03-17 Thread Gunnar Hjalmarsson
Bug #1844853 was explicitly verified (again, comment #31 this time).
Didn't observe any unexpected behavior due to the glib2.0 upgrade.

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

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

Title:
  Use after free in gdbus leads to eds segfaults

Status in GLib:
  Fix Released
Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Eoan:
  Fix Committed

Bug description:
  [ Description ]

  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
evolution-data-server.  This problem was most recently seen with package 
version 3.34.1-1, the problem page at 
https://errors.ubuntu.com/problem/b1f62616406e36e521fd1fb1d2be4ac2fe9a2cda 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

  [ Fix ]

  This bug was fixed upstream in 2.62.2 (see the links below). That
  update is being issues to eoan.

  [ QA ]

  Under https://wiki.ubuntu.com/StableReleaseUpdates/GNOME, we don't
  need to explicitly test that this bug is fixed. Nevertheless, to
  verify this bug please give the desktop a good workout. Ideally
  install the SRU and use your machine as you would normally for a
  variety of tasks. Make sure there are no regressions.

  [ Regression potential ]

  1) The changes involve mutexes and stuff, which is error prone.

  2) It's GLib, a core library, so any bad regressions will be really
  serious for the desktop as a whole.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glib/+bug/1848202/+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 1850932] Re: [SRU] Backport 2.62.4-1

2020-03-17 Thread Gunnar Hjalmarsson
Bug #1844853 was explicitly verified (again, comment #31 this time).
Didn't observe any unexpected behavior due to the glib2.0 upgrade.

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

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

Title:
  [SRU] Backport 2.62.4-1

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Eoan:
  Fix Committed

Bug description:
  [ Description ]

  I'm creating this bug report to have a place to describe the proposed
  backport of glib2.0 2.62.4-1 from focal.

  One purpose of this backport is to fix bug #1844853.

  But there are several other changes. Here's the diff of NEWS:

  +Overview of changes in GLib 2.62.4
  +==
  +
  +* Apply recursion depth limits to variants in D-Bus messages (!1290)
  +
  +* Bugs fixed:
  + - #1938 GDateTime doesn't support leap seconds
  + - !1240 Backport !1233 “gdatetime: Handle leap seconds in ISO8601 dates” 
+to glib-2-62
  + - !1257 Backport !1232 “kqueue: Do not return early from _kqsub_cancel” +to 
glib-2-62
  + - !1266 Backport !1265 “build: don't check for protected visibility” to 
+glib-2-62
  + - !1276 Backport !1274 “trash portal: Don't follow symlinks” to glib-2-62
  + - !1290 Backport !1201 “gdbusmessage: Limit recursion of variants in +D-Bus 
messages” to glib-2-62
  +
  +Overview of changes in GLib 2.62.3
  +==
  +
  +* Use `poll()` in `g_spawn_sync()` rather than `select()`, which is subject 
to
  +  FD limits (#954)
  +
  +* Fix undefined behaviour with `g_utf8_find_prev_char()` (#1917)
  +
  +* Bugs fixed:
  + - #954 The g_spawn_sync() function uses select() which has limitations
  + - #1318 rare failure in gdbus-peer test: invalid uninstantiatable type 
'(null)' in cast to 'GDBusServer'
  + - #1897 glib 2.62.0 fails test 'test_writev_no_vectors' wih gcc7
  + - #1903 use-after-free in mimeapps test causes intermittent segfault during 
testing
  + - #1916 objcopy not used from cross-compilation file in GIO tests
  + - #1917 Test utf8-pointer fails with static build, LTO, optimisations, and 
new GCC
  + - !1174 Backport !1164 “use-after-free fix in mimeapps test” to glib-2-62
  + - !1184 Backport !1173 “gvariant: Limit recursion in g_variant_parse()” to 
glib-2-62
  + - !1194 Backport !1176, !1183, !1188, !1191 to `glib-2-62`
  + - !1203 Backport !1192, !1193, !1197 Fixes for gdbus-peer tests to glib-2-62
  + - !1207 Backport !1206 “goption: Relax assertion to avoid being broken by 
kdeinit5” to glib-2-62
  + - !1215 [2.62] gdbus-peer: Specifically listen on 127.0.0.1
  + - !1219 Backport !1218 “gdb: Fix GHashTable pretty printer off-by-one error”
  + - !1222 Backport !1221 “Add NOTE_REVOKE to the list of the monitoring 
events” to glib-2-62
  + - !1228 Backport !1199 “gunicode: Fix UB in gutf8.c and utf8-pointer test” 
to glib-2-62
  +
  +
  +Overview of changes in GLib 2.62.2
  +==
  +
  +* Bugs fixed:
  + - #1896 Use after free when calling g_dbus_connection_flush_sync() in a 
dedicated thread
  + - !1154 Backport !1152 “gwinhttpvfs: Handle g_get_prgname() returning NULL” 
to glib-2-62
  + - !1156 Backport !1146 Solaris fixes to glib-2-62

  This release can be considered to be tested under
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  There are patches from the upstream master branch rather than this
  stable release:

  + Add-a-test-for-GDBusServer-authentication.patch
  + gdbus-server-auth-test-Create-temporary-directory-for-Uni.patch
  + gdbus-server-auth-test-Include-gcredentialsprivate.h.patch
  + Make-ld-executable-configurable.patch

  They are sensible backports which I hope are appropriate for SRU.

  [ QA ]

  The testsuite fixes will verify themselves during the build and
  autopkgtest.

  For the rest of the fixes, please exercise the desktop thoroughly. Log
  in, log out, run many applications and make sure there are no
  regressions.

  [ Regression potential ]

  test fixes> Build failures or autopkgtest failures.

  GLib is a central desktop library. Regressions could break any part of
  the desktop - so QA is important, the SRU exception notwithstanding.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1850932/+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 1844853] Re: IBus no longer works in Qt applications after upgrade

2020-03-17 Thread Gunnar Hjalmarsson
I have verified the testcase on eoan using version
2.62.4-1~ubuntu19.10.1 of the libglib2.0-* packages from eoan-proposed
and version 1.5.21-1~exp2ubuntu2.1 of the ibus packages from ppa:ubuntu-
security-proposed/ppa.

As regards the autopkgtest failure, please see:

https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1850932/comments/12

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

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

Title:
  IBus no longer works in Qt applications after upgrade

Status in GLib:
  Fix Released
Status in ibus:
  Fix Released
Status in glib2.0 package in Ubuntu:
  Fix Released
Status in ibus package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Xenial:
  Fix Committed
Status in glib2.0 source package in Bionic:
  Fix Committed
Status in glib2.0 source package in Disco:
  Won't Fix
Status in glib2.0 source package in Eoan:
  Fix Committed
Status in glib2.0 source package in Focal:
  Fix Released
Status in ibus source package in Focal:
  Fix Released
Status in glib2.0 package in Debian:
  Fix Released

Bug description:
  [Impact]

  IBus was broken for Qt applications as a regression due to the fix of
  CVE-2019-14822. As a result the IBus patch was disabled temporarily,
  which fixed IBus from a usability POV.

  The real fix has been made in glib2.0, and the updates in -proposed
  will allow the IBus patch to be re-enabled.

  [Test Case]

   * On a standard Ubuntu {eoan,disco,bionic,xenial} installation
     - Upgrade the glib2.0 packages from
   {eoan,disco,bionic,xenial}-proposed
     - Upgrade the ibus packages from
   https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa
     - Install some IBus input method, e.g. ibus-libpinyin
     - Install some Qt application, e.g. Kate

  * Relogin (maybe reboot)

  * Add the input method to the input sources

  * Open the Qt app and try to input something using the IBus IM

  => Find that the transliteration works as expected

  [Regression Potential]

  The applicable patches origin from glib upstream:
  https://gitlab.gnome.org/GNOME/glib/merge_requests/1176
  Consequently the changes have been reviewed by the glib maintainer, but also 
tested by the IBus maintainer, by me (gunnarhj), and - of course - the author 
Simon McVittie. The changes have been in Debian unstable since 2019-10-30.

  [Original description]

  Kubuntu Release 18.04.3 LTS

  Expected behavior:
  ibus continues working as before after applying security update 
1.5.17-ubuntu5.1 from version 1.5.17-ubuntu5.

  Observed behavior:
  ibus is not usable anymore in Qt applications.

  After updating ibus and the related packages ibus-gtk, ibus-gtk3, 
libibus-1.0-5 and gir1.2-ibus-1.0 all from version 1.5.17-ubuntu5 to 
1.5.17-ubuntu5.1, I can no longer use ibus in Qt applications. Using 
shift-space no longer changes the selected input method and even when i switch 
to the mozc input method in a gtk application, i can not use it in any Qt 
applications.
  When starting qtconfig in a terminal, I also get the following message:

  Bus::open: Connect ibus failed!
  IBusInputContext::createInputContext: no connection to ibus-daemon

  This bug was not present in version 1.5.17-3ubuntu5 and I also
  confirmed that downgrading the packages to version 1.5.17-3ubuntu4
  restores ibus functionality in Qt applications.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu5.1
  ProcVersionSignature: Ubuntu 5.0.0-30.32~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-30-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Sep 21 07:58:56 2019
  InstallationDate: Installed on 2019-06-28 (84 days ago)
  InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/glib/+bug/1844853/+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 1864982] Re: Ubuntu desktop computer doesn't seem to lock correctly

2020-03-16 Thread Gunnar Hjalmarsson
Ok, thanks. Since LightDM is not the default DM on Ubuntu 18.04, I set
the importance of this bug to "Low".

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

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

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

Title:
  Ubuntu desktop computer doesn't seem to lock correctly

Status in lightdm package in Ubuntu:
  New

Bug description:
  Ubuntu desktop computer doesn't seem to lock correctly if I click "Lock 
Screen" it does lock if I use shortcut. If I use the "lock screen" button then 
anyone can unlock it by merely pressing "ctrl+alt+f7".
  The problem is not that I cannot lock my screen, the problem is I was under 
the impression that my computer was being locked when it was not.
  now that I know that the "Lock Screen" button doesn't work correctly I know 
of other ways to lock my computer still the lock screen button should work and 
it looks like it locked my screen,but if I press "ctrl+alt+f7" then it 
magically unlocks

  So it is a security incident.

  Thanks in Advance.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1864982/+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 1864982] Re: Ubuntu desktop computer doesn't seem to lock correctly

2020-03-16 Thread Gunnar Hjalmarsson
So did you replace GDM with LightDM on your Ubuntu installs? If you
didn't, this may actually be a gnome-shell and/or gdm3 issue. Please
clarify.

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

Title:
  Ubuntu desktop computer doesn't seem to lock correctly

Status in lightdm package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu desktop computer doesn't seem to lock correctly if I click "Lock 
Screen" it does lock if I use shortcut. If I use the "lock screen" button then 
anyone can unlock it by merely pressing "ctrl+alt+f7".
  The problem is not that I cannot lock my screen, the problem is I was under 
the impression that my computer was being locked when it was not.
  now that I know that the "Lock Screen" button doesn't work correctly I know 
of other ways to lock my computer still the lock screen button should work and 
it looks like it locked my screen,but if I press "ctrl+alt+f7" then it 
magically unlocks

  So it is a security incident.

  Thanks in Advance.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1864982/+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 1864982] Re: Ubuntu desktop computer doesn't seem to lock correctly

2020-03-16 Thread Gunnar Hjalmarsson
That's distro... I think Marc asked about if you use Ubuntu with GNOME,
Xubuntu, Lubuntu, or Budgie etc.

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

Title:
  Ubuntu desktop computer doesn't seem to lock correctly

Status in lightdm package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu desktop computer doesn't seem to lock correctly if I click "Lock 
Screen" it does lock if I use shortcut. If I use the "lock screen" button then 
anyone can unlock it by merely pressing "ctrl+alt+f7".
  The problem is not that I cannot lock my screen, the problem is I was under 
the impression that my computer was being locked when it was not.
  now that I know that the "Lock Screen" button doesn't work correctly I know 
of other ways to lock my computer still the lock screen button should work and 
it looks like it locked my screen,but if I press "ctrl+alt+f7" then it 
magically unlocks

  So it is a security incident.

  Thanks in Advance.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1864982/+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 1855514] Re: ibus preferences do not show up in search or indicator bar

2020-03-14 Thread Gunnar Hjalmarsson
Thanks for your report! It's not a bug, though.

$ cat /usr/share/applications/org.freedesktop.IBus.Setup.desktop | grep '# 
GNOME' -A 1
# GNOME uses its own "input source" settings instead
NotShowIn=GNOME;Unity;

IBus is integrated into the GNOME desktop, and normally the UI provided
by Settings -> Region & Language is sufficient.

Closing.

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

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

Title:
  ibus preferences do not show up in search or indicator bar

Status in ibus package in Ubuntu:
  Invalid

Bug description:
  This might be two separate bugs. But I feel like they have the same
  root, so I reported them as one.

  Remarks:
  [1] This report is *not* related to bug 1854610 in ibus-anthy (Ubuntu) "No 
Japanese input possible after upgrade from 19.04 to 19.10" [Undecided,New] 
https://launchpad.net/bugs/1854610

  [2] This report might be related to
  https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1580463, but I'm
  not sure. Someone with more technical knowledge should look into this.

   1 ---
  steps to reproduce:
  1) Have a fresh ubuntu 19.10 installation
  2) install ibus and ibus-anthy
  3) press windows key to open all applications
  4) type in ibus

  Actual:
  5) ibus settings will not show up

  Expected:
  5) ibus settings show up

  Workaround:
  6) open Software center
  7) search for ibus
  8) click "launch there"

   2 --
  steps to reproduce:
  1) Have a fresh Ubuntu 19.10 installation
  2) install ibus and ibus-anthy
  3) Set input method to "ibus"
  4) restart

  Actual:
  5) ibus preferences do not show up in the top bar at the indicators

  Expected
  6) "ibus preferences" is visible at the top bar inside the indicators area.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ibus 1.5.21-1~exp2ubuntu2
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec  7 13:10:27 2019
  SourcePackage: ibus
  UpgradeStatus: no upgrade log present

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1855514/+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   >