[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

[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

[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

[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

[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

[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

[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

[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

[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

@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

[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.

[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

[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

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

[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,

[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

@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

[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

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

** Changed in: ubuntu-release-upgrader (Ubuntu Mantic) Status: Triaged => In Progress -- 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

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

Thanks Chris! Possibly no other flavor is affected by this issue, at least not in this cycle. -- 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

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

I submitted a MP to make the fix apply to MATE. It's not without issues, though (see the linked MP), and I think we need involvement from the MATE developers. ** Merge proposal linked: https://code.launchpad.net/~gunnarhj/ubuntu-release-upgrader/+git/ubuntu-release-upgrader/+merge/453086 --

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

To the extent I participated in the resolution of this bug, I had standard Ubuntu in mind, where the default desktop font can be accessed like this: gsettings get org.gnome.desktop.interface font-name And that's the key whose value is temporarily changed when upgrading to 23.10. But on MATE that

[Touch-packages] [Bug 2023322] Re: Unable to setup Google Online Accounts with Nvidia drivers

Added yelp as affected package too, since you hit this bug if you browse the desktop guide on X11/NVIDIA. ** Also affects: yelp (Ubuntu) Importance: Undecided Status: New ** Changed in: yelp (Ubuntu) Status: New => Triaged -- You received this bug notification because you are

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

On 2023-09-26 22:32, Gunnar Hjalmarsson wrote: > But one of the changes in mantic is that no font is safely present > (i.e. the default ones are "Recommends:" only). So later, when people > will upgrade from 23.10 to 24.04, just using "Sans" temporarily may > not

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

@Nick: That would be an improvement indeed. Guess you abandon /tmp then. ;) -- 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

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

On 2023-09-26 22:52, Steve Langasek wrote: > Trying to think in terms of robust general solutions to this problem, > what if update-manager were to notice when fonts were upgraded, and > when they are, shut down the GUI connection and reinitialize it? > This might require saving a bit of state

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

Hopefully an ubuntu-release-upgrader workaround will be in place soon. But in a sense this is an ubuntu-meta matter as well. The code in my merge proposal sets the "Sans" font temporarily, which in lunar means that either DejaVu Sans or Noto Sans will be used in the UI during the upgrade (unless

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

@Daniel: Maybe I answered a bit hasty. I see this issue over and over again without any Nvidia driver. But I do have a Nvidia card, if that may be related. Not sure about the root cause of this bug. We know that it happens with the Ubuntu font and that that font was changed in the mantic cycle.

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

** Changed in: ubuntu-release-upgrader (Ubuntu Mantic) Status: Confirmed => In Progress ** Changed in: ubuntu-release-upgrader (Ubuntu Mantic) Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj) -- You received this bug notification because you are a member of Ubuntu

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

On 2023-09-25 03:15, Daniel van Vugt wrote: > is it specific to Nvidia desktops like bug 1876632? No. -- 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:

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

@Steve: I made such a change to the MR. -- 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

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

** Merge proposal linked: https://code.launchpad.net/~gunnarhj/ubuntu-release-upgrader/+git/ubuntu-release-upgrader/+merge/451815 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.

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

The attached script is an attempt to express my idea in python code. I don't know where exactly I'd put those commands, though, so that's why I abstain from a merge request. ** Attachment added: "proposed_commands.py"

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

Without my workaround, I didn't even get that far, but it hanged before the "Cleaning up" phase. I could reboot manually, though. With the workaround, the upgrade completed including "Cleaning up". -- You received this bug notification because you are a member of Ubuntu Touch seeded packages,

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

Gunnar Hjalmarsson wrote: > Maybe it would be sufficient to drop the Ubuntu font as the first choice and > simply let fontconfig deal with it for everyone. I tested that approach. On an updated lunar I run this command: gsettings set org.gnome.desktop.interface font-name 'Sans 11' before

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

> What about this idea for a workaround: have the upgrader temporarily switch the UI font to a font that hasn't been changed since Jammy? That sounds as a reasonable idea. Maybe it would be sufficient to drop the Ubuntu font as the first choice and simply let fontconfig deal with it for everyone.

[Touch-packages] [Bug 1966552] Re: IBus input method candidate box cannot follow the cursor

Marking this as invalid for ibus and ibus-libpinyin. ibus upstream provided an explanation and confirmed that the workaround makes sense. ** Changed in: ibus (Ubuntu) Status: New => Invalid ** Changed in: ibus-libpinyin (Ubuntu) Status: New => Invalid -- You received this bug

[Touch-packages] [Bug 2033377] Re: New whitespace between digits and colon in time at top of desktop screen

> 1. Patch to revert to a colon in the default US English translation. > > 2. Propose to upstream to not use RATIO in future because fonts don't > often implement the Mathematical Operators block. Those were my reflexive thoughts too, especially item 2. But then I saw that RATIO has been

[Touch-packages] [Bug 2033377] Re: New whitespace between digits and colon in time at top of desktop screen

For the record: The different results depending on locale is a "translation" matter. While the default time separator is \u2236, it has been "translated" for e.g. en_GB in Ubuntu into \u003A: https://translations.launchpad.net/ubuntu/mantic/+source/gnome- desktop/+pots/gnome-desktop-3.0/en_GB/24

[Touch-packages] [Bug 2033377] Re: New whitespace between digits and colon in time at top of desktop screen

in: language-selector (Ubuntu) Importance: Undecided => Medium ** Changed in: language-selector (Ubuntu) Status: New => Fix Committed ** Changed in: language-selector (Ubuntu) Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj) -- You received this bug notificatio

[Touch-packages] [Bug 2033129] Re: hplip is in universe and was dropped from Recommends

hplip is back in main and shipped on the ISO again. Closing this to reduce unnecessary noise. ** Changed in: ubuntu-meta (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to

[Touch-packages] [Bug 2024560] Re: Check if 0010-set-language needs to be update for the new languages property

@Sebastien: Is this bug ready to be closed again? -- 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/2024560 Title: Check if 0010-set-language needs to be update for

[Touch-packages] [Bug 1996652] Re: Nautilus search is slow and jumbles keyboard input on 22.10

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

[Touch-packages] [Bug 1996652] Re: Nautilus search is slow and jumbles keyboard input on 22.10

@Federico: The x11 issue you spotted has now been fixed through updated patches, and the PPA has been updated with the latest patch versions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu.

[Touch-packages] [Bug 1996652] Re: Nautilus search is slow and jumbles keyboard input on 22.10

Nah, it's fine to test on lunar. I do it on mantic since I don't have a lunar installation easily available. Previously, when I couldn't reproduce, I tested in a Wayland session. Now I have tried "Ubuntu on Xorg", and there I see bad things when using gnome-terminal or gedit, i.e. gtk3

[Touch-packages] [Bug 1996652] Re: Nautilus search is slow and jumbles keyboard input on 22.10

@Federico: Thanks for testing and reporting that observation! I can't reproduce it (on mantic), though. Dead keys work as expected for me, also with the keyboard layout you mentioned. Are you sure that the issue is related to the proposed ibus version? Does the issue go away if you downgrade to

[Touch-packages] [Bug 1996652] Re: Nautilus search is slow and jumbles keyboard input on 22.10

My first upload to the PPA proved to not be complete. Corrected now. (Wait for the builds to finish and the packages to be published before updating). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu.

[Touch-packages] [Bug 2017076] Re: default Chinese font in snap apps is ugly

On 2023-07-03 12:59, Gunnar Hjalmarsson wrote: > (But I notice another weird issue: In the FF Settings it shows Ubuntu > as the default serif font irrespective of locale. How come?) Pls disregard that. User error. -- You received this bug notification because you are a member of Ubuntu

[Touch-packages] [Bug 2017076] Re: default Chinese font in snap apps is ugly

On 2023-07-03 11:08, Sebastien Bacher wrote: > Could you use a new bug to discuss the japanese issue? Yes, Mitsuya plans to submit a new bug once he has checked mantic. (I have used this one in the meantime to share a couple of thoughts.) > It could help also to know if you are using the core20

[Touch-packages] [Bug 2017076] Re: default Chinese font in snap apps is ugly

I think the reason why fonts-droid-fallback is installed by default is this dependency chain: ubuntu-desktop -> ghostscript-x -> ghostscript -> libgs10 -> libgs10-common -> (recommends) fonts-droid-fallback A fragile workaround might be to somehow stop fonts-droid-fallback from being pulled

[Touch-packages] [Bug 2017076] Re: default Chinese font in snap apps is ugly

> I am concerned that it only affects the snap package, while > the non-snap package seems to select the correct glyphs. Yes, that's what it looks like. $ lsb_release -c No LSB modules are available. Codename: mantic $ dpkg-query -W fonts-droid-fallback fonts-droid-fallback

[Touch-packages] [Bug 2017076] Re: default Chinese font in snap apps is ugly

@Mitsuya Shibata: Well, yes it *affects* Japanese fonts too, but it makes no sense that *this change* would increase the risk of picking Chinese glyphs under a Japanese locale. OTOH, if I start Firefox with: env LC_CTYPE=ja_JP.UTF-8 firefox the default sans-serif font for me according to FF

[Touch-packages] [Bug 1996652] Re: Nautilus search is slow and jumbles keyboard input on 22.10

The IBus maintainer Takao Fujiwara has submitted a pull request which is intended to address this issue. I applied the pull request and uploaded IBus (for 23.04 and 23.10) to this PPA: https://launchpad.net/~gunnarhj/+archive/ubuntu/ibus Can users who are affected by the issue please install

[Touch-packages] [Bug 2024560] Re: Check if 0010-set-language needs to be update for the new languages property

It's probably because you still have that colon separated list in your keyfile in /var/lib/AccountsService/users after having played with version 23.13.9-1ubuntu1. * Go to Settings -> Region & Language (it will complain there too) * Change the language to French, which alters the applicable

[Touch-packages] [Bug 2024870] Re: accountsservice package

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

[Touch-packages] [Bug 2024560] Re: Check if 0010-set-language needs to be update for the new languages property

uage-not- xpg.patch. Not sure if the upstream project is at all useful for us. In any case I kind of fear the it will cause more issues... ** Changed in: accountsservice (Ubuntu) Status: New => Fix Committed ** Changed in: accountsservice (Ubuntu) Assignee: (unassigned) => Gunnar H

[Touch-packages] [Bug 2024560] Re: Check if 0010-set-language needs to be update for the new languages property

@Sebastien: The new "Languages" property is described as an optional one, but it still looks like language changes are now stored in the "Languages" property instead of "Language". The backend patches in accountsservice, g-c-c, etc. (which I'm guilty of) 1. serve the purpose of keeping

[Touch-packages] [Bug 2024560] Re: Check if 0010-set-language needs to be update for the new languages property

I'll comment on this in a bit. Busy with another thing ATM. -- 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/2024560 Title: Check if 0010-set-language needs to be

[Touch-packages] [Bug 2017076] Re: default Chinese font in snap apps is ugly

@Sebastien: Sorry for confusing the installer with the ISO (which is used for installing...). My point was that at first login after a Chinese install, you have the versions of firefox and core22 from April, and thus see the issue if you open FF before having refreshed the snaps. One concern of

[Touch-packages] [Bug 2017076] Re: default Chinese font in snap apps is ugly

The installer is mentioned in the first sentence in the bug description. :) I was thinking that the installer still ships the old snap without the fix. Then, if the user opens FF before refreshing the snaps, they would still have the wrong default in FF. Maybe I'm wrong. I haven't done any

[Touch-packages] [Bug 2017076] Re: default Chinese font in snap apps is ugly

This seems to be fixed in Firefox latest/stable/ubuntu-23.04 114.0.1. @Sebastien: But that doesn't fix the 23.04 installer, does it? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu.

[Touch-packages] [Bug 2017573] Re: Font hinting broken on 23.04

I made some changes to this bug report, such as replacing fontconfig with plasma-desktop as the affected package. While I'm not sure about that either, it's a way to call the Kubuntu developers' attention to the issue. ** Package changed: fontconfig (Ubuntu) => plasma-desktop (Ubuntu) ** Changed

[Touch-packages] [Bug 2017573] Re: Font hinting broken on 23.04

Thanks again. You mentioned "under Wayland". Does that mean that the issue is not present if you log in to a Plasma (X11) session instead of a Plasma (Wayland) one? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig

[Touch-packages] [Bug 2017573] Re: Font hinting broken on 23.04

On 2023-04-24 23:00, mrvanes wrote: > It's written to ~/.config/fontconfig/fonts.conf For me it's not. Wonder why. > and it certainly is used. Right, it should be, because that file path is not deprecated. Thanks for clarifications. Then, if I understand it correctly, the problem is specific

[Touch-packages] [Bug 2017573] Re: Font hinting broken on 23.04

I had a look in a Kubuntu 23.04 install I have in a VM, and it looks like changes via the KDE UI for managing fonts alters the file ~/.fonts.conf. If that is the way you do it, can you please attach your ~/.fonts.conf file to this bug report. The ~/.fonts-conf file has been considered deprecated

[Touch-packages] [Bug 2017573] Re: Font hinting broken on 23.04

Ok, thanks. You said "I use full hinting". Are you referring to some custom font configuration? I'm asking because I'm not aware of any general Ubuntu changes with respect to hinting. And the file names of the Ubuntu and Ubuntu Mono font files were changed. -- You received this bug notification

[Touch-packages] [Bug 2017573] Re: Font hinting broken on 23.04

Thanks for your report! I recall a couple of fonts related changes and issues. Since you mention the Ubuntu and Ubuntu Mono fonts, they were indeed upgraded. But to start with it would be good if you could let us know the exact context where you see that hinting has changed. Is it in connection

[Touch-packages] [Bug 2003579] Re: Simulating Secondary mouse key fails

** Package changed: xkeyboard-config (Ubuntu) => gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/2003579 Title: Simulating Secondary mouse

[Touch-packages] [Bug 2003581] Re: Mouse keys fails to work after a restart

Thanks for additional info. Well, it was a guess.. Replacing xkeyboard-config with gnome-shell, since I think this is a gnome-shell feature. ** No longer affects: im-config (Ubuntu) ** Package changed: xkeyboard-config (Ubuntu) => gnome-shell (Ubuntu) -- You received this bug notification

[Touch-packages] [Bug 2003581] Re: Mouse keys fails to work after a restart

This comment is a guess, and I may be completely wrong, but I wonder if this happens in Ubuntu on Xorg only. If so, it may be related to the fact that ibus wasn't always automatically enabled at the start of the session. That issue was fixed in 22.04 via bug #2007379. So, @nix, it would be

[Touch-packages] [Bug 2017076] Re: default Chinese font in snap apps is ugly

** Changed in: fontconfig (Ubuntu) Importance: High => Undecided ** Changed in: fontconfig (Ubuntu) Status: New => Invalid ** Changed in: language-selector (Ubuntu) Status: New => Invalid ** Changed in: snappy Status: New => Confirmed -- You received this bug

[Touch-packages] [Bug 2017076] Re: default Chinese font in snap apps is ugly

On 2023-04-21 21:18, Sebastien Bacher wrote: > @Gunnar, that's because the only channel which has the core22 > firefox atm is stable/ubuntu-23.04 (which is specific to Lunar). So, then I just learned that if you are on lunar aka 23.04 and install firefox from the latest/stable channel, you get

[Touch-packages] [Bug 2017076] Re: default Chinese font in snap apps is ugly

This is confusing. If you install Ubuntu 23.04, you get FF from latest/stable/23.04 together with core22. Now I did a test where I removed FF, set the zh_CN.UTF-8 locale, and installed FF again. Whichever channel I pick (tried latest/stable, latest/beta and latest/edge) it pulls core20, and then

[Touch-packages] [Bug 2017076] Re: default Chinese font in snap apps is ugly

I had an IRC conversion with Sebastien Bacher and learned that things no longer work as I thought they did. Unlike what I thought, the snaps do no longer honor the font configuration of the host system, but live in their own world in this respect.

[Touch-packages] [Bug 2017076] Re: default Chinese font in snap apps is ugly

Adding the language-selector package, since many fontconfig files affecting Chinese rendering are provided by language-selector-common. ** Also affects: language-selector (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of

[Touch-packages] [Bug 2017076] Re: default Chinese font in snap apps is ugly

One thought is to ask why we still install the fonts-arphic-uming package when installing Chinese (Simplified as well as Traditional). Probably it is of historical reasons from the time before Noto existed. But let's consider that to be a matter of its own. Even if AR PL UMing is available, Noto

[Touch-packages] [Bug 2017076] Re: default Chinese font is ugly

@Shengjing Zhu: Can you confirm that it's only in snap applications you see UMing instead of Noto? Btw, is it limited to Snap Store, or is the FF snap affected as well? Also: Is Noto used as expected - when browsing web sites with Chinese contents - in the desktop itself, e.g. Settings **

[Touch-packages] [Bug 2015962] Re: indicator-messages-service crashed with SIGSEGV in g_type_check_instance() from g_signal_handlers_disconnect_matched() from act_user_manager_finalize() from g_object

Since im_accounts_service_dispose() is mentioned in the bug title, can this possibly have something to do with bug #2015610? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu.

[Touch-packages] [Bug 2016318] Re: free command: in Italian header is misaligned and wrongly translated

** Changed in: ubuntu-translations Importance: Undecided => Medium ** Changed in: ubuntu-translations Status: New => Confirmed ** Changed in: ubuntu-translations Assignee: (unassigned) => Traduttori Italiani del software di Ubuntu (ubuntu-l10n-it) -- You received this bug

[Touch-packages] [Bug 2015619] Re: IBus Pinyin automatically backspaces selection

Thanks for your report. ibus-pinyin is deprecated, and we recommend to use ibus-libpinyin (Intelligent Pinyin) instead. A problem with a specific IBus plugin is not an ibus bug per se, so closing. ** Changed in: ibus (Ubuntu) Status: New => Invalid -- You received this bug notification

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

This is under control now. An upstream ibus commit fixes it (see discussion at upstream issue). Fix uploaded to Debian experimental. ** Changed in: ibus (Ubuntu) Status: Confirmed => In Progress ** Changed in: ibus (Ubuntu) Assignee: (unassigned) => Gunnar Hjalmarsson (gu

[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

[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. ;) **

[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

[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

[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

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,

[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 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

[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

[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.

[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

[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 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 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-

[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

[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 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

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.

[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

  1   2   3   4   5   6   7   8   9   10   >