I could reproduce it.
The old installer makes use of the time zone location to "guess" the
desired locale, but that is apparently not the case with the flutter
based installer (at least not for the English variants).
There is a similar issue reported at GitHub:
And another question, btw: Did you use the new flutter based installer
or the "legacy" Ubiquity one?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/2043609
Title:
Well, that's a different issue. ;)
Which time zone location did you select during the install?
** Changed in: gnome-control-center (Ubuntu)
Status: Invalid => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Thanks for your report.
The "Language for menus and windows" setting shows which locale is used
to determine the display language. That's unrelated to the keyboard
layout for typing. You find the activated keyboard layouts in Settings
-> Keyboard.
Closing.
** Changed in: gnome-control-center
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
Ok, thanks. Then we can drop the rebuild idea, so closing this bug. I
also added yelp to bug #2023322.
** Changed in: yelp (Ubuntu)
Status: In Progress => Invalid
** Changed in: yelp (Ubuntu)
Assignee: Gunnar Hjalmarsson (gunnarhj) => (unassigned)
--
You received th
in: yelp (Ubuntu)
Status: New => In Progress
** Changed in: yelp (Ubuntu)
Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to yelp in Ubuntu.
https://bugs.launchp
Public bug reported:
Please see this email thread:
https://lists.ubuntu.com/archives/ubuntu-devel-
discuss/2023-September/019607.html
** Affects: yelp (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop
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
** Changed in: ubuntu-translations
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/389428
Title:
Stop importing RTL translations for
There are at least three bugs about that already. I don't think yet
another bug would make much of a difference. :)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
Is hplip installed? (For the case you are affected by bug #2033129.)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/2033059
Title:
Unable to add a printer
To manage
I unfixed it unintentionally as regards hplip, though, see bug #2033129.
** Changed in: ubuntu-meta (Ubuntu)
Status: Fix Released => In Progress
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
Upstream does object to the use of the patch. Please see this comment:
https://salsa.debian.org/gnome-team/gnome-
terminal/-/commit/c808edb8#note_420724
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu.
** No longer affects: glib2.0 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2031340
Title:
slic3r-prusa autopkgtest flaky
To manage notifications about this bug go to:
** Also affects: glib2.0 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2031340
Title:
slic3r-prusa autopkgtest flaky
To
Public bug reported:
In gnome-terminal 3.49.92-2ubuntu1 d/p/screen-Use-clean-env-when-
creating-new-tab.patch is disabled since the code is applied upstream in
3.49.92. However, upstream hesitates and has now reverted the code in
question. Please see this commit message:
Status: New
** Changed in: fonts-noto (Ubuntu)
Status: Confirmed => Invalid
** Changed in: language-selector (Ubuntu)
Status: New => In Progress
** Changed in: language-selector (Ubuntu)
Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)
--
You received
Thanks for letting us know that it has improved. :)
Closing.
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
Is this still a problem with the Ubuntu version you are using now?
> This is always on machine with on/off screen.
Can you explain what that means exactly. Does it only happen when you
return to your session after the screen has turned black or locked?
** Package changed: language-selector
Fixed upstream.
https://gitlab.gnome.org/GNOME/gnome-control-center/-/commit/701f7c6c
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/2025290
Title:
user-accounts:
** Changed in: gnome-control-center (Ubuntu)
Status: Expired => New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1987928
Title:
gnome-control-center closes
** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #2547
https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2547
** Also affects: gnome-control-center via
https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2547
Importance: Unknown
Status:
Possibly the updated accountsservice has something to do with it.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/2025290
Title:
user-accounts: GFileInfo created
Public bug reported:
If I open g-c-c from terminal on an updated mantic install and switch to
the Users panel, I see some warning messages (see attachment).
I don't know the significance of it, but it does not look right...
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package:
** Bug watch removed: gitlab.gnome.org/GNOME/gnome-shell/-/issues #6373
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6373
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #4467
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4467
** Changed in: gnome-shell
Status: Fix Released => Unknown
** Changed in: gnome-shell
Remote watch: gitlab.gnome.org/GNOME/gnome-shell/-/issues #6373 =>
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #6373
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6373
** Also affects: gnome-shell via
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6373
Importance: Unknown
Status: Unknown
--
You received this bug
** Changed in: gnome-software (Ubuntu)
Status: Fix Released => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1927149
Title:
Irrelevant translatable
I see the issue in Debian testing with mutter 43.4. So if the issue is
not present in 22.10, and if it is a mutter thing, it may have happened
somewhere between mutter 43.0 and 43.4.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
On 2023-05-19 18:45, Angel D. Segarra wrote:
> On 23.04 I still get a black window on first firefox start with the
> proposed mutter update.
Please note that installing the mutter binary package is not sufficient.
I suspect that you need to do:
sudo apt install libmutter-12-0/lunar-proposed
** Tags added: update-excuse-lunar
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1987976
Title:
firefox black window on wayland
To manage notifications about this bug go to:
As regards the failed autopkgtest on amd64, it's reasonably not related
to the proposed change, since also version 44.0-2ubuntu4 fails now
(unlike before the 23.04 release). My impression is that it's a problem
beyond the mutter package:
Running test case...
TAP version 13
# random seed:
Ah, thank you!
** Also affects: gnome-shell via
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6484
Importance: Unknown
Status: Unknown
** Bug watch added: Debian Bug tracker #1032388
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032388
** Also affects: gnome-shell
@Fedon: I think this is an issue which should be better reported to
GNOME upstream. But gnome-control-center is probably not the correct
project, since gnome-control-center just sets the dconf value in
question, while the problem is that that value is no longer honored in
x11 sessions. So it would
** Package changed: xkeyboard-config (Ubuntu) => gnome-shell (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/2003579
Title:
Simulating Secondary mouse key fails
To
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
resent (probably fresh install)
** Also affects: firefox (Ubuntu Lunar)
Importance: Undecided
Status: Confirmed
** Also affects: mutter (Ubuntu Lunar)
Importance: High
Assignee: Gunnar Hjalmarsson (gunnarhj)
Status: In Progress
** No longer affects: firefox (Ubuntu Lunar)
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
@Andreas: I just wrote this on #ubuntu-desktop:
https://irclogs.ubuntu.com/2023/04/20/%23ubuntu-desktop.html#t17:57
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1987976
Title:
Mentioned under "Known Issues" in the lunar release notes.
** Changed in: ubuntu-release-notes
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
I'm not sure, but I think the issue was present in kinetic. Hence not a
regression (probably).
I agree. Only this issue would not motivate a respin, and mentioning it
in the release note sounds reasonable.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
Marco Trevisan submitted an upstream mutter merge request with a fix of
this issue. I have applied it to the Ubuntu package through a PPA,
installed the resulting binaries, and accomplished some tests:
* I can no longer reproduce the issue with a black window when opening
Firefox in wayland, not
** Summary changed:
- firefox black window
+ firefox black window on wayland
** Changed in: mutter (Ubuntu)
Importance: Undecided => High
** Changed in: mutter (Ubuntu)
Status: Confirmed => In Progress
** Changed in: mutter (Ubuntu)
Assignee: (unassigned) => Gunnar Hj
*** This bug is a duplicate of bug 1987976 ***
https://bugs.launchpad.net/bugs/1987976
Let's use the original bug report instead.
** This bug has been marked a duplicate of bug 1987976
firefox black window
--
You received this bug notification because you are a member of Ubuntu
Desktop
the patch to the repo.
https://salsa.debian.org/gnome-team/mutter/-/commit/a400e60d
** Changed in: mutter (Ubuntu)
Status: New => In Progress
** Changed in: mutter (Ubuntu)
Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)
--
You received this bug notification becau
Public bug reported:
This may actually be a duplicate of bug #1987976, but I was advised to
file a new bug to get attention to this issue for the 23.04 release and
consider a possible workaround.
https://irclogs.ubuntu.com/2023/04/18/%23ubuntu-desktop.html#t17:42
In short: On a fresh 23.04
This fixes the issue for me:
$ cat /etc/xdg/autostart/firefox-snap-launch-xwayland.desktop
[Desktop Entry]
Name=Launch Xwayland on startup of wayland session
Comment=This allows to start the Firefox snap from the dock without a black
window
Type=Application
Exec=sh -c 'if [ "$XDG_SESSION_TYPE" =
)
Importance: Undecided
Status: New
** Changed in: pkgbinarymangler (Ubuntu)
Status: New => In Progress
** Changed in: pkgbinarymangler (Ubuntu)
Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)
** Merge proposal linked:
https://code.launchpad.net/~gunnarh
Public bug reported:
In my 23.04 development installation I installed the ubuntu-unity-
desktop package and then logged in to Unity. One observation is that the
input source indicator is not shown in the top bar, even if that feature
is enabled in Text Entry. Please see the attached screenshot.
** Changed in: devscripts (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/2012738
Title:
language support crashes
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
** 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
Desktop
I still have an issue. Not sure if it is related.
When clicking the Firefox icon in the dock, a completely black window
opens. Then I can close it and try again, and the second time it works
as expected. This repeats itself in each session.
--
You received this bug notification because you are
Now fixed in upstream's main, and patch in the Ubuntu branch:
https://salsa.debian.org/gnome-team/gnome-control-
center/-/commit/c25acdf4
** Changed in: gnome-control-center (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of
That's expected behavior. But you can change it to better fit your
situation:
* Open /usr/share/ibus/component/libpinyin.xml for editing.
* For the libpinyin engine, change this line:
default
to:
us
** Changed in: ibus-libpinyin (Ubuntu)
Status: New => Invalid
--
You received
Thanks for your report!
I noticed the same thing a while ago, and reported it upstream. The
upstream maintainer moved the English candidates after the sentence
candidates, and the new behavior should be present in Ubuntu 23.04.
** Changed in: ibus-libpinyin (Ubuntu)
Status: New => Fix
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. ;)
**
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
Happens in both x11 and wayland sessions.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/2012788
Title:
Entering Unicode characters with code points broken
To manage
Public bug reported:
On an updated lunar, following this instruction:
https://help.ubuntu.com/stable/ubuntu-help/tips-
specialchars.html#ctrlshiftu
no longer works. If I press for instance
Ctrl+Shift+U followed by 2014
I see u2014 (underlined) on the screen. But it's not replaced with the
gnome-control-center (Ubuntu)
Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)
** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #2418
https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2418
** Also affects: gnome-control-center via
Thanks for your report. I made a quick test, and couldn't reproduce the
behavior.
After having set "United Kingdom", can you please run the below terminal
commands and show us what they output in a comment here.
cat /etc/default/locale
locale -a
locale
** Changed in: gnome-control-center
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
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
Desktop Bugs,
Thanks for your follow-up, Mark!
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/2011313
Title:
gnome-control-center crashes after launch
To manage notifications
g-c-c 1:44~rc-1ubuntu1 has migrated to lunar-release.
** Changed in: gnome-control-center (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
*** This bug is a duplicate of bug 2011313 ***
https://bugs.launchpad.net/bugs/2011313
Thanks for your report. I suspect this is a duplicate of bug #2011313,
so marking it as such.
** Attachment removed: "CoreDump.gz"
On 2023-03-14 09:09, Tigran Aivazian wrote:
> So, you are saying that with this version I don't need the file
> /etc/profile.d/input-method-config.sh and can simply remove it?
No. I said that you can do that if you are on an Ubuntu version > 20.04.
Given the version you actually are on, instead I
Another theory is that you may have removed the im-config package
without purging it. In latter im-config versions we prevent such a
measure from leading to issues, but in the version uploaded due to this
bug there was no such protection.
--
You received this bug notification because you are a
@Tigran: It struck me that /etc/profile.d/input-method-config.sh is an
ancient file. Yes, it was introduced in 2017 due to this bug as a fix or
workaround, but it was dropped long ago. If you are on an Ubuntu version
> 20.04, you can safely just remove it.
So how could that happen? My guess is
On 2023-03-13 07:52, Mark Smith wrote:
> Do you know when 1:44~rc will be merged?
It has already been merged into the repo. Refreshing one or two patches
remains. I would guess it will be uploaded to lunar very soon.
--
You received this bug notification because you are a member of Ubuntu
Yeah.. That "Couldn't get locale for language: (null)" warning comes
from a patch which I wrote initially, and first I feared that the
segfault is related to that. But it's not. I committed a fix which will
get rid of the warning in this situation:
Sorry, I was on Ubuntu 22.04 when testing that command, but they seem to
have changed the schema name. On 23.04 this would have worked:
gsettings reset org.gnome.Settings last-panel
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Well, I don't claim that im-config is bug free forever after the fix of
this bug. New issues show up.
My point is that trying to revive an old and closed bug report is simply
not the right way to call the developers' attention to new issues.
My advice still stands: Use Ask Ubuntu to get help to
Btw, you can run this terminal command:
gsettings reset org.gnome.ControlCenter last-panel
and then you should be able to successfully open Settings. But avoid
"Users" for now.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Thanks for your report! I see the same thing when trying to switch to
the Users panel with gnome-control-center 1:44~alpha-0ubuntu1, but the
issue seems not to be present in the coming version 1:44~rc-1ubuntu1. So
stay tuned. :)
** Summary changed:
- Ubuntu-Settings crashes after launch
+
@Tigran: This bug was closed several years ago, and there is absolutely
no point in adding comments to it now.
If you have found a new bug, please report it separately. If you need
support, please visit some resource for that, e.g. https://askubuntu.com
. My guess is that the latter applies to
@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
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2004241
Title:
Update to glib >= 2.75.1
Added the block-proposed tag to bug #2004241 instead.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2008279
Title:
glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps
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
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
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
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
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2008279
Title:
glib2.0 2.75.3-3
@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
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
** 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)
--
** 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
** Tags added: lunar
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1956916
Title:
Using certain xkb-options, e.g. Alt+Shift, for switching input sources
not
@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,
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
Desktop Bugs, which is subscribed
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
Desktop Bugs, which is subscribed to
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
** 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:
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.
**
enter (Ubuntu)
Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/2008770
Title:
Sound: seg fault if env
Please disregard my "couldn't login" talk in the previous comment. I was
confused. Not the first time in history, and not the last.
So:
The version in my PPA (including that upstream g-s-d commit) works fine
for me on my regular lunar install. I can type in the address bar in
both the Firefox
I built g-s-d in a PPA with the revert reverted:
https://launchpad.net/~gunnarhj/+archive/ubuntu/gnome-settings-
daemon/+packages
On wayland I see no difference; everything works as expected. Also with
a fresh lunar install in VirtualBox.
But my observations on Xorg with my regular install was
"After screen lock" indicates that gnome-shell is involved.
Also note: NVIDIA + wayland
** Also affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in
Btw, im-config 0.55-1 is not in Debian testing yet, which might be the
reason why you didn't see the issue there.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/2008279
Wow.. This is "interesting". Compare this with bug #2007379, where we
work around the problem which the now reversed upstream g-s-d commit
tries to address. (I wasn't aware of this upstream move.)
im-config 0.55-1 is already in lunar-release. Can the fact that im-
config now sets
** Description changed:
While preparing the gnome-settings-daemon 44 Beta update for Ubuntu
23.04, I noticed that I could no longer enter text in the address bars
for the Chromium or Firefox snaps.
Therefore, I reverted https://gitlab.gnome.org/GNOME/gnome-settings-
1 - 100 of 1590 matches
Mail list logo
