[Bug 2006756] Re: composite emoji shows extra vertical color lines
This bug was fixed in the package pango1.0 - 1.50.6+ds-2ubuntu1 --- pango1.0 (1.50.6+ds-2ubuntu1) jammy; urgency=medium * Cherry-pick fix for vertical color lines showing with composite emoji (LP: #2006756) -- Jeremy Bicha Thu, 09 Feb 2023 11:34:31 -0500 ** Changed in: pango1.0 (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/2006756 Title: composite emoji shows extra vertical color lines To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/2006756/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2006756] Update Released
The verification of the Stable Release Update for pango1.0 has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/2006756 Title: composite emoji shows extra vertical color lines To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/2006756/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968383] Re: Touchpad gesture animations trigger Object St.Button (0x56439bd53160), has been already disposed — impossible to get any property from it. This might be caused by the object having b
Tracking in https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6448 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #6448 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6448 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6448 Importance: Unknown Status: Unknown ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Medium -- 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/1968383 Title: Touchpad gesture animations trigger Object St.Button (0x56439bd53160), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. [windowPreview.js:566] To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1968383/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2008853] [NEW] Notifications block the view. Small size tweak needed to fix the bug
Public bug reported: Various notifications are shown in Nautilus, when files are deleted etc. These notification boxes (as shown in the attached screenshot) are a UI/UX nightmare, since each time such an action is performed, the box blocks part of the screen, forcing the User to either pause until the box disappears or forcing the User to click the close button of the message. It is a poor UI/UX design, to block the view with such a message. A simple temporary fix for this UI/UX bug, is to simply reduce the height of the message box (as shown in the bottom of the screenshot). I have requested for this earlier too. Please implement it at least this time, and please release the fix for Ubuntu 20.04 too. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1.20.04.2 ProcVersionSignature: Ubuntu 5.15.0-60.66~20.04.1-generic 5.15.78 Uname: Linux 5.15.0-60-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Mar 1 10:11:59 2023 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'205' b'org.gnome.nautilus.window-state' b'initial-size' b'(899, 826)' b'org.gnome.nautilus.preferences' b'click-policy' b"'single'" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" InstallationDate: Installed on 2023-01-16 (43 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "Screenshot showing how the notifications block the folders and force the user to wait or have to click unnecessarily to close the notification" https://bugs.launchpad.net/bugs/2008853/+attachment/5650611/+files/obscured.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2008853 Title: Notifications block the view. Small size tweak needed to fix the bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2008853/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1857392] Re: Window manager warning: Overwriting existing binding of keysym...
Although your log is full of this bug's message, it has nothing to do with "computer may stop responding". It looks like you have some kernel crashes there so should create a new bug about them with: ubuntu-bug linux -- 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/1857392 Title: Window manager warning: Overwriting existing binding of keysym... To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1857392/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1857392] Re: Window manager warning: Overwriting existing binding of keysym...
Periodically, the computer may stop responding to commands. Linux toshiba-Inspiron-15-3511 5.19.0-32-generic #33~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Mon Jan 30 17:03:34 UTC 2 x86_64 x86_64 x86_64 GNU/Linux ** Attachment added: "journalctl_28_02_2023.zip" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1857392/+attachment/5650602/+files/journalctl_28_02_2023.zip -- 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/1857392 Title: Window manager warning: Overwriting existing binding of keysym... To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1857392/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1915910] Re: evince does not print (apparmor, pxgsettings)
This bug was fixed in the package evince - 42.3-0ubuntu3 --- evince (42.3-0ubuntu3) jammy; urgency=medium * debian/apparmor-profile: - allow access to the libproxy helper pxgsettings which is needed on some configuration to access remote printers (LP: #1915910) -- Sebastien Bacher Wed, 07 Dec 2022 11:35:07 +0100 ** Changed in: evince (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1915910 Title: evince does not print (apparmor, pxgsettings) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1915910/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2003176] Re: SRU: metacity crashes while minimizing a windows that has undocked child
This bug was fixed in the package metacity - 1:3.36.1-1ubuntu1 --- metacity (1:3.36.1-1ubuntu1) focal; urgency=medium * Backport upstream patch to fix metacity crash when a parent window is minimized while a docked window is undocked (LP: #2003176). * Backport upstream patch to fix restoring docked window when the parent window is unminimized. -- Mustafa Kemal GILOR Wed, 18 Jan 2023 13:10:06 +0300 ** Changed in: metacity (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/2003176 Title: SRU: metacity crashes while minimizing a windows that has undocked child To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/2003176/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2008770] Re: Sound: seg fault if env variable not set (v41.7)
Thanks for your report! Well, "the user" normally has that variable set. ;) But it's still a valid bug. I pushed a fix to the repo, so it will be fixed in Ubuntu 23.04. ** 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, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2008770 Title: Sound: seg fault if env variable not set (v41.7) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2008770/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1971558] Re: dropbox menu icon often replaced with three dots under Jammy
I've not been able to reproduce it lock/unlock, but I do reloading the shell. In such case, I bisected it to this commit: https://github.com/ubuntu/gnome-shell-extension- appindicator/commit/6fa6ee276692e517148c2cba8764114706a20d8f Can someone please check if applying it (can just edit /usr/share/gnome- shell/extensions/ubuntu-appindicat...@ubuntu.com/appIndicator.js) fixes the issue for you? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1971558 Title: dropbox menu icon often replaced with three dots under Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1971558/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2004424] Re: This bug affects me.
Provide logs and better title or this report is useless -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/2004424 Title: This bug affects me. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/2004424/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2008779] [NEW] gvfsd-mtp crashed with SIGSEGV in g_mount_spec_get()
Public bug reported: The desktop session keeps crashing on ubuntu 22.04 LTS ```Title: gvfsd-mtp crashed with SIGSEGV in g_mount_spec_get() UpgradeStatus: No upgrade log present (probaby fresh install) _MarkForUpload: True separator: ``` ** Affects: gvfs (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/2008779 Title: gvfsd-mtp crashed with SIGSEGV in g_mount_spec_get() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/2008779/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1801813] Re: gvfsd-mtp crashed with SIGSEGV
*** This bug is a duplicate of bug 1706097 *** https://bugs.launchpad.net/bugs/1706097 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gvfs (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1801813 Title: gvfsd-mtp crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1801813/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1966635] Re: can't move file/directory by drag and drop by using touch monitor
** Tags added: originate-from-2006685 sutton -- 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/1966635 Title: can't move file/directory by drag and drop by using touch monitor To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1966635/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1929209] Re: [i915] external monitor goes black for several seconds at a time, randomly
My issue with Intel 12th gen regularly losing display signal *appears* to be fixed by using kernel 6.1. Fingers crossed it stays fixed. -- 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/1929209 Title: [i915] external monitor goes black for several seconds at a time, randomly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1929209/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2008770] [NEW] Sound: seg fault if env variable not set (v41.7)
Public bug reported:
On Ubuntu 22.04, gnome-control-center (41.7) crashes with a segmentation fault
if $XDG_CURRENT_DESKTOP is not set, upon entering the Sound menu.
This is due to the passing of a NULL pointer into strstr which results in
undefined behavior.
For the user it gets worse, as entering Sound instantly crashes the
application and subsequent launches will keep starting in Sound and just
keep crashing. The application is then not usable, and it's not directly
clear how to reset it as to not start in Sound.
In this case, it is partly my fault since I don't use a GNOME desktop
environment resulting in this env variable not being set.
panels/sound/cc-sound-panel.c:305
if (strstr (g_getenv("XDG_CURRENT_DESKTOP"), "ubuntu") != NULL) {
Which seem to originate from
debian/patches/ubuntu/sound-Allow-volume-to-be-set-above-100.patch
-> gnome-control-center_41.7-0ubuntu0.22.04.6.debian.tar.xz
Fixed by adding `alias XDG_CURRENT_DESKTOP=test` in .bashrc.
System:
Sway (Ubuntu's default DE is also installed)
Ubuntu 22.04 (updated 2023-02-28)
Linux 5.15.0-60-generic #66-Ubuntu SMP Fri Jan 20 14:29:49 UTC 2023 x86_64
x86_64 x86_64 GNU/Linux
** Affects: gnome-control-center (Ubuntu)
Importance: Undecided
Status: New
** Tags: crash patch
** Description changed:
On Ubuntu 22.04, gnome-control-center (41.7) crashes with a segmentation
fault if $XDG_CURRENT_DESKTOP is not set, upon entering the Sound menu.
This is due to the passing of a NULL pointer into strstr which results in
undefined behavior.
For the user it gets worse, as entering Sound instantly crashes the
application and subsequent launches will keep starting in Sound and just
keep crashing. The application is then not usable, and it's not directly
clear how to reset it as to not start in Sound.
In this case, it is partly my fault since I don't use a GNOME desktop
environment resulting in this env variable not being set.
- **panels/sound/cc-sound-panel.c:305** \
- `if (strstr (g_getenv("XDG_CURRENT_DESKTOP"), "ubuntu") != NULL) {`
+ panels/sound/cc-sound-panel.c:305
+ if (strstr (g_getenv("XDG_CURRENT_DESKTOP"), "ubuntu") != NULL) {
Which seem to originate from debian/patches/ubuntu/sound-Allow-volume-
to-be-set-above-100.patch from gnome-control-
center_41.7-0ubuntu0.22.04.6.debian.tar.xz
Fixed by adding `alias XDG_CURRENT_DESKTOP=test` in .bashrc.
- ```
+
System:
- Sway (Ubuntu's default DE is also installed)
- Ubuntu 22.04 (updated 2023-02-28)
- Linux 5.15.0-60-generic #66-Ubuntu SMP Fri Jan 20 14:29:49 UTC 2023
x86_64 x86_64 x86_64 GNU/Linux
- ```
+ Sway (Ubuntu's default DE is also installed)
+ Ubuntu 22.04 (updated 2023-02-28)
+ Linux 5.15.0-60-generic #66-Ubuntu SMP Fri Jan 20 14:29:49 UTC 2023
x86_64 x86_64 x86_64 GNU/Linux
** Description changed:
On Ubuntu 22.04, gnome-control-center (41.7) crashes with a segmentation
fault if $XDG_CURRENT_DESKTOP is not set, upon entering the Sound menu.
This is due to the passing of a NULL pointer into strstr which results in
undefined behavior.
For the user it gets worse, as entering Sound instantly crashes the
application and subsequent launches will keep starting in Sound and just
keep crashing. The application is then not usable, and it's not directly
clear how to reset it as to not start in Sound.
In this case, it is partly my fault since I don't use a GNOME desktop
environment resulting in this env variable not being set.
panels/sound/cc-sound-panel.c:305
- if (strstr (g_getenv("XDG_CURRENT_DESKTOP"), "ubuntu") != NULL) {
+ if (strstr (g_getenv("XDG_CURRENT_DESKTOP"), "ubuntu") != NULL) {
- Which seem to originate from debian/patches/ubuntu/sound-Allow-volume-
- to-be-set-above-100.patch from gnome-control-
- center_41.7-0ubuntu0.22.04.6.debian.tar.xz
+ Which seem to originate from
+ debian/patches/ubuntu/sound-Allow-volume-to-be-set-above-100.patch
+ -> gnome-control-center_41.7-0ubuntu0.22.04.6.debian.tar.xz
Fixed by adding `alias XDG_CURRENT_DESKTOP=test` in .bashrc.
-
-
System:
Sway (Ubuntu's default DE is also installed)
Ubuntu 22.04 (updated 2023-02-28)
Linux 5.15.0-60-generic #66-Ubuntu SMP Fri Jan 20 14:29:49 UTC 2023
x86_64 x86_64 x86_64 GNU/Linux
--
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 variable not set (v41.7)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2008770/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1961508] Re: Dock displaying over window after resuming from blank screen
Hi, affected. Notebook. Ubuntu 22.04.2 LTS, Wayland. Gnome Version 42.5 Affected apps: Firefox, gnome-terminal. Hardware: HP EliteBook 850 G8 Notebook PC 11th Gen Intel® Core™ i7-1185G7 @ 3.00GHz × 8 Mesa Intel® Xe Graphics (TGL GT2) It happened once with this flow but I couldn't reproduce it immediately after: 1. Locking the screen by closing my notebook. 2. Opening my notebook and unlocking the login screen 3. Switching from a window like Firefox with Alt+Tab to the terminal 4. At that point, the dock overlapped the terminal and when alt-tabbing again, it also overlapped Firefox. -- 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/1961508 Title: Dock displaying over window after resuming from blank screen To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1961508/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968040] Re: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]
Thanks Michal. The diff looks perfectly clean and exactly what I would expect in that no part of the system has changed that would fool mutter into doing the wrong thing. So it's just that mutter's done the wrong thing... somehow. And that wrong thing is not visible in the above text files. -- 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/1968040 Title: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument] To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1968040/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
