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

** Changed in: accountsservice (Ubuntu Kinetic) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1974250 Title: ~/.pam_envi

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

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

[Touch-packages] [Bug 1976255] Re: accountsservice ftbfs in the jammy release pocket

This was fixed via accountsservice 22.07.5-2ubuntu1.3 in jammy-updates. ** Changed in: accountsservice (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. htt

[Touch-packages] [Bug 1999207] Re: Error in dead key management of latin keyboards

Thanks for your report. I can't reproduce it, though. Whether the layout is "French (alt., Latin-9 only)" or "Swedish" I can type the dead_circumflex symbol followed by u, and get û. For me that works also with Firefox. Which physical keys are you using to type dead_circumflex? To access that sym

[Touch-packages] [Bug 1999207] Re: Error in dead key management of latin keyboards

I also tested on Xubuntu 22.10, which I happen to have access to. The reason is that I there (unlike on GNOME) can disable ibus completely. Using the Mozilla tool you linked to, and with ibus disabled, I get: compositionstart: compositionend: in the event log (even if the û character is shown

[Touch-packages] [Bug 1999207] Re: Error in dead key management of latin keyboards

Are you using some layout which is not provided by xkb-data? The one I used is named "French (alt., Latin-9 only)" and is represented by the dconf value fr+oss_latin9. The dconf value fr+latin9 is also available, but the name of that layout is "French (legacy, alt.)". I'm not sure about the signi

[Touch-packages] [Bug 1999207] Re: Error in dead key management of latin keyboards

On 2022-12-13 19:40, Sharcoux wrote: > layout: fr,fr > variant:latin9,oss Then it's the "French (legacy, alt.)" layout you use. And yes, with that layout you get dead_circumflex by simply pressing the key to the right of the P key. (But I think the layout used to make use of some dead key

[Touch-packages] [Bug 1999698] Re: Dodgy looking patch applied to our build.

Please see https://salsa.debian.org/freedesktop- team/accountsservice/-/commit/19eaa3f1 ** Changed in: accountsservice (Ubuntu) Status: New => Fix Committed ** Changed in: accountsservice (Ubuntu) Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj) -- You received th

[Touch-packages] [Bug 1999207] Re: Error in dead key management of latin keyboards

That UI is a three step thing. From the first view you should click "More..." (three vertically aligned dots), in the second view you should scroll to the bottom and there click "Other". Then you ought to see a very long list, including the one I mentioned. -- You received this bug notification b

[Touch-packages] [Bug 1999986] Re: ibus-daemon 170% CPU when using Flatpak Endeavour

Can you please install endeavour from the Ubuntu archive sudo apt install endeavour and let us know if the issue is present also when using that version of it. ** Changed in: ibus (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu

[Touch-packages] [Bug 1999207] Re: Error in dead key management of latin keyboards

Good. Then let me try to explain the nature of the problem you encountered. It's not really an ibus issue. But GNOME integrates ibus into its desktop, and this is about the way they do so. ibus is started and configured by default in GNOME desktops. But for some reason they have an on/off mechani

[Touch-packages] [Bug 2000551] Re: [System Fonts] Replace default sinhala font from LKLUG to Noto

Hi Aurora, and thanks for your report. I see that LKLUG is pulled by default by several meta packages, and I'd prefer to avoid stopping them from doing that. $ apt rdepends fonts-lklug-sinhala fonts-lklug-sinhala Reverse Depends: Recommends: ubuntu-desktop Recommends: xubuntu-desktop Recomm

[Touch-packages] [Bug 2000551] Re: [System Fonts] Replace default sinhala font from LKLUG to Noto

nged in: language-selector (Ubuntu) Importance: Undecided => Wishlist ** Changed in: language-selector (Ubuntu) Status: New => Fix Committed ** Changed in: language-selector (Ubuntu) Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj) ** Changed in: language-selector (Ubuntu

[Touch-packages] [Bug 1999986] Re: ibus-daemon 170% CPU when using Flatpak Endeavour

A long shot: Install gnome-session: sudo apt install gnome-session log in to a "vanilla" GNOME session and see if you notice a difference with respect to the endeavour behavior. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed t

[Touch-packages] [Bug 2000551] Re: [System Fonts] Replace default sinhala font from LKLUG to Noto

On 2023-01-04 18:46, Robie Basak wrote: > What's the plan for Kinetic? Please see: > https://wiki.ubuntu.com/StableReleaseUpdates#Newer_Releases The plan is to be lazy and skip kinetic. ;) Actually, in this particular case it shouldn't be a problem. If a user with an updated jammy (including this

[Touch-packages] [Bug 2000551] Re: [System Fonts] Replace default sinhala font from LKLUG to Noto

27;t Fix => In Progress ** Changed in: language-selector (Ubuntu Kinetic) Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj) ** Description changed: [ Impact ] The current default font for Sinhala (LKLUG) is unmaintained and comes with issues. Noto offers Sinh

[Touch-packages] [Bug 2000551] Re: [System Fonts] Replace default sinhala font from LKLUG to Noto

I have accomplished the steps in the test plan: * for jammy with language-selector-[common,gnome] 0.219.1 * for kinetic with language-selector-[common,gnome] 0.219.22.10.1 and can verify the expected improvement. (The kinetic verification was made on Xubuntu 22.10 where fonts-noto-core is instal

[Touch-packages] [Bug 1999986] Re: ibus-daemon 170% CPU when using Flatpak Endeavour

** Changed in: ibus (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/186 Title: ibus-daemon 170% CPU when using Flatpak Endeavour

[Touch-packages] [Bug 2002869] Re: "ctrl:swapcaps" doesn't swap shift+capslock and shift+ctrl

Thanks for your report! That kind of issue is really upstream in nature, and nothing we would like to change in Ubuntu only. So it would be great if you could submit an upstream issue too: https://gitlab.freedesktop.org/xkeyboard-config/xkeyboard- config/-/issues If you do, please add a comment

[Touch-packages] [Bug 2000551] Re: [System Fonts] Replace default sinhala font from LKLUG to Noto

@Aurora: fonts-noto-core needs to be installed also. Please see the test plan. They should open Language Support. If a user already has the Sinhala language installed, they will be prompted to install fonts-noto-core. Otherwise they should install Sinhala, in which case fonts-noto-core will be one

[Touch-packages] [Bug 2000551] Re: [System Fonts] Replace default sinhala font from LKLUG to Noto

On 2023-01-17 08:48, Aurora wrote: >> Or they can simply do: sudo apt install fonts-noto-core > > but flatpak users said that flatpak apps still use LKLUG, how to > solve that problem? I don't know anything about Flatpak, sorry. Can't tell to which extent Flatpak honors fontconfig. Maybe try Ask

[Touch-packages] [Bug 2003331] [NEW] Can't log in to lunar x11 session

Public bug reported: On a freshly installed and updated lunar in VirtualBox it doesn't let me log in to Ubuntu on Xorg. I'm just bumped back to the login screen. journalctl extract attached. On my regular (updated) lunar install, logging in to Ubuntu on Xorg works fine. But that's anything but a

[Touch-packages] [Bug 2003331] Re: Can't log in to lunar x11 session

Actually I see the issue with both. The journalctl extract is from an attempt with the current image (with Ubiquity). Yesterday I installed via yesterday's pending image. Same problem. Not magically fixed. :( ** Changed in: ubuntu-meta (Ubuntu) Status: Incomplete => New -- You received

[Touch-packages] [Bug 1958084] Re: Please apply the upstream commit to drop Bitstream Vera fonts

Fixed also in Ubuntu. ** Changed in: fontconfig (Ubuntu) Status: New => Fix Released -- 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/1958084 Title: Please apply

[Touch-packages] [Bug 2004200] [NEW] dpkg-maintscript-helper refuses to remove file

Public bug reported: At the update of fontconfig to version 2.14.1-3ubuntu1, an Ubuntu patch, which previously added a config file under /etc, was dropped. Hence I tried to have the file removed via this line in debian/fontconfig- config.maintscript: rm_conffile /etc/fonts/conf.avail/10-antialias

[Touch-packages] [Bug 2003331] Re: Can't log in to lunar x11 session

On 2023-02-02 20:25, Brian Murray wrote: > Could this be a duplicate of bug 2004092? I don't think so. The buttons showed up as expected, and I installed successfully. My user ID is 1000. The problem is that I can't log in to "Ubuntu on Xorg". Just updated the packages and the problem is still pr

[Touch-packages] [Bug 2003269] Re: Please update to openjdk 8u362-ga

** Tags added: update-excuse ** Also affects: fontconfig (Ubuntu) Importance: Undecided Status: New -- 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/2003269 Titl

[Touch-packages] [Bug 2003269] Re: Please update to openjdk 8u362-ga

The problem seems to be resolved now. https://lists.ubuntu.com/archives/ubuntu-devel/2023-February/042453.html ** Tags removed: update-excuse ** No longer affects: fontconfig (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subsc

[Touch-packages] [Bug 2005124] Re: package fontconfig-config 2.13.1-4.4ubuntu1 failed to install/upgrade: trying to overwrite '/etc/fonts/conf.d/10-sub-pixel-rgb.conf', which is also in package kubunt

nged in: kubuntu-settings (Ubuntu) Importance: Undecided => High ** Changed in: kubuntu-settings (Ubuntu) Status: Confirmed => Fix Committed ** Changed in: kubuntu-settings (Ubuntu) Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj) ** Changed in: fontconfig

[Touch-packages] [Bug 2005124] Re: package fontconfig-config 2.13.1-4.4ubuntu1 failed to install/upgrade: trying to overwrite '/etc/fonts/conf.d/10-sub-pixel-rgb.conf', which is also in package kubunt

It struck me that this issue motivates a Breaks/Replaces in fontconfig- config to ensure smooth upgrades. I uploaded that change. ** Changed in: fontconfig (Ubuntu) Status: Invalid => Fix Committed ** Changed in: fontconfig (Ubuntu) Assignee: (unassigned) => Gunnar Hjalm

[Touch-packages] [Bug 1887252] Re: config-error-dialog.sh should pass --no-markup

@Hongyi Zhao: As you wrote in the duplicate bug, my simplistic code in comment #2, which only escapes the '<' character, would not be sufficient. At the same time the issue I mentioned, about --no-markup making \n being displayed literally instead of interpreted as a newline, still stands. Probabl

[Touch-packages] [Bug 1887252] Re: config-error-dialog.sh should pass --no-markup

That looks like a better solution indeed, and I think I have got enough of evidence that we should go for Sebastian's suggestion. ( Why didn't you mention that upstream discussion in your bug? ;) ) Thanks for your persistence! I'll make that change soon. ** Changed in: gdm3 (Ubuntu) Statu

[Touch-packages] [Bug 1887252] Re: config-error-dialog.sh should pass --no-markup

Change for gdm3 was pushed to git repo: https://salsa.debian.org/gnome-team/gdm/-/commit/03d610a4 lightdm has been uploaded with the change. ** Changed in: gdm3 (Ubuntu) Status: In Progress => Fix Committed ** Changed in: lightdm (Ubuntu) Status: In Progress => Fix Committed --

[Touch-packages] [Bug 2007124] [NEW] Move available config files from /etc to /usr

Public bug reported: At the upgrade to fontconfig 2.10 a decade ago, the directory for storing available config files was changed from /etc/fonts/conf.avail to /usr/share/fontconfig/conf.avail. It was done upstream as well as in Debian, but Ubuntu delayed the transition for some reason. I think we

[Touch-packages] [Bug 2000551] Re: [System Fonts] Replace default sinhala font from LKLUG to Noto

> so this is not the expected solution :( It's the solution we are able to offer ATM. Please understand: * It's not an option in the short run to install fonts-noto-core for all Ubuntu users. At the moment that package gets installed as a language support component for certain languages, includi

[Touch-packages] [Bug 2003331] Re: Can't log in to lunar x11 session

On 2023-02-03 04:32, Gunnar Hjalmarsson wrote: > Just updated the packages and the problem is still present. Same observation today. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. ht

[Touch-packages] [Bug 2003331] Re: Can't log in to lunar x11 session

The above observations are with virtualbox 6.1.38-dfsg-3~ubuntu1.22.04.1 on jammy. ** Also affects: virtualbox (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta i

[Touch-packages] [Bug 2007124] Re: Move available config files from /etc to /usr

This was uploaded to lunar after a brief IRC conversation: https://irclogs.ubuntu.com/2023/02/23/%23ubuntu-desktop.html#t14:18 ** Changed in: fontconfig (Ubuntu) Status: New => Fix Committed ** Changed in: fontconfig (Ubuntu) Assignee: (unassigned) => Gunnar Hjalmarsson (gu

[Touch-packages] [Bug 2003331] Re: Can't log in to lunar x11 session

On 2023-02-23 15:16, Gunnar Hjalmarsson wrote: > The above observations are with virtualbox > 6.1.38-dfsg-3~ubuntu1.22.04.1 on jammy. But today I saw the same with virtualbox 7.0.6-dfsg-1 on lunar. -- You received this bug notification because you are a member of Ubuntu Touch seeded pa

[Touch-packages] [Bug 2008592] Re: editing python code with idle

** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/2008592/+attachment/5649994/+files/CoreDump.gz ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is

[Touch-packages] [Bug 2003331] Re: Can't log in to lunar x11 session

Just made a normal installation which succeeded. The issue reported here seems to be unrelated to ubuntu-meta. ** Changed in: ubuntu-meta (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to

[Touch-packages] [Bug 2008279] Re: xsettings ibus commit broke text input for Firefox & Chromium snaps

Hmm.. Suddenly I could no longer type in the address bar of the Firefox snap. But I think the culprit is glib2.0 2.75.3-3, which I installed from -proposed yesterday in order to test build g-c-c from ubuntu/master. After having downgraded glib2.0 to 2.74.5-1 the issue is no longer present. ** Also

[Touch-packages] [Bug 2008279] Re: glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps

** Summary changed: - xsettings ibus commit broke text input for Firefox & Chromium snaps + glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps ** No longer affects: gnome-settings-daemon (Ubuntu) ** Changed in: glib2.0 (Ubuntu) Importance: Undecided => High ** Tags added: rls-ll

[Touch-packages] [Bug 2008279] Re: glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps

With glib2.0 2.75.3-3 installed and when starting the Firefox snap from terminal I see these warning messages: [Parent 3792, Main Thread] WARNING: Unable to connect to ibus: Could not connect: Permission denied: 'glib warning', file /build/firefox/parts/firefox/build/toolkit/xre/nsSigHandlers.cpp:

[Touch-packages] [Bug 2008279] Re: glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps

Want to mention that the issue is not present with glib2.0 2.75.3-3 if fcitx5 is used instead of ibus. :/ ** Also affects: ibus (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed

[Touch-packages] [Bug 2008279] Re: glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps

ibus in lunar-release was built against glib2.0 2.74.5-1. I tried a no- change rebuild of ibus against glib2.0 2.75.3-3, but it didn't help. (Such a rebuild may still be motivated later.) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is sub

[Touch-packages] [Bug 2008279] Re: glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps

@Jeremy: I figured out the nature of the issue you originally reported in this bug. With this combo: $ dpkg-query -W libglib2.0-0 gnome-settings-daemon gnome-settings-daemon 44~beta-1ubuntu1 libglib2.0-0:amd64 2.75.3-3 and as long as no IBus IM has been added to the list of input sources,

[Touch-packages] [Bug 2009077] Re: ibus-x11 assert failure: double free or corruption (fasttop)

** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/2009077/+attachment/5651136/+files/CoreDump.gz ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is

[Touch-packages] [Bug 2008279] Re: glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps on Xorg

** Description changed: Test Case - From Ubuntu 23.04, install glib >= 2.75.3-3 + + Test 1: Log out Click your name on the login screen. Click the gear button to choose Ubuntu on Xorg Enter your password to finish logging in. Open Firefox (or Chromium) Try to enter text

[Touch-packages] [Bug 2008279] Re: glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps if IBus is turned on

** Also affects: snapd (Ubuntu) Importance: Undecided Status: New ** Changed in: snapd (Ubuntu) Importance: Undecided => High ** Changed in: snapd (Ubuntu) Status: New => In Progress ** Changed in: snapd (Ubuntu) Assignee: (unassigned) => James Henstridge (jamesh) -- Y

[Touch-packages] [Bug 2008279] Re: glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps if IBus is turned on

@Michael: Any chance you can make a new bug fix release of snapd soon? This issue blocks quite a few packages from migrating to lunar-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.launch

[Touch-packages] [Bug 2009700] Re: [lunar] missing key events with ibus 1.5.28

Importance: Undecided => High ** Changed in: ibus (Ubuntu) Status: New => In Progress ** Changed in: ibus (Ubuntu) Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is su

[Touch-packages] [Bug 2008279] Re: glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps if IBus is turned on

Great, Seb. Guess we'd better remove the block-proposed tag then. ** Tags removed: block-proposed -- 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/2008279 Title: glib2.0 2.75.

[Touch-packages] [Bug 2008279] Re: glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps if IBus is turned on

Removing block-proposed again after a short IRC talk with Sebastien. We don't want to prevent snapd from migrating. ** Tags removed: block-proposed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.

[Touch-packages] [Bug 2004241] Re: Update to glib >= 2.75.1

While the issue in bug #2008279 will be fixed via a snapd change, it was caused by a glib change. We don't want glib2.0 >=2.75 to migrate before snapd 2.58.3+23.04ubuntu1 has made it to lunar-release and has been confirmed to fix the issue. ** Tags added: block-proposed -- You received this bug

[Touch-packages] [Bug 2008279] Re: glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps if IBus is turned on

Added the block-proposed tag to bug #2004241 instead. -- 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/2008279 Title: glib2.0 2.75.3-3 breaks text input for Firefox & Chromium

[Touch-packages] [Bug 2007785] Re: Livepatch tab missing PT(-BR) translation after language pack 1:22.04+20230209 update

That one beats me. Adding a software-properties bug task, so the maintainer can determine the cause of that lack of translation. (I don't find the string in the POT file.) ** Also affects: software-properties (Ubuntu) Importance: Undecided Status: New -- You received this bug notificat

[Touch-packages] [Bug 2007785] Re: Livepatch tab missing PT(-BR) translation after language pack 1:22.04+20230209 update

Correction: So you are now talking about update-manager... That string was changed a bit, and the changed string has not yet been translated to Brazilian Portuguese. It's as simple as that. https://translations.launchpad.net/ubuntu/lunar/+source/update- manager/+pots/update-manager/pt_BR?search=U

[Touch-packages] [Bug 2004241] Re: Update to glib >= 2.75.1

@Daniel: It's already in -proposed. And there are more packages which depend on glib >=2.75. -- 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/2004241 Title: Update to glib >

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

** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/2011656/+attachment/5654564/+files/CoreDump.gz ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is

[Touch-packages] [Bug 2012146] Re: very high cpu usage, system unresponsive

Thanks for your report! I see that you installed your system last year. Can you possibly tell if it's a regression from ibus 1.5.28-1, i.e. did it work smoothly with that version and the issue started with ibus 1.5.28-2? I'm asking because 1.5.28-2 includes two patches which are not yet in the up

[Touch-packages] [Bug 2012146] Re: very high cpu usage, system unresponsive

Ok.. But when exactly did you do that? If it was very recently, you may have upgraded ibus from 1.5.27-2 directly to 1.5.28-2. -- 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/201

[Touch-packages] [Bug 2012146] Re: very high cpu usage, system unresponsive

Thanks for clarifying. It means that we can't tell whether the issue is related to the specific changes in ibus 1.5.28-2, or if it is a general ibus 1.5.28 problem (or an ardour 7.3 problem...). In any case my plea to also report it to ibus upstream still stands. -- You received this bug notific

[Touch-packages] [Bug 2012146] Re: very high cpu usage, system unresponsive

@enorrmann: The latter is valuable info. I submitted an ardour Debian bug, which you should have received a copy of. Please feel free to add relevant info to that bug, if you think that I missed something. ** Also affects: ardour (Ubuntu) Importance: Undecided Status: New ** Bug watch a

[Touch-packages] [Bug 2012146] Re: very high cpu usage, system unresponsive

And thanks for reporting it to ibus upstream too. :) ** Also affects: ibus via https://github.com/ibus/ibus/issues/2492 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

[Touch-packages] [Bug 2012552] Re: /usr/libexec/accounts-daemon:11:g_dbus_method_invocation_return_value_internal:check_auth_cb:g_simple_async_result_complete:check_authorization_cb:g_task_return_now

The latter comment reminds me of bug #2011313, where the underlying issue was a failure (for some reason) to fetch user data. One side effect in that case was that it resulted in a language variable having a NULL value, and then it failed when trying to convert it to a valid locale name. Anyway, t

[Touch-packages] [Bug 2012552] Re: /usr/libexec/accounts-daemon:11:g_dbus_method_invocation_return_value_internal:check_auth_cb:g_simple_async_result_complete:check_authorization_cb:g_task_return_now

Status: New ** Changed in: gnome-control-center (Ubuntu) Status: New => Fix Committed ** Changed in: gnome-control-center (Ubuntu) Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj) -- You received this bug notification because you are a member of Ubuntu Touch seeded pa

[Touch-packages] [Bug 2012552] Re: /usr/libexec/accounts-daemon:11:g_dbus_method_invocation_return_value_internal:check_auth_cb:g_simple_async_result_complete:check_authorization_cb:g_task_return_now

Now I have tested too. :/ Switching language does not result in an attempt to reset region, and seems to work as expected. I can no longer reproduce any errors or warnings when starting g-c-c from terminal. ** Changed in: accountsservice (Ubuntu) Status: Incomplete => Invalid -- You recei

[Touch-packages] [Bug 2012788] Re: Entering Unicode characters with code points broken

Yes, Heinrich, on the surface this seems to be an ibus issue. But I think the root cause lies in some package which ibus is built with. If I downgrade to the binaries built by ibus 1.5.28-1 on February 23, using code points works fine. In 1.5.28-2 two upstream commits were added as patches, but if

[Touch-packages] [Bug 2012788] Re: Entering Unicode characters with code points broken

If I install ibus 1.5.28-2 from experimental on Debian, there is no code point issue. While the source is identical with 1.5.28-2 on Ubuntu, the binaries on Debian were built with older versions of some libraries. I'm not sure that the problem lies in glib. It's simply my intuition. ;) ** Changed

[Touch-packages] [Bug 2012788] Re: Entering Unicode characters with code points broken

** Bug watch added: github.com/ibus/ibus/issues #2496 https://github.com/ibus/ibus/issues/2496 ** Also affects: ibus via https://github.com/ibus/ibus/issues/2496 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch see

[Touch-packages] [Bug 2034986] Re: some text became unreadable during a distribution upgrade

I just ran an errand, and thought about that font workaround. The MATE issue makes me doubt about running the code for all the flavors. We know that the root cause is changes to the Ubuntu font. That font is explicitly used for desktop in standard Ubuntu and MATE. But is it used for desktop by any

[Touch-packages] [Bug 2034986] Re: some text became unreadable during a distribution upgrade

@Ethan: MATE is about to be fixed. Once ubuntu-release-upgrader 1:23.10.10 has made it to mantic-release, you shouldn't be able to reproduce that. Let us know otherwise. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-m

[Touch-packages] [Bug 2034986] Re: some text became unreadable during a distribution upgrade

Hmm.. The XDG_CURRENT_DESKTOP variable keeps being present when you use sudo, which is the reason why we successfully tested the MATE specific code. Apparently the pkexec environment differs. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is

[Touch-packages] [Bug 2034986] Re: some text became unreadable during a distribution upgrade

On 2023-10-12 18:39, Brian Murray wrote: > however the title bar was corrupted but that's fine. Yeah, that's expected. I didn't think it was motivated to play with multiple dconf keys only for MATE. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, w

[Touch-packages] [Bug 2034986] Re: some text became unreadable during a distribution upgrade

I'm investigating the flavors in this respect more systematically, and just found that a 23.04 -> 23.10 upgrade of Ubuntu Cinnamon is still hit by this issue (they use the schema org.cinnamon.desktop.interface ...). So adding the Cinnamon project for now. I will soon come up with a proposal for ma

[Touch-packages] [Bug 2034986] Re: some text became unreadable during a distribution upgrade

On 2023-10-13 22:10, Jeremy Bícha wrote: > Gunnar, I tested these desktop flavors successfully (23.04 to 23.10): > - Ubuntu Desktop > - Ubuntu Budgie > - Ubuntu Kylin > - Kubuntu > - Lubuntu > - Xubuntu Thanks for reporting that. I have not found otherwise. But in most of those cases (not Ubuntu

[Touch-packages] [Bug 2034986] Re: some text became unreadable during a distribution upgrade

Since I propose yet another SRU, I created bug #2039356. This bug report is quite noisy already... My examination of the flavors with respect to this issue focused on two questions: 1. Does the u-r-u model effectively prevent 'the unreadable text issue' when the desktop font in use — whether defa

[Touch-packages] [Bug 2034986] Re: some text became unreadable during a distribution upgrade

@Michael: Then you hadn't installed version version 1:23.04.7 of ubuntu- release-upgrader first, right? Please compare comment #44. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.

[Touch-packages] [Bug 2034986] Re: some text became unreadable during a distribution upgrade

@Nathan: I think you actually describe the underlying reason why this is an issue. For running processes which use a particular font, you'll see the characters become corrupted if you replace the related font file, and it will fix itself when you restart the process. -- You received this bug noti

[Touch-packages] [Bug 2034986] Re: some text became unreadable during a distribution upgrade

I made a verification attempt for mantic of the 1:23.10.12 changes. https://bugs.launchpad.net/ubuntu/+source/ubuntu-release- upgrader/+bug/2039356/comments/3 While those changes are included in 1:23.10.13, the specific change in 1:23.10.13 (letting do-release-upgrade set the XDG_CURRENT_DESKTOP

[Touch-packages] [Bug 2034986] Re: some text became unreadable during a distribution upgrade

@Bloodyiron: Does it help to reboot? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2034986 Title: some text became unreadable during a distribution upgrade Status in

[Touch-packages] [Bug 2034986] Re: some text became unreadable during a distribution upgrade

Ok. This bug is focused on the UI for the upgrader itself. I would recommend you to ask a question at Ask Ubuntu. That way you'll hopefully get help to determine if it is a problem with your configuration or some kind of bug. -- You received this bug notification because you are a member of Ubun

[Touch-packages] [Bug 2043234] Re: Symlink for resolv.conf is wrong on fresh install

** Package changed: ubuntu-docs (Ubuntu) => systemd (Ubuntu) -- 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/2043234 Title: Symlink for resolv.conf is wrong on fresh instal

[Touch-packages] [Bug 412195] Re: ttf-tahoma-replacement makes some web-sites look ugly

@Jaromir, @Bloodyiron: This bug was closed more than a decade ago. Please don't waste time with adding new comments here. If you see issues (beyond personal preferences) with fonts-wine, please submit a new bug: ubuntu-bug wine -- You received this bug notification because you are a member of U

[Touch-packages] [Bug 412195] Re: ttf-tahoma-replacement makes some web-sites look ugly

On 2023-11-13 18:44, Marius Gedminas wrote: > Debian reverted the change to isolate these low quality fonts from the > rest of the system in > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883973, and now this > bug is back in Ubuntu 23.10. Good catch! That Debian bug was filed in 2017, and "t

[Touch-packages] [Bug 2043442] Re: /usr/libexec/ibus-ui-gtk3 --enable-wayland-im system freezes

Thanks for your report. I see Plasma and Wayland, which reminds me of and . * Have you applied the IBus Wayland virtual keyboard? * If you have, can you please run this command: im-config -n none and reboot, and then let us

[Touch-packages] [Bug 2034986] Re: some text became unreadable during a distribution upgrade

On 2023-11-24 21:06, BloodyIron wrote: > For me removing "fonts-wine" "solved" the problem, Well, it solved *your* problem, which we now know is of another nature () than the issue with the ubuntu- release-upgrader UI dealt with in this bug report. ** Bug watch add

[Touch-packages] [Bug 2045245] Re: ubuntu22.04 ibus Chinese pinying input not response

Thanks for your report. It's hard to comment on without more info. Possibly there is a need to clean the cache in ~/.cache/ibus/libpinyin . ** Changed in: ibus (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded package

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

On 2020-01-16 13:03, Jarno Suni wrote: > What is so difficult in not asking password when guest session > is concerned? Maybe low priority since guest session is disabled by default. https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1775088/comments/2 > Does one need to switch from guest se

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

@aslam: This is a 10 years old bug report, and it was closed long ago. I'm not sure that you found a bug. I'd recommend you to start with asking for help at e.g. in order to find out if there is something you have misunderstood or if there really is a bug, and if it is, to

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

I verified the test plan * on 20.04 using lightdm 1.30.0-0ubuntu4~20.04.1 from focal-proposed * on 20.10 using lightdm 1.30.0-0ubuntu4~20.10.1 from groovy-proposed ** Tags removed: verification-needed verification-needed-focal verification-needed-groovy ** Tags added: verification-done verifica

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

Thanks for your report! Since you use lightdm 1.30.0-0ubuntu4~20.04.1 from focal-proposed, can you please downgrade to version 1.30.0-0ubuntu3.1 and let us know if it makes a difference. ** Changed in: lightdm (Ubuntu) Status: New => Incomplete -- You received this bug notification becau

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

On 2021-04-30 23:59, Robert Dinse wrote: > I was under the impression that the purpose of proposed was to test > and get feedback and fix such things before it entered mainstream. It is, but such testing happens normally via dedicated bug reports. As regards the current lightdm version in -propose

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

OTOH... If you haven't enabled the guest session feature, the difference between the lightdm versions in focal-release and focal-proposed can't possibly cause the segfault. Did you possibly install everything from focal-proposed? In that case you may be actually 'testing' this upload: https://lau

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

Right, bugs are filed against source packages. Changing. ** Package changed: lightdm (Ubuntu) => glibc (Ubuntu) ** Changed in: glibc (Ubuntu) Status: Incomplete => New ** Summary changed: - lightdm segfaults + libc-2.31.so segfaults -- You received this bug notification because you are

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

Compose followed by i followed by j gives me ij on Ubuntu 21.04. So somehow (gtk update?) this bug seems to have been fixed. Closing. ** Package changed: xkeyboard-config (Ubuntu) => gtk+3.0 (Ubuntu) ** Changed in: gtk+3.0 (Ubuntu) Status: Triaged => Fix Released -- You received this bug

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

Assuming that this may require apparmor changes, I added an apparmor (Ubuntu) bug task. ** Also affects: apparmor (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor i

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

It struck me that Lubuntu, which ships Fcitx by default, has a special interest in this change, so added a Lubuntu bug task. ** Also affects: lubuntu-default-settings Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded

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

I submitted a merge proposal with suggested changes to language-selector (pkg_depends). Please review and give feedback. ** Changed in: language-selector (Ubuntu) Status: New => In Progress ** Changed in: language-selector (Ubuntu) Assignee: (unassigned) => Gunnar Hjalm

  1   2   3   4   5   6   7   8   9   10   >