[Desktop-packages] [Bug 2060266] [NEW] gnome-session no longer supports --builtin
You have been subscribed to a public bug:
Hi,
`gnome-session.service` has the following:
| [Service]
| ExecStart=/bin/sh -exc '[ "$DESKTOP_SESSION" != "gnome-classic" ] || export |
GNOME_SHELL_SESSION_MODE=classic; \
| export GNOME_SESSION_XDG_SESSION_PATH=${XDG_SESSION_PATH}; \
| [ "$DESKTOP_SESSION" = gnome-flashback-metacity ] && \
| exec gnome-session --builtin --session=$DESKTOP_SESSION
--disable-acceleration-check || \
| exec gnome-session --builtin --session=$DESKTOP_SESSION'
Unfortunately, the latest `gnome-session` no longer supports
`--builtin`. This causes login failures, in particular for me, using
Unity, I get logged back out from the unity greeter.
| $ apt-cache policy gnome-session-bin
| gnome-session-bin:
| Installed: 46.0-1ubuntu2
| Candidate: 46.0-1ubuntu2
| Version table:
| *** 46.0-1ubuntu2 500
| 500 http://haw-test.archive.ubuntu.com/ubuntu noble/main amd64
Packages
| 100 /var/lib/dpkg/status
| 45.0-1ubuntu1 500
| 500 http://haw-test.archive.ubuntu.com/ubuntu noble-updates/main
amd64 Packages
| $ gnome-session --builtin
|
| ** (gnome-session-binary:5602): WARNING **: 15:35:22.156: Unknown option
--builtin
Removing `--builtin` from `/usr/lib/systemd/user/gnome-session.service`
let's me log in.
With that though, I was not able to input text in chromium (installed
via the snap).
Downgrading `gnome-session-bin`, `gnome-session-common`, and `unity-
session` back to 45.0-1ubuntu1 restores things for me:
| [hloeung@dharkan tmp]$ apt-cache policy gnome-session-bin
| gnome-session-bin:
| Installed: 45.0-1ubuntu1
| Candidate: 46.0-1ubuntu2
| Version table:
| 46.0-1ubuntu2 500
| 500 http://haw-test.archive.ubuntu.com/ubuntu noble/main amd64
Packages
| *** 45.0-1ubuntu1 500
| 500 http://haw-test.archive.ubuntu.com/ubuntu noble-updates/main
amd64 Packages
| 100 /var/lib/dpkg/status
| [hloeung@dharkan tmp]$ apt-cache policy gnome-session-common
| gnome-session-common:
| Installed: 45.0-1ubuntu1
| Candidate: 46.0-1ubuntu2
| Version table:
| 46.0-1ubuntu2 500
| 500 http://haw-test.archive.ubuntu.com/ubuntu noble/main amd64
Packages
| *** 45.0-1ubuntu1 500
| 500 http://haw-test.archive.ubuntu.com/ubuntu noble-updates/main
amd64 Packages
| 100 /var/lib/dpkg/status
| [hloeung@dharkan tmp]$ apt-cache policy unity-session
| unity-session:
| Installed: 45.0-1ubuntu1
| Candidate: 46.0-1ubuntu2
| Version table:
| 46.0-1ubuntu2 500
| 500 http://haw-test.archive.ubuntu.com/ubuntu noble/universe amd64
Packages
| *** 45.0-1ubuntu1 500
| 500 http://haw-test.archive.ubuntu.com/ubuntu noble-updates/universe
amd64 Packages
| 100 /var/lib/dpkg/status
** Affects: gnome-session (Ubuntu)
Importance: Undecided
Status: New
** Tags: noble
--
gnome-session no longer supports --builtin
https://bugs.launchpad.net/bugs/2060266
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2060266] Re: gnome-session no longer supports --builtin
Please find out what package is providing the outdated 'gnome-
session.service' file.
** No longer affects: gnome-session (Ubuntu Noble)
** Changed in: gnome-session (Ubuntu)
Status: New => Incomplete
** Package changed: gnome-session (Ubuntu) => ubuntu
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/2060266
Title:
gnome-session no longer supports --builtin
Status in Ubuntu:
Incomplete
Bug description:
Hi,
`gnome-session.service` has the following:
| [Service]
| ExecStart=/bin/sh -exc '[ "$DESKTOP_SESSION" != "gnome-classic" ] || export
| GNOME_SHELL_SESSION_MODE=classic; \
| export GNOME_SESSION_XDG_SESSION_PATH=${XDG_SESSION_PATH}; \
| [ "$DESKTOP_SESSION" = gnome-flashback-metacity ] && \
| exec gnome-session --builtin --session=$DESKTOP_SESSION
--disable-acceleration-check || \
| exec gnome-session --builtin --session=$DESKTOP_SESSION'
Unfortunately, the latest `gnome-session` no longer supports
`--builtin`. This causes login failures, in particular for me, using
Unity, I get logged back out from the unity greeter.
| $ apt-cache policy gnome-session-bin
| gnome-session-bin:
| Installed: 46.0-1ubuntu2
| Candidate: 46.0-1ubuntu2
| Version table:
| *** 46.0-1ubuntu2 500
| 500 http://haw-test.archive.ubuntu.com/ubuntu noble/main amd64
Packages
| 100 /var/lib/dpkg/status
| 45.0-1ubuntu1 500
| 500 http://haw-test.archive.ubuntu.com/ubuntu noble-updates/main
amd64 Packages
| $ gnome-session --builtin
|
| ** (gnome-session-binary:5602): WARNING **: 15:35:22.156: Unknown option
--builtin
Removing `--builtin` from `/usr/lib/systemd/user/gnome-
session.service` let's me log in.
With that though, I was not able to input text in chromium (installed
via the snap).
Downgrading `gnome-session-bin`, `gnome-session-common`, and `unity-
session` back to 45.0-1ubuntu1 restores things for me:
| [hloeung@dharkan tmp]$ apt-cache policy gnome-session-bin
| gnome-session-bin:
| Installed: 45.0-1ubuntu1
| Candidate: 46.0-1ubuntu2
| Version table:
| 46.0-1ubuntu2 500
| 500 http://haw-test.archive.ubuntu.com/ubuntu noble/main amd64
Packages
| *** 45.0-1ubuntu1 500
| 500 http://haw-test.archive.ubuntu.com/ubuntu noble-updates/main
amd64 Packages
| 100 /var/lib/dpkg/status
| [hloeung@dharkan tmp]$ apt-cache policy gnome-session-common
| gnome-session-common:
| Installed: 45.0-1ubuntu1
| Candidate: 46.0-1ubuntu2
| Version table:
| 46.0-1ubuntu2 500
| 500 http://haw-test.archive.ubuntu.com/ubuntu noble/main amd64
Packages
| *** 45.0-1ubuntu1 500
| 500 http://haw-test.archive.ubuntu.com/ubuntu noble-updates/main
amd64 Packages
| 100 /var/lib/dpkg/status
| [hloeung@dharkan tmp]$ apt-cache policy unity-session
| unity-session:
| Installed: 45.0-1ubuntu1
| Candidate: 46.0-1ubuntu2
| Version table:
| 46.0-1ubuntu2 500
| 500 http://haw-test.archive.ubuntu.com/ubuntu noble/universe amd64
Packages
| *** 45.0-1ubuntu1 500
| 500 http://haw-test.archive.ubuntu.com/ubuntu
noble-updates/universe amd64 Packages
| 100 /var/lib/dpkg/status
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2060266/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2057773] Re: After the latest kernel update if you toggle wifi on and off the system crashes
Today I got a kernel update and now the wifi toggle is fixed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2057773 Title: After the latest kernel update if you toggle wifi on and off the system crashes Status in network-manager package in Ubuntu: New Bug description: I got a kernel update today and updated it. So after i updated it and toggled wifi on and off the system soft locked it is nonfunctional but the mouse still works. It even can't do a sudo reboot or reboot at all. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: network-manager 1.44.2-1ubuntu1.2 ProcVersionSignature: Ubuntu 6.5.0-25.25-generic 6.5.13 Uname: Linux 6.5.0-25-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Mar 13 15:23:23 2024 InstallationDate: Installed on 2024-01-22 (51 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) IpRoute: default via 192.168.0.1 dev wlp2s0 proto dhcp src 192.168.2.37 metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.0.0/22 dev wlp2s0 proto kernel scope link src 192.168.2.37 metric 600 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.44.2 connected started full enabled enabled enabled missing enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2057773/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1988393] Re: JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js 287]: Too many arguments to method Gio.AsyncInitable.init_async: expected 3, got 4
What package version are you using on jammy to experience this bug? ** Tags added: rls-jj-incoming ** Tags removed: regression-proposed ** Tags added: regression-update ** Also affects: gjs (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: gjs (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: gjs (Ubuntu Jammy) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1988393 Title: JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js 287]: Too many arguments to method Gio.AsyncInitable.init_async: expected 3, got 4 Status in gjs: Fix Released Status in gjs package in Ubuntu: Fix Released Status in gjs source package in Jammy: Incomplete Bug description: I'm seeing this in everyone's kinetic logs: JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js 287]: Too many arguments to method Gio.AsyncInitable.init_async: expected 3, got 4 and it appears gjs is the only place where too many arguments are provided. To manage notifications about this bug go to: https://bugs.launchpad.net/gjs/+bug/1988393/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2060391] Re: gnome desktop cannot start as mutter fails to find drmModeCloseFB
The bug persists after reinstalling libdrm2. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2060391 Title: gnome desktop cannot start as mutter fails to find drmModeCloseFB Status in mutter package in Ubuntu: Incomplete Bug description: mutter: symbol lookup error: /lib/x86_64-linux-gnu/libmutter-14.so.0: undefined symbol: drmModeCloseFB Package libdrm2: i 2.4.120-2 noble 500 Package libdrm2:i386: i 2.4.120-2 noble 500 Package libmutter-14-0: i 46.0-1ubuntu6 noble 500 Package mutter: i 46.0-1ubuntu6 noble 500 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2060391/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2060391] Re: gnome desktop cannot start as mutter fails to find drmModeCloseFB
Yes, I do have librdm2 version 2.4.120-2 both for amd64 and i386 (dpkg won't let me install different versions for each). As the graphical session failed to start, I tried to invoke apport-collect from terminal (with multi-user.target -ish level of services having already started), but it redirected me to the "default" browser, which happens to be firefox for GUI and lynx for terminal in my case. I couldn't progress after the password prompt as lynx apparently doesn't support http Referer feature. Here, apport should present its own login prompt or allow fetching the access token from system keyring for more robustness. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2060391 Title: gnome desktop cannot start as mutter fails to find drmModeCloseFB Status in mutter package in Ubuntu: Incomplete Bug description: mutter: symbol lookup error: /lib/x86_64-linux-gnu/libmutter-14.so.0: undefined symbol: drmModeCloseFB Package libdrm2: i 2.4.120-2 noble 500 Package libdrm2:i386: i 2.4.120-2 noble 500 Package libmutter-14-0: i 46.0-1ubuntu6 noble 500 Package mutter: i 46.0-1ubuntu6 noble 500 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2060391/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1970291] Re: [nvidia] Secondary monitor performance is slow on an Nvidia hybrid system in Wayland sessions
It's complicated. You will at least need libmutter version 46.0 installed to get the fix for bug 1970291. But then you still have bug 2038801 slowing you down. That one can be solved by adding CLUTTER_PAINT=disable-dynamic-max-render-time to /etc/environment. Or just wait for libmutter 46.1 which I expect will have both fixes. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1970291 Title: [nvidia] Secondary monitor performance is slow on an Nvidia hybrid system in Wayland sessions Status in GNOME Shell: New Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Bug description: In session with Wayland the Nvidia driver settings do not load. And there is a sluggishness when opening apps, show applications menu, maximize, changing workspace, resize, changing monitor windows etc. When in an Xorg session the Nvidia settings load correctly and the performance is satisfactory. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 510.60.02 Wed Mar 16 11:24:05 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 25 21:18:08 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:2086] NVIDIA Corporation TU116M [GeForce GTX 1660 Ti Mobile] [10de:2191] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation TU116M [GeForce GTX 1660 Ti Mobile] [8086:2086] InstallationDate: Installed on 2022-04-24 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) MachineType: Avell High Performance A60 MUV ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=894cb598-7172-481c-a449-3133b8f226e5 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/11/2020 dmi.bios.release: 5.13 dmi.bios.vendor: Intel Corp. dmi.bios.version: QCCFL357.0122.2020.0911.1520 dmi.board.name: Avell High Performance dmi.board.vendor: Avell High Performance dmi.chassis.type: 10 dmi.chassis.vendor: Avell High Performance dmi.chassis.version: 1.0 dmi.ec.firmware.release: 1.25 dmi.modalias: dmi:bvnIntelCorp.:bvrQCCFL357.0122.2020.0911.1520:bd09/11/2020:br5.13:efr1.25:svnAvellHighPerformance:pnA60MUV:pvr:rvnAvellHighPerformance:rnAvellHighPerformance:rvr:cvnAvellHighPerformance:ct10:cvr1.0:skuA60MUV: dmi.product.family: A60 MUV dmi.product.name: A60 MUV dmi.product.sku: A60 MUV dmi.sys.vendor: Avell High Performance version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1970291/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2054761] Re: gnome-shell crashed with signal 5: Settings schema 'org.gnome.mutter.wayland' does not contain a key named 'xwayland-allow-byte-swapped-clients'
Maybe fixing bug 2060423 would also help here? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2054761 Title: gnome-shell crashed with signal 5: Settings schema 'org.gnome.mutter.wayland' does not contain a key named 'xwayland- allow-byte-swapped-clients' Status in Mutter: Fix Released Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Feb 21 21:39:12 autopkgtest gnome-shell[17945]: Settings schema 'org.gnome.mutter.wayland' does not contain a key named 'xwayland-allow-byte-swapped-clients' Feb 21 21:39:12 autopkgtest gnome-session-binary[17908]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 5 Feb 21 21:39:12 autopkgtest gnome-shell[17959]: Settings schema 'org.gnome.mutter.wayland' does not contain a key named 'xwayland-allow-byte-swapped-clients' Feb 21 21:39:12 autopkgtest gnome-session-binary[17908]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 5 https://errors.ubuntu.com/problem/bf714caff944bed915a3c4321664107c65547d1f https://errors.ubuntu.com/oops/af2e99fc-d101-11ee-8a58-fa163ec8ca8c To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2054761/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2060423] Re: gnome-shell crashes instead of displaying a login screen (mutter-common package version mismatch)
Rather than treating this as a temporary issue I think we should fix the
dependencies that led to it.
** Changed in: mutter (Ubuntu)
Status: New => Triaged
** Description changed:
- gnome-shell crashes instead of displaying a login screen. It seems the
- cause is a package version mismatch in mutter-common:
+ gnome-shell crashes instead of displaying a login screen:
+
+ gnome-shell[1954]: Running GNOME Shell (using mutter 45.3) as a Wayland
display server
+ gnome-shell[1954]: Settings schema 'org.gnome.mutter.x11' is not installed
+
+ It seems the cause is a package version mismatch in mutter-common:
ii gir1.2-mutter-13:amd64 45.3-1ubuntu1
amd64GObject introspection data for Mutter
ii libmutter-13-0:amd64 45.3-1ubuntu1
amd64window manager library from the Mutter window
manager
ii libmutter-13-dev:amd64 45.3-1ubuntu1
amd64Development files for the Mutter window manager
ii libmutter-test-13 45.3-1ubuntu1
amd64Test helper library for GNOME's window manager
library
ii mutter 45.3-1ubuntu1
amd64Example window manager using GNOME's window manager
library
ii mutter-13-tests45.3-1ubuntu1
amd64Tests for GNOME's window manager library
ii mutter-common 46.0-1ubuntu6
all shared files for the Mutter window manager
ii mutter-common-bin 45.3-1ubuntu1
amd64shared programs for the Mutter window manager
Downgrading mutter-common to
https://launchpad.net/ubuntu/+source/mutter/45.3-1ubuntu1/+build/27621415/+files/mutter-
common_45.3-1ubuntu1_all.deb appears to fix it.
** Summary changed:
- gnome-shell crashes instead of displaying a login screen (mutter-common
package version mismatch)
+ gnome-shell crashes ("Oh no! Something has gone wrong.") instead of
displaying a login screen (mutter-common package version mismatch)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2060423
Title:
gnome-shell crashes ("Oh no! Something has gone wrong.") instead of
displaying a login screen (mutter-common package version mismatch)
Status in mutter package in Ubuntu:
Triaged
Bug description:
gnome-shell crashes instead of displaying a login screen:
gnome-shell[1954]: Running GNOME Shell (using mutter 45.3) as a Wayland
display server
gnome-shell[1954]: Settings schema 'org.gnome.mutter.x11' is not installed
It seems the cause is a package version mismatch in mutter-common:
ii gir1.2-mutter-13:amd64 45.3-1ubuntu1
amd64GObject introspection data for Mutter
ii libmutter-13-0:amd64 45.3-1ubuntu1
amd64window manager library from the Mutter window
manager
ii libmutter-13-dev:amd64 45.3-1ubuntu1
amd64Development files for the Mutter window manager
ii libmutter-test-13 45.3-1ubuntu1
amd64Test helper library for GNOME's window manager
library
ii mutter 45.3-1ubuntu1
amd64Example window manager using GNOME's window manager
library
ii mutter-13-tests45.3-1ubuntu1
amd64Tests for GNOME's window manager library
ii mutter-common 46.0-1ubuntu6
all shared files for the Mutter window manager
ii mutter-common-bin 45.3-1ubuntu1
amd64shared programs for the Mutter window manager
Downgrading mutter-common to
https://launchpad.net/ubuntu/+source/mutter/45.3-1ubuntu1/+build/27621415/+files/mutter-
common_45.3-1ubuntu1_all.deb appears to fix it.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2060423/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2060423] [NEW] gnome-shell crashes ("Oh no! Something has gone wrong.") instead of displaying a login screen (mutter-common package version mismatch)
Public bug reported:
gnome-shell crashes instead of displaying a login screen:
gnome-shell[1954]: Running GNOME Shell (using mutter 45.3) as a Wayland display
server
gnome-shell[1954]: Settings schema 'org.gnome.mutter.x11' is not installed
It seems the cause is a package version mismatch in mutter-common:
ii gir1.2-mutter-13:amd64 45.3-1ubuntu1
amd64GObject introspection data for Mutter
ii libmutter-13-0:amd64 45.3-1ubuntu1
amd64window manager library from the Mutter window manager
ii libmutter-13-dev:amd64 45.3-1ubuntu1
amd64Development files for the Mutter window manager
ii libmutter-test-13 45.3-1ubuntu1
amd64Test helper library for GNOME's window manager library
ii mutter 45.3-1ubuntu1
amd64Example window manager using GNOME's window manager
library
ii mutter-13-tests45.3-1ubuntu1
amd64Tests for GNOME's window manager library
ii mutter-common 46.0-1ubuntu6
all shared files for the Mutter window manager
ii mutter-common-bin 45.3-1ubuntu1
amd64shared programs for the Mutter window manager
Downgrading mutter-common to
https://launchpad.net/ubuntu/+source/mutter/45.3-1ubuntu1/+build/27621415/+files/mutter-
common_45.3-1ubuntu1_all.deb appears to fix it.
** Affects: mutter (Ubuntu)
Importance: High
Status: Triaged
** Tags: noble
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2060423
Title:
gnome-shell crashes ("Oh no! Something has gone wrong.") instead of
displaying a login screen (mutter-common package version mismatch)
Status in mutter package in Ubuntu:
Triaged
Bug description:
gnome-shell crashes instead of displaying a login screen:
gnome-shell[1954]: Running GNOME Shell (using mutter 45.3) as a Wayland
display server
gnome-shell[1954]: Settings schema 'org.gnome.mutter.x11' is not installed
It seems the cause is a package version mismatch in mutter-common:
ii gir1.2-mutter-13:amd64 45.3-1ubuntu1
amd64GObject introspection data for Mutter
ii libmutter-13-0:amd64 45.3-1ubuntu1
amd64window manager library from the Mutter window
manager
ii libmutter-13-dev:amd64 45.3-1ubuntu1
amd64Development files for the Mutter window manager
ii libmutter-test-13 45.3-1ubuntu1
amd64Test helper library for GNOME's window manager
library
ii mutter 45.3-1ubuntu1
amd64Example window manager using GNOME's window manager
library
ii mutter-13-tests45.3-1ubuntu1
amd64Tests for GNOME's window manager library
ii mutter-common 46.0-1ubuntu6
all shared files for the Mutter window manager
ii mutter-common-bin 45.3-1ubuntu1
amd64shared programs for the Mutter window manager
Downgrading mutter-common to
https://launchpad.net/ubuntu/+source/mutter/45.3-1ubuntu1/+build/27621415/+files/mutter-
common_45.3-1ubuntu1_all.deb appears to fix it.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2060423/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1917926] Re: Window focus/clicking/moving failures for Xorg sessions in 3.38.3-3ubuntu1
This bug has been closed for 3 years so current issues ideally shouldn't be discussed here. If you're using Nvidia then please see bug 2059847. If that's not the issue then please run this command to open a new bug: ubuntu-bug libmutter-13-0 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1917926 Title: Window focus/clicking/moving failures for Xorg sessions in 3.38.3-3ubuntu1 Status in mutter package in Ubuntu: Fix Released Bug description: I switched to an Xorg session in hirsute today after upgrading gnome- shell and mutter packages which just hit the release package. There are very strange focus issues. Clicking on a window doesn't raise it to the front, alt-tab seems to only switch between a subset of the one windows. It's impossible to move windows with the mouse and resizing does not work. This occurred with: gnome-shell=3.38.3-3ubuntu1 mutter=3.38.3-3ubuntu1 Downgrading these packages fixed it: gnome-shell=3.38.3-2ubuntu2 mutter=3.38.3-2ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1917926/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2060204] Re: Resolution drop on third monitor on USB C
Hi Robby, What's the display layout used, e.g. extended mode, mirror mode? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2060204 Title: Resolution drop on third monitor on USB C Status in mutter package in Ubuntu: New Bug description: I have a laptop with an integrated intel intel gpu, 2/3 days ago it was working fine; I have 1 monitor plugged with hdmi and the other one with USB-c Now, the one plugged with USB-C get a lower resolution 1024*768 (not changeable) if the HDMI is plugged at the same time (it works well if I only have the USB c plugged) Feel free to ask if you need information cat /var/log/apt/history.log (relevant lines) Start-Date: 2024-03-29 14:21:01 Commandline: apt upgrade -y Requested-By: roudonro (1000) Upgrade: snapd:amd64 (2.58+22.04.1, 2.61.3+22.04) End-Date: 2024-03-29 14:21:15 Start-Date: 2024-04-02 16:06:48 Commandline: apt upgrade gnome-calendar Requested-By: roudonro (1000) Upgrade: coreutils:amd64 (8.32-4.1ubuntu1.1, 8.32-4.1ubuntu1.2), apt:amd64 (2.4.11, 2.4.12), libapt-pkg6.0:amd64 (2.4.11, 2.4.12), libmutter-10-0:amd64 (42.9-0ubuntu5, 42.9-0ubuntu7), libwbclient0:amd64 (2:4.15.13+dfsg-0ubuntu1.5, 2:4.15.13+dfsg-0ubuntu1.6), libsmbclient:amd64 (2:4.15.13+dfsg-0ubuntu1.5, 2:4.15.13+dfsg-0ubuntu1.6), mutter-common:amd64 (42.9-0ubuntu5, 42.9-0ubuntu7), update-notifier:amd64 (3.192.54.6, 3.192.54.8), gir1.2-mutter-10:amd64 (42.9-0ubuntu5, 42.9-0ubuntu7), samba-libs:amd64 (2:4.15.13+dfsg-0ubuntu1.5, 2:4.15.13+dfsg-0ubuntu1.6), apt-utils:amd64 (2.4.11, 2.4.12), update-notifier-common:amd64 (3.192.54.6, 3.192.54.8) End-Date: 2024-04-02 16:06:51 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 4 09:15:15 2024 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Dell TigerLake-LP GT2 [Iris Xe Graphics] [1028:0a21] InstallationDate: Installed on 2024-03-27 (7 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) MachineType: Dell Inc. Latitude 5520 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-26-generic root=UUID=d63caf0d-f785-49dd-94e1-518dc8a874be ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2023 dmi.bios.release: 1.31 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.31.0 dmi.board.name: 0DPC2R dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.31.0:bd08/08/2023:br1.31:svnDellInc.:pnLatitude5520:pvr:rvnDellInc.:rn0DPC2R:rvrA00:cvnDellInc.:ct10:cvr:sku0A21: dmi.product.family: Latitude dmi.product.name: Latitude 5520 dmi.product.sku: 0A21 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~22.04.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2060204/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2059847] Re: Input lag or freezes on Nvidia desktops with X11
Comment #37 needs a new bug report please. It looks like hybrid GPUs? Comment #39 should be discussed in bug 2007742. Not here. ** Changed in: mutter (Ubuntu Noble) Status: In Progress => Fix Committed ** Tags added: fixed-in-mutter-46.1 fixed-upstream -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2059847 Title: Input lag or freezes on Nvidia desktops with X11 Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Committed Status in mutter source package in Jammy: Triaged Status in mutter source package in Mantic: Triaged Status in mutter source package in Noble: Fix Committed Bug description: [ Impact ] Input or the entire screen may freeze at times on systems using the Nvidia Xorg driver with GNOME. [ Test Plan ] 0. Set up a desktop with Nvidia driver 545 or 550. 1. Log into Ubuntu, ensuring it's a Xorg session. 2. Open a Terminal, resize it vigorously, and type several lines of text. 3. Verify that input never froze for any perceptible period of time. 4. Run: journalctl -b0 | grep MetaSyncRing 5. Verify the above command does NOT show messages such as: Window manager warning: MetaSyncRing: Sync object is not ready -- were events handled properly? Window manager warning: MetaSyncRing: Sync object is not ready -- were events handled properly? Window manager warning: MetaSyncRing: Sync object is not ready -- were events handled properly? Window manager warning: MetaSyncRing: Too many reboots -- disabling [ Where problems could occur ] Anywhere in Nvidia (proprietary driver) Xorg sessions since that's the code being modified. [ Original Description ] There is a noticeable delay in input while using the native terminal. I belive it was caused by a recent software update, as this issue is relatively new. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Mar 30 19:57:13 2024 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2024-03-30 (0 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) SourcePackage: ubiquity Symptom: installation UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2059847/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2060391] Re: gnome desktop cannot start as mutter fails to find drmModeCloseFB
drmModeCloseFB is definitely in libdrm.so.2 version 2.4.120-2 on amd64. I wonder how or if i386 is different. I should also note that /lib/x86_64-linux-gnu/libmutter-14.so.0 might not be installed at all if you have package 'libdrm2:i386'. Please make sure that 'libdrm2:amd64' is installed and also execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 2060391 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Tags removed: regression-release ** Changed in: mutter (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2060391 Title: gnome desktop cannot start as mutter fails to find drmModeCloseFB Status in mutter package in Ubuntu: Incomplete Bug description: mutter: symbol lookup error: /lib/x86_64-linux-gnu/libmutter-14.so.0: undefined symbol: drmModeCloseFB Package libdrm2: i 2.4.120-2 noble 500 Package libdrm2:i386: i 2.4.120-2 noble 500 Package libmutter-14-0: i 46.0-1ubuntu6 noble 500 Package mutter: i 46.0-1ubuntu6 noble 500 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2060391/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2060412] Re: Gnome3 apps very slow
*** This bug is a duplicate of bug 2059847 *** https://bugs.launchpad.net/bugs/2059847 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 2059847, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 2059847 Input lag or freezes on Nvidia desktops with X11 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2060412 Title: Gnome3 apps very slow Status in gnome-shell package in Ubuntu: New Bug description: Gnome3 apps became very slow. Even type in interminal. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Apr 7 21:39:03 2024 DisplayManager: gdm3 InstallationDate: Installed on 2023-07-21 (261 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RelatedPackageVersions: mutter-common 42.9-0ubuntu7 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2023-07-23T12:30:16.555014 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2060412/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2060354] Re: Segfault in 2:21.1.4-2ubuntu1.7-22.04.9
A new symptom. While I'm working with NetBeans the system very often freezes randomly. Only reboot helps. I see next data in log: [ 235.747] (EE) BUG: triggered 'if (glyph->refcnt == 0)' [ 235.748] (EE) BUG: ../../../../render/glyph.c:252 in FreeGlyph() [ 235.748] (EE) [ 235.748] (EE) Backtrace: [ 235.748] (EE) 0: /usr/lib/xorg/Xorg (AddTraps+0x4e3b) [0x5590352dce3b] [ 235.748] (EE) 1: /usr/lib/xorg/Xorg (SendErrorToClient+0x354) [0x559035205144] [ 235.748] (EE) 2: /usr/lib/xorg/Xorg (InitFonts+0x3b4) [0x5590352091f4] [ 235.749] (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0x7f6d6bb0c083] [ 235.749] (EE) 4: /usr/lib/xorg/Xorg (_start+0x2e) [0x5590351f2ace] [ 235.749] (EE) [ 235.749] (EE) BUG: triggered 'if (glyph->refcnt == 0)' [ 235.749] (EE) BUG: ../../../../render/glyph.c:252 in FreeGlyph() [ 235.749] (EE) [ 235.749] (EE) Backtrace: [ 235.749] (EE) 0: /usr/lib/xorg/Xorg (AddTraps+0x4e3b) [0x5590352dce3b] [ 235.749] (EE) 1: /usr/lib/xorg/Xorg (SendErrorToClient+0x354) [0x559035205144] [ 235.749] (EE) 2: /usr/lib/xorg/Xorg (InitFonts+0x3b4) [0x5590352091f4] [ 235.750] (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0x7f6d6bb0c083] [ 235.750] (EE) 4: /usr/lib/xorg/Xorg (_start+0x2e) [0x5590351f2ace] [ 235.750] (EE) [ 235.750] (EE) [ 235.750] (EE) Backtrace: [ 235.751] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x559035366fdc] [ 235.751] (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7f6d6bcf0420] [ 235.752] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xcb) [0x7f6d6bb2b00b] [ 235.752] (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x12b) [0x7f6d6bb0a859] [ 235.753] (EE) 4: /lib/x86_64-linux-gnu/libc.so.6 (__fsetlocking+0x42e) [0x7f6d6bb7526e] [ 235.754] (EE) 5: /lib/x86_64-linux-gnu/libc.so.6 (pthread_attr_setschedparam+0x54c) [0x7f6d6bb7d2fc] [ 235.754] (EE) 6: /lib/x86_64-linux-gnu/libc.so.6 (pthread_attr_setschedparam+0xd28) [0x7f6d6bb7dad8] [ 235.755] (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (pthread_attr_setschedparam+0x2230) [0x7f6d6bb7efe0] [ 235.755] (EE) 8: /lib/x86_64-linux-gnu/libc.so.6 (pthread_attr_setschedparam+0x4172) [0x7f6d6bb80f22] [ 235.756] (EE) 9: /lib/x86_64-linux-gnu/libc.so.6 (realloc+0x2d6) [0x7f6d6bb83156] [ 235.756] (EE) 10: /usr/lib/xorg/Xorg (ReadRequestFromClient+0x4ab) [0x559035365e8b] [ 235.757] (EE) 11: /usr/lib/xorg/Xorg (SendErrorToClient+0x2ed) [0x5590352050dd] [ 235.757] (EE) 12: /usr/lib/xorg/Xorg (InitFonts+0x3b4) [0x5590352091f4] [ 235.758] (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0x7f6d6bb0c083] [ 235.758] (EE) 14: /usr/lib/xorg/Xorg (_start+0x2e) [0x5590351f2ace] [ 235.759] (EE) [ 235.759] (EE) Fatal server error: [ 235.759] (EE) Caught signal 6 (Aborted). Server aborting [ 235.759] (EE) [ 235.759] (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. [ 235.760] (EE) Please also check the log file at "/home/axenic/.local/share/xorg/Xorg.0.log" for additional information. [ 235.760] (EE) [ 235.760] (II) AIGLX: Suspending AIGLX clients for VT switch Or this: [ 1036.721] (EE) BUG: triggered 'if (glyph->refcnt == 0)' [ 1036.721] (EE) BUG: ../../../../render/glyph.c:252 in FreeGlyph() [ 1036.721] (EE) [ 1036.721] (EE) Backtrace: [ 1036.722] (EE) 0: /usr/lib/xorg/Xorg (AddTraps+0x4e3b) [0x5570de00de3b] [ 1036.723] (EE) 1: /usr/lib/xorg/Xorg (SendErrorToClient+0x354) [0x5570ddf36144] [ 1036.723] (EE) 2: /usr/lib/xorg/Xorg (InitFonts+0x3b4) [0x5570ddf3a1f4] [ 1036.723] (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0x7f317a306083] [ 1036.723] (EE) 4: /usr/lib/xorg/Xorg (_start+0x2e) [0x5570ddf23ace] [ 1036.723] (EE) [ 1036.723] (EE) [ 1036.723] (EE) Backtrace: [ 1036.723] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x5570de097fdc] [ 1036.724] (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7f317a4ea420] [ 1036.724] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xcb) [0x7f317a32500b] [ 1036.725] (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x12b) [0x7f317a304859] [ 1036.725] (EE) 4: /lib/x86_64-linux-gnu/libc.so.6 (__fsetlocking+0x42e) [0x7f317a36f26e] [ 1036.725] (EE) 5: /lib/x86_64-linux-gnu/libc.so.6 (pthread_attr_setschedparam+0x54c) [0x7f317a3772fc] [ 1036.726] (EE) 6: /lib/x86_64-linux-gnu/libc.so.6 (pthread_attr_setschedparam+0xd28) [0x7f317a377ad8] [ 1036.726] (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (pthread_attr_setschedparam+0x2ed3) [0x7f317a379c83] [ 1036.726] (EE) 8: /lib/x86_64-linux-gnu/libc.so.6 (__libc_calloc+0x85) [0x7f317a37db95] [ 1036.730] (EE) 9: /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so (radeon_drm_winsys_create+0x176878) [0x7f3178a79d18] [ 1036.730] (EE) 10: /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so (radeon_drm_winsys_create+0x17778d) [0x7f3178a7ac2d] [ 1036.731] (EE) 11:
[Desktop-packages] [Bug 2060412] [NEW] Gnome3 apps very slow
Public bug reported: Gnome3 apps became very slow. Even type in interminal. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Apr 7 21:39:03 2024 DisplayManager: gdm3 InstallationDate: Installed on 2023-07-21 (261 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RelatedPackageVersions: mutter-common 42.9-0ubuntu7 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2023-07-23T12:30:16.555014 ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2060412 Title: Gnome3 apps very slow Status in gnome-shell package in Ubuntu: New Bug description: Gnome3 apps became very slow. Even type in interminal. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Apr 7 21:39:03 2024 DisplayManager: gdm3 InstallationDate: Installed on 2023-07-21 (261 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RelatedPackageVersions: mutter-common 42.9-0ubuntu7 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2023-07-23T12:30:16.555014 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2060412/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1988754]
I have confirmed that this bug is still present in version 24.2. When inserting a page break followed by undo in the sample document there is a crash. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1988754 Title: libreoffice writer crashes when edit the page break Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: New Bug description: LibreOffice Writes crashes when editing the page break. It happens in Xubuntu 22.04.1 and also in LinuxMint 21. I have tried also using LibreOffice from ppa and it still crashes. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1988754/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2017786] Re: update script in ubuntu-meta not handling germinate or specified versions
** Changed in: ubuntu-mate-meta (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2017786 Title: update script in ubuntu-meta not handling germinate or specified versions Status in edubuntu-meta package in Ubuntu: Won't Fix Status in kubuntu-meta package in Ubuntu: Fix Released Status in lubuntu-meta package in Ubuntu: New Status in ubuntu-budgie-meta package in Ubuntu: New Status in ubuntu-mate-meta package in Ubuntu: Won't Fix Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-unity-meta package in Ubuntu: New Status in ubuntucinnamon-meta package in Ubuntu: New Status in ubuntukylin-meta package in Ubuntu: New Status in ubuntustudio-meta package in Ubuntu: Won't Fix Status in xubuntu-meta package in Ubuntu: Won't Fix Bug description: update script handled debootstrap and devscripts, does not handle germinate. also doesn't handle potential specified versions in the package directory. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/edubuntu-meta/+bug/2017786/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2060354] Re: Segfault in 2:21.1.4-2ubuntu1.7-22.04.9
In my case the crash happens randomly, when I'm working with NetBeans 21. I didn't any system updates. Perhaps the NetBeans made auto update. My log lile: [ 356.402] (EE) [ 356.402] (EE) Backtrace: [ 356.403] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x5594ee295fdc] [ 356.404] (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7f37ec080420] [ 356.405] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (__libc_malloc+0x11e) [0x7f37ebf121fe] [ 356.405] (EE) 3: /usr/lib/xorg/Xorg (SetGlyphPicture+0x15d) [0x5594ee201ced] [ 356.405] (EE) 4: /usr/lib/xorg/Xorg (AddTraps+0x4b5a) [0x5594ee20bb5a] [ 356.405] (EE) 5: /usr/lib/xorg/Xorg (SendErrorToClient+0x354) [0x5594ee134144] [ 356.405] (EE) 6: /usr/lib/xorg/Xorg (InitFonts+0x3b4) [0x5594ee1381f4] [ 356.406] (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0x7f37ebe9c083] [ 356.406] (EE) 8: /usr/lib/xorg/Xorg (_start+0x2e) [0x5594ee121ace] [ 356.406] (EE) [ 356.406] (EE) Segmentation fault at address 0x0 [ 356.406] (EE) Fatal server error: [ 356.406] (EE) Caught signal 11 (Segmentation fault). Server aborting [ 356.406] (EE) [ 356.406] (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. [ 356.406] (EE) Please also check the log file at "/home/user-name/.local/share/xorg/Xorg.0.log" for additional information. [ 356.406] (EE) [ 356.406] (II) AIGLX: Suspending AIGLX clients for VT switch [ 356.425] (EE) Server terminated with error (1). Closing log file. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/2060354 Title: Segfault in 2:21.1.4-2ubuntu1.7-22.04.9 Status in xorg-server package in Ubuntu: Confirmed Bug description: I just upgraded xserver-xorg-core and xserver-common to 2:21.1.4-2ubuntu1.7-22.04.9 and when starting IntelliJ IDEA Ultimate EAP (downloaded from JerBrains website) Xorg server crashes with segfault: X.Org X Server 1.21.1.4 X Protocol Version 11, Revision 0 Current Operating System: Linux nazar-pc 6.8.4-x64v4-xanmod1 #0~20240404.gdb9d4f4 SMP PREEMPT_DYNAMIC Thu Apr 4 20:28:35 UTC x86_64 Kernel command line: BOOT_IMAGE=/root/boot/vmlinuz-6.8.4-x64v4-xanmod1 root=UUID=5170aca4-061a-4c6c-ab00-bd7fc8ae6030 ro rootflags=subvol=root nosplash amd_iommu=on intel_iommu=on libahci.ignore_sss=1 fastboot xorg-server 2:21.1.4-2ubuntu1.7~22.04.9 (For technical support please see http://www.ubuntu.com/support) Current version of pixman: 0.40.0 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Sat Apr 6 15:28:18 2024 (==) Using system config directory "/usr/share/X11/xorg.conf.d" malloc(): unaligned tcache chunk detected (EE) (EE) Backtrace: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x5def21b09ab9] (EE) 1: /lib/x86_64-linux-gnu/libc.so.6 (__sigaction+0x50) [0x7ec01c442520] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (pthread_kill+0x12c) [0x7ec01c4969fc] (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (raise+0x16) [0x7ec01c442476] (EE) 4: /lib/x86_64-linux-gnu/libc.so.6 (abort+0xd3) [0x7ec01c4287f3] (EE) 5: /lib/x86_64-linux-gnu/libc.so.6 (__fsetlocking+0x426) [0x7ec01c489676] (EE) 6: /lib/x86_64-linux-gnu/libc.so.6 (timer_settime+0x2cc) [0x7ec01c4a0cfc] (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (malloc+0x33c) [0x7ec01c4a53dc] (EE) 8: /usr/lib/xorg/Xorg (SetGlyphPicture+0x15d) [0x5def21a6311d] (EE) 9: /usr/lib/xorg/Xorg (AddTraps+0x347a) [0x5def21a6b8da] (EE) 10: /usr/lib/xorg/Xorg (SendErrorToClient+0x365) [0x5def21993635] (EE) 11: /usr/lib/xorg/Xorg (InitFonts+0x3c4) [0x5def219976b4] (EE) 12: /lib/x86_64-linux-gnu/libc.so.6 (__libc_init_first+0x90) [0x7ec01c429d90] (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0x80) [0x7ec01c429e40] (EE) 14: /usr/lib/xorg/Xorg (_start+0x25) [0x5def21980605] (EE) (EE) Fatal server error: (EE) Caught signal 6 (Aborted). Server aborting (EE) (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. (EE) (II) AIGLX: Suspending AIGLX clients for VT switch (EE) Server terminated with error (1). Closing log file. Downgraded to 2:21.1.3-2ubuntu2 for now and it works. Looks like security backports were done incorrectly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/2060354/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to :
[Desktop-packages] [Bug 2060400] [NEW] Remmina crashes instantly when trying to open a remote session
Public bug reported: I've been testing Noble for a couple of weeks and Remmina has not been working. Fully upto date with regards to updates now and it's still crashing. The initial windows comes up allowing you to select a session. The various preference dialogues seem to work but as soon as you try to initiate a remote session it crashes instantly. No crash is shown on the command line. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: remmina 1.4.35+dfsg-0ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Apr 7 20:17:02 2024 InstallationDate: Installed on 2024-03-25 (13 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240323) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: remmina UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: remmina (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to remmina in Ubuntu. https://bugs.launchpad.net/bugs/2060400 Title: Remmina crashes instantly when trying to open a remote session Status in remmina package in Ubuntu: New Bug description: I've been testing Noble for a couple of weeks and Remmina has not been working. Fully upto date with regards to updates now and it's still crashing. The initial windows comes up allowing you to select a session. The various preference dialogues seem to work but as soon as you try to initiate a remote session it crashes instantly. No crash is shown on the command line. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: remmina 1.4.35+dfsg-0ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Apr 7 20:17:02 2024 InstallationDate: Installed on 2024-03-25 (13 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240323) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: remmina UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/2060400/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2060391] Re: gnome desktop cannot start as mutter fails to find drmModeCloseFB
** Tags added: regression-release -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2060391 Title: gnome desktop cannot start as mutter fails to find drmModeCloseFB Status in mutter package in Ubuntu: New Bug description: mutter: symbol lookup error: /lib/x86_64-linux-gnu/libmutter-14.so.0: undefined symbol: drmModeCloseFB Package libdrm2: i 2.4.120-2 noble 500 Package libdrm2:i386: i 2.4.120-2 noble 500 Package libmutter-14-0: i 46.0-1ubuntu6 noble 500 Package mutter: i 46.0-1ubuntu6 noble 500 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2060391/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1630931] Re: Wayland turkish language bug
** Changed in: mutter (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1630931 Title: Wayland turkish language bug Status in Kali Linux : Fix Released Status in mutter package in Ubuntu: Fix Released Status in Fedora: Won't Fix Bug description: I can not write any of these letters "ı,I,i,İ" in GNOME Wayland Session. To manage notifications about this bug go to: https://bugs.launchpad.net/kiddomonster/+bug/1630931/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2060391] [NEW] gnome desktop cannot start as mutter fails to find drmModeCloseFB
Public bug reported: mutter: symbol lookup error: /lib/x86_64-linux-gnu/libmutter-14.so.0: undefined symbol: drmModeCloseFB Package libdrm2: i 2.4.120-2 noble 500 Package libdrm2:i386: i 2.4.120-2 noble 500 Package libmutter-14-0: i 46.0-1ubuntu6 noble 500 Package mutter: i 46.0-1ubuntu6 noble 500 ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: noble ** Summary changed: - mutter fails to find drmModeCloseFB + gnome desktop cannot start as mutter fails to find drmModeCloseFB ** Tags removed: regression-release -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2060391 Title: gnome desktop cannot start as mutter fails to find drmModeCloseFB Status in mutter package in Ubuntu: New Bug description: mutter: symbol lookup error: /lib/x86_64-linux-gnu/libmutter-14.so.0: undefined symbol: drmModeCloseFB Package libdrm2: i 2.4.120-2 noble 500 Package libdrm2:i386: i 2.4.120-2 noble 500 Package libmutter-14-0: i 46.0-1ubuntu6 noble 500 Package mutter: i 46.0-1ubuntu6 noble 500 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2060391/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2060390] [NEW] Snapshot No Camera Found
Public bug reported: Start snapshot, I see just a black window with a message: "No camera found" see attachment Note guvcview works fine with this camera ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-snapshot 46.0-1ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Apr 7 17:29:25 2024 ExecutablePath: /usr/bin/snapshot InstallationDate: Installed on 2024-04-07 (0 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240407.2) ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-snapshot UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-snapshot (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble wayland-session ** Attachment added: "Screenshot from 2024-04-07 17-33-49.png" https://bugs.launchpad.net/bugs/2060390/+attachment/5761970/+files/Screenshot%20from%202024-04-07%2017-33-49.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-snapshot in Ubuntu. https://bugs.launchpad.net/bugs/2060390 Title: Snapshot No Camera Found Status in gnome-snapshot package in Ubuntu: New Bug description: Start snapshot, I see just a black window with a message: "No camera found" see attachment Note guvcview works fine with this camera ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-snapshot 46.0-1ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Apr 7 17:29:25 2024 ExecutablePath: /usr/bin/snapshot InstallationDate: Installed on 2024-04-07 (0 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240407.2) ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-snapshot UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-snapshot/+bug/2060390/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2060375] Re: Error appeared when updating Snap on Ubuntu 20
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 2060375 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/2060375 Title: Error appeared when updating Snap on Ubuntu 20 Status in gnome-software package in Ubuntu: New Bug description: see attached screenshot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/2060375/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2058451] Re: CRITICAL: gnome_get_language_from_locale: assertion '*locale != '\0'' failed
This bug does not reproduce on gnome-control-center 1:46.0.1-1ubuntu2. It is believed to have been fixed at some point. ** Changed in: gnome-control-center (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2058451 Title: CRITICAL: gnome_get_language_from_locale: assertion '*locale != '\0'' failed Status in gnome-control-center package in Ubuntu: Incomplete Bug description: On noble, gnome-control-center hangs to open system menu. How to reproduce: * Install Ubuntu 24.04 Desktop without en locale (for example, select Japanese language). * Open System settings app, and select "System" * Click "Region & Language" menu. or you can simplify following command. $ gnome-control-center system Expected result: * Open "Region & Language" menu. Actual result: * Hang up gnome-control-center. --- In this flow, gnome-control-center dumps following errors. $ gnome-control-center system 16:56:12.1249 cc-system-panel[16533]: WARNING: Could not set system time: GDBus.Error:org.freedesktop.timedate1.AutomaticTimeSyncEnabled: Automatic time synchronization is enabled 16:56:12.1252 cc-system-panel[16533]: WARNING: Could not set system time: GDBus.Error:org.freedesktop.timedate1.AutomaticTimeSyncEnabled: Automatic time synchronization is enabled 16:56:12.6869 **[16533]: WARNING: Couldn't get locale for language: en 16:56:12.6871 GnomeDesktop[16533]:CRITICAL: gnome_get_language_from_locale: assertion '*locale != '\0'' failed 16:56:12.7022 **[16533]: WARNING: Couldn't get locale for language: en 16:56:12.7023 GnomeDesktop[16533]:CRITICAL: gnome_get_language_from_locale: assertion '*locale != '\0'' failed My locale is following: $ locale -a C C.utf8 POSIX ja_JP.utf8 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-control-center 1:46~beta-1ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Mar 20 16:56:59 2024 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2024-03-20 (0 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240319) ProcEnviron: LANG=ja_JP.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2058451/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2060350] Re: all windows under gnome shell lack the close, minimize and maximize buttons
I seem to have fixed this, the gnome-session package was missing on my machine (uninstalled by the dependency issue that ensued due to the archive rebuild) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2060350 Title: all windows under gnome shell lack the close, minimize and maximize buttons Status in gnome-shell package in Ubuntu: New Bug description: Using gnome-shell 46 on noble, no window seems to be rendering the close, maximize and minimize buttons. Trying to click in the top right corner to look for buttons that are transparent yielded no result. The buttons seem to not be present at all. I have tried to reinstall gnome-shell-common since a forum post indicates that it contains the assets required to draw those buttons, but it was all in vain. As a workaround I am riht clicking on the window title/headerbars to reveal the context menu with which I can close the window successfully. This seems to be related to the issue where gdm3 is not drawing the login widgets at all (switched to sddm to workaround). ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-shell 46.0-0ubuntu3.1 Uname: Linux 6.8.4-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu Date: Sat Apr 6 11:22:19 2024 DisplayManager: sddm InstallationDate: Installed on 2016-02-19 (2969 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) RelatedPackageVersions: mutter-common 46.0-1ubuntu6 SourcePackage: gnome-shell UpgradeStatus: Upgraded to noble on 2024-03-29 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2060350/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2060384] [NEW] I'm using an external diplay. When disconnecting the HDMI cable, my laptop screen remains dark (when it should actually activate)+
Public bug reported: I normally don't use the laptop screen, as the external display suits me better. However, when I disconnect the HDMI cable (and the external screen is no longer connected), the laptop display should pop back and activate. This doesn't happen - the laptop display remains dark and I have no active display. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Apr 7 14:15:24 2024 DisplayManager: gdm3 InstallationDate: Installed on 2024-02-27 (40 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) RelatedPackageVersions: mutter-common 42.9-0ubuntu7 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2060384 Title: I'm using an external diplay. When disconnecting the HDMI cable, my laptop screen remains dark (when it should actually activate)+ Status in gnome-shell package in Ubuntu: New Bug description: I normally don't use the laptop screen, as the external display suits me better. However, when I disconnect the HDMI cable (and the external screen is no longer connected), the laptop display should pop back and activate. This doesn't happen - the laptop display remains dark and I have no active display. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Apr 7 14:15:24 2024 DisplayManager: gdm3 InstallationDate: Installed on 2024-02-27 (40 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) RelatedPackageVersions: mutter-common 42.9-0ubuntu7 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2060384/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2060375] Re: Error appeared when updating Snap on Ubuntu 20
see also attached log ** Attachment added: "log messages snap update" https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/2060375/+attachment/5761933/+files/log%20messages%20snap%20update -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/2060375 Title: Error appeared when updating Snap on Ubuntu 20 Status in gnome-software package in Ubuntu: New Bug description: see attached screenshot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/2060375/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2060375] [NEW] Error appeared when updating Snap on Ubuntu 20
Public bug reported: see attached screenshot ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Attachment added: "ubuntu-snap-upd-err.png" https://bugs.launchpad.net/bugs/2060375/+attachment/5761930/+files/ubuntu-snap-upd-err.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/2060375 Title: Error appeared when updating Snap on Ubuntu 20 Status in gnome-software package in Ubuntu: New Bug description: see attached screenshot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/2060375/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2057792] Re: Some Games are crashing linked to a vm_max_map_count too low
This bug was fixed in the package procps - 2:4.0.4-4ubuntu3 --- procps (2:4.0.4-4ubuntu3) noble; urgency=medium * No-change rebuild for CVE-2024-3094 -- Steve Langasek Sun, 31 Mar 2024 08:16:00 + ** Changed in: procps (Ubuntu) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-3094 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gamemode in Ubuntu. https://bugs.launchpad.net/bugs/2057792 Title: Some Games are crashing linked to a vm_max_map_count too low Status in gamemode package in Ubuntu: Confirmed Status in linux package in Ubuntu: Won't Fix Status in procps package in Ubuntu: Fix Released Bug description: Hello there, I submit this request to improve the gaming experience in ubuntu for all users. Today, Hogwarts Legacy, Star Citizen and few more games are crashing or just not starting because the vm_max_map_count is locked at 65530. If we change this value to a value > 20, all games are working well and there is no bug linked to maps. Some others distribution like Fedora or Pop OS, have already made the change few month before. It's time to Ubuntu to makes the change also. Thanks in advance for applying this request. How to make this change : One file to modify : /etc/sysctl.conf Add this line : vm.max_map_count=2147483642 Save Reboot and enjoy Best Regards Vinceff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gamemode/+bug/2057792/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
