[Bug 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
John, I think it's worth mentionning this is also breaking usage of MozRegression tool. I think it requires a profile allowing any firefox binary under /tmp for unblocking ... -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to devhelp in Ubuntu. https://bugs.launchpad.net/bugs/2046844 Title: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/2046844/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2065843] Re: mutter crash when unplugging from dock station with monitors
*** This bug is a duplicate of bug 2050865 *** https://bugs.launchpad.net/bugs/2050865 Thanks, when filing bug 2050865 did not show up as a potential dupe. I'll wait for the update, for the moment it looks like disabling Tiling Assistant may be enough to workaround already? At least i dont repro when it is disabled. -- 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/2065843 Title: mutter crash when unplugging from dock station with monitors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2065843/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2065843] [NEW] mutter crash when unplugging from dock station with monitors
Public bug reported: Same setup for years, two 4K monitors on ThinkPad docking station. Right when I unplugged my laptop this morning, GNOME sessions disappeared logs shows: mai 16 06:57:19 portable-alex gnome-shell[4624]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->logical_monitors)' failed mai 16 06:57:19 portable-alex gnome-shell[4624]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed mai 16 06:57:19 portable-alex gnome-shell[4624]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->logical_monitors)' failed mai 16 06:57:19 portable-alex gnome-shell[4624]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed mai 16 06:57:19 portable-alex gnome-shell[4624]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->logical_monitors)' failed mai 16 06:57:19 portable-alex gnome-shell[4624]: ** mai 16 06:57:19 portable-alex gnome-shell[4624]: libmutter:ERROR:../src/core/window.c:5869:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_monitor) mai 16 06:57:19 portable-alex gnome-shell[4624]: Bail out! libmutter:ERROR:../src/core/window.c:5869:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_monitor) mai 16 06:57:19 portable-alex gnome-shell[4624]: GNOME Shell crashed with signal 6 mai 16 06:57:19 portable-alex gnome-shell[4624]: == Stack trace for context 0x604d83def510 == mai 16 06:57:19 portable-alex gnome-shell[4624]: #0 7b6590f0 b file:///usr/share/gnome-shell/extensions/tiling-assist...@ubuntu.com/src/extension/moveHandler.js:503 (22745f4a4e20 @ 454) mai 16 06:57:19 portable-alex gnome-shell[4624]: #1 7b659290 b file:///usr/share/gnome-shell/extensions/tiling-assist...@ubuntu.com/src/extension/moveHandler.js:391 (22745f4a4ba0 @ 1833) mai 16 06:57:19 portable-alex gnome-shell[4624]: #2 604d83eb2818 i resource:///org/gnome/shell/ui/init.js:21 (17c84fd70bf0 @ 48) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-shell 46.0-0ubuntu5.1 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: zen_workaround ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu May 16 07:09:36 2024 DisplayManager: gdm3 InstallationDate: Installed on 2022-07-04 (682 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 46.0-1ubuntu9 SourcePackage: gnome-shell UpgradeStatus: Upgraded to noble on 2024-05-13 (3 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble wayland-session -- 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/2065843 Title: mutter crash when unplugging from dock station with monitors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2065843/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
I am also just wondering how we can effectively work on sandbox-related code on 24.04 ; does it means any developper (and potentially CI) will have to setup its AppArmor profile **also** matching the builds to have proper userns ? The way it is currently handled, I dont see any other way around, but it also means it needs to be done for any objdir we work on ? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to devhelp in Ubuntu. https://bugs.launchpad.net/bugs/2046844 Title: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/2046844/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
Yep, this is fine. I just wanted to make it clear for others, because one of the comment above might be misleading and even though I know the area of the code impacted by userns, I was actually thinking you got a fix landed on AppArmor side to avoid the need for a dedicated profile. AppImage being impacted might also be good to report to those upstream? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to devhelp in Ubuntu. https://bugs.launchpad.net/bugs/2046844 Title: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/2046844/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
I have just upgraded to 24.04 from 23.10 and I'd like to emphasize that
for the Firefox case, the comments on that thread mentions "AppArmor
should fix it with beta3" is inaccurate and incomplete: it only
partially fixes the issue since it only covers packaged versions.
Anybody relying on the tarball should have something similar (assuming you
install in $HOME/bin/firefox)
> $ cat /etc/apparmor.d/firefox-bin
> # This profile allows everything and only exists to give the
> # application a name instead of having the label "unconfined"
>
> abi ,
> include
>
> profile firefox /home/XXX/bin/firefox/firefox flags=(unconfined) {
> userns,
>
> # Site-specific additions and overrides. See local/README for details.
> include if exists
> }
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to devhelp in Ubuntu.
https://bugs.launchpad.net/bugs/2046844
Title:
AppArmor user namespace creation restrictions cause many applications
to crash with SIGTRAP
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/2046844/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2045632] Re: gnome-shell libmozjs g_closure_unref: assertion closure->ref_count > 0 failed
The only extensions installed are: > $ gnome-extensions list > lockk...@vaina.lt > d...@rastersoft.com > ubuntu-appindicat...@ubuntu.com > ubuntu-d...@ubuntu.com > tiling-assist...@ubuntu.com -- 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/2045632 Title: gnome-shell libmozjs g_closure_unref: assertion closure->ref_count > 0 failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2045632/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2045632] Re: gnome-shell libmozjs g_closure_unref: assertion closure->ref_count > 0 failed
** Attachment added: "prevjournal.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2045632/+attachment/5726373/+files/prevjournal.txt -- 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/2045632 Title: gnome-shell libmozjs g_closure_unref: assertion closure->ref_count > 0 failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2045632/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2045632] Re: gnome-shell libmozjs g_closure_unref: assertion closure->ref_count > 0 failed
Lots of crashes on https://errors.ubuntu.com/user/a5880f5d67200136401b48e606e90173fb34300b11a89ca2507124cd0b5a044b7751eefba0fc9f16b27183bed1a11134c74d956b2b7161ee37aa1ee5d1d5c8ed The one we are interested in is https://errors.ubuntu.com/oops/ad78e2e9-9344-11ee-8949-fa163ec8ca8c but I'm not able to access to its content. -- 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/2045632 Title: gnome-shell libmozjs g_closure_unref: assertion closure->ref_count > 0 failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2045632/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2045632] Re: gnome-shell libmozjs g_closure_unref: assertion closure->ref_count > 0 failed
** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2045632/+attachment/5726374/+files/journal.txt -- 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/2045632 Title: gnome-shell libmozjs g_closure_unref: assertion closure->ref_count > 0 failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2045632/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2045632] Re: gnome-shell libmozjs g_closure_unref: assertion closure->ref_count > 0 failed
it was uploaded already but I dont know where: > $ sudo cat /var/crash/_usr_bin_gnome-shell.1000.uploaded > ad78e2e9-9344-11ee-8949-fa163ec8ca8c -- 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/2045632 Title: gnome-shell libmozjs g_closure_unref: assertion closure->ref_count > 0 failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2045632/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2045632] [NEW] gnome-shell libmozjs g_closure_unref: assertion closure->ref_count > 0 failed
Public bug reported: While just using my system, GNOME Shell suddenly disappeared and logs shows: déc. 05 09:02:23 portable-alex gnome-shell[4341]: g_closure_unref: assertion 'closure->ref_count > 0' failed déc. 05 09:02:23 portable-alex gnome-shell[4341]: GNOME Shell crashed with signal 11 déc. 05 09:02:23 portable-alex gnome-shell[4341]: == Stack trace for context 0x55996924e410 == déc. 05 09:02:23 portable-alex kernel: traps: JS Helper[4367] general protection fault ip:7fe24f05d21c sp:7fe2339fec80 error:0 in libmozjs-115.so.115.3.0[7fe24ef18000+b73000] ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.1-0ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-13.13-generic 6.5.3 Uname: Linux 6.5.0-13-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Dec 5 09:08:03 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-07-04 (519 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45.0-3ubuntu3.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to mantic on 2023-10-16 (50 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic wayland-session -- 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/2045632 Title: gnome-shell libmozjs g_closure_unref: assertion closure->ref_count > 0 failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2045632/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland
** Tags removed: verification-needed verification-needed-mantic ** Tags added: verification-done-mantic -- 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/2034619 Title: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2034619/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland
Enabled proposed repo on 23.10 ``` $ $ sudo apt install -t mantic-proposed mutter Lecture des listes de paquets... Fait Construction de l'arbre des dépendances... Fait Lecture des informations d'état... Fait Le paquet suivant a été installé automatiquement et n'est plus nécessaire : libjs-jquery-ui-theme-base Veuillez utiliser « sudo apt autoremove » pour le supprimer. Les paquets supplémentaires suivants seront installés : gir1.2-mutter-13 libmutter-13-0 mutter-common mutter-common-bin Les NOUVEAUX paquets suivants seront installés : mutter Les paquets suivants seront mis à jour : gir1.2-mutter-13 libmutter-13-0 mutter-common mutter-common-bin 4 mis à jour, 1 nouvellement installés, 0 à enlever et 26 non mis à jour. Il est nécessaire de prendre 1 727 ko dans les archives. Après cette opération, 205 ko d'espace disque supplémentaires seront utilisés. Souhaitez-vous continuer ? [O/n] Réception de :1 http://fr.archive.ubuntu.com/ubuntu mantic-proposed/main amd64 mutter-common all 45.0-3ubuntu3.1 [45,5 kB] Réception de :2 http://fr.archive.ubuntu.com/ubuntu mantic-proposed/main amd64 gir1.2-mutter-13 amd64 45.0-3ubuntu3.1 [130 kB] Réception de :3 http://fr.archive.ubuntu.com/ubuntu mantic-proposed/main amd64 libmutter-13-0 amd64 45.0-3ubuntu3.1 [1 391 kB] Réception de :4 http://fr.archive.ubuntu.com/ubuntu mantic-proposed/main amd64 mutter-common-bin amd64 45.0-3ubuntu3.1 [49,3 kB] Réception de :5 http://fr.archive.ubuntu.com/ubuntu mantic-proposed/universe amd64 mutter amd64 45.0-3ubuntu3.1 [111 kB] 1 727 ko réceptionnés en 0s (7 132 ko/s) (Lecture de la base de données... 313559 fichiers et répertoires déjà installés.) Préparation du dépaquetage de .../mutter-common_45.0-3ubuntu3.1_all.deb ... Dépaquetage de mutter-common (45.0-3ubuntu3.1) sur (45.0-3ubuntu3) ... Préparation du dépaquetage de .../gir1.2-mutter-13_45.0-3ubuntu3.1_amd64.deb ... Dépaquetage de gir1.2-mutter-13:amd64 (45.0-3ubuntu3.1) sur (45.0-3ubuntu3) ... Préparation du dépaquetage de .../libmutter-13-0_45.0-3ubuntu3.1_amd64.deb ... Dépaquetage de libmutter-13-0:amd64 (45.0-3ubuntu3.1) sur (45.0-3ubuntu3) ... Préparation du dépaquetage de .../mutter-common-bin_45.0-3ubuntu3.1_amd64.deb ... Dépaquetage de mutter-common-bin (45.0-3ubuntu3.1) sur (45.0-3ubuntu3) ... Sélection du paquet mutter précédemment désélectionné. Préparation du dépaquetage de .../mutter_45.0-3ubuntu3.1_amd64.deb ... Dépaquetage de mutter (45.0-3ubuntu3.1) ... Paramétrage de mutter-common (45.0-3ubuntu3.1) ... Paramétrage de mutter-common-bin (45.0-3ubuntu3.1) ... Traitement des actions différées (« triggers ») pour libglib2.0-0:amd64 (2.78.0-2) ... Traitement des actions différées (« triggers ») pour libglib2.0-0:i386 (2.78.0-2) ... Traitement des actions différées (« triggers ») pour libc-bin (2.38-1ubuntu6) ... Traitement des actions différées (« triggers ») pour man-db (2.11.2-3) ... Paramétrage de libmutter-13-0:amd64 (45.0-3ubuntu3.1) ... Paramétrage de mutter (45.0-3ubuntu3.1) ... update-alternatives: utilisation de « /usr/bin/mutter » pour fournir « /usr/bin/x-window-manager » (x-window-manager) en mode automatique Paramétrage de gir1.2-mutter-13:amd64 (45.0-3ubuntu3.1) ... Traitement des actions différées (« triggers ») pour libc-bin (2.38-1ubuntu6) ... ``` Closed GNOME session, reopened it, unplugged from dock, force lock screen, and I cannot reproduce the problem anymore. -- 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/2034619 Title: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2034619/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2039958] Re: gnome-shell session dies when locking laptop screen
dupe of https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2034619 ? -- 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/2039958 Title: gnome-shell session dies when locking laptop screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2039958/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2039958] Re: gnome-shell session dies when locking laptop screen
Disabling all extensions does not help -- 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/2039958 Title: gnome-shell session dies when locking laptop screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2039958/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2039958] [NEW] gnome-shell session dies when locking laptop screen
Public bug reported: Started after migrating to 23.10 STR: - Boot laptop - Login - Start GNOME Terminal - Lock screen Expected: - Screen is locked, I can unlock and recover my session Actual: - Screen gets locked, does not unlock, and ends up starting a new gnome session This only reproduces in the simple case of laptop with its integrated screen being used. When I connect to my docking station, with two external monitors and the internal screen disabled, I can properly perform the locking/unlocking. journalctl does not show anything useful besides: oct. 20 11:40:13 portable-alex kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 oct. 20 11:40:18 portable-alex gnome-shell[27866]: (EE) failed to read Wayland events: Broken pipe oct. 20 11:40:18 portable-alex update-notifier[28393]: Error reading events from display: Relais brisé (pipe) oct. 20 11:40:18 portable-alex vorta.desktop[27371]: The Wayland connection broke. Did the Wayland compositor die? oct. 20 11:40:18 portable-alex xdg-desktop-por[26680]: Error reading events from display: Relais brisé (pipe) oct. 20 11:40:18 portable-alex snapd-desktop-i[26606]: Error reading events from display: Broken pipe oct. 20 11:40:18 portable-alex solaar[26327]: Error reading events from display: Relais brisé (pipe) oct. 20 11:40:18 portable-alex evolution-alarm[26356]: Error reading events from display: Relais brisé (pipe) oct. 20 11:40:18 portable-alex xdg-desktop-por[26746]: Error reading events from display: Relais brisé (pipe) oct. 20 11:40:18 portable-alex vorta[27371]: Error reading events from display: Relais brisé (pipe) oct. 20 11:40:18 portable-alex gsd-wacom[26213]: Error reading events from display: Relais brisé (pipe) oct. 20 11:40:18 portable-alex gsd-color[26168]: Error reading events from display: Relais brisé (pipe) oct. 20 11:40:18 portable-alex gsd-power[26183]: Error reading events from display: Relais brisé (pipe) oct. 20 11:40:18 portable-alex gsd-keyboard[26178]: Error reading events from display: Relais brisé (pipe) oct. 20 11:40:18 portable-alex gnome-terminal-[27151]: Error reading events from display: Relais brisé (pipe) oct. 20 11:40:18 portable-alex gsd-media-keys[26180]: Error reading events from display: Relais brisé (pipe) oct. 20 11:40:18 portable-alex systemd[3731]: org.gnome.SettingsDaemon.Color.service: Main process exited, code=exited, status=1/FAILURE ░░ Subject: Unit process exited ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ An ExecStart= process belonging to unit UNIT has exited. ░░ ░░ The process' exit code is 'exited' and its exit status is 1. oct. 20 11:40:18 portable-alex sudo[28424]: pam_unix(sudo:session): session closed for user root oct. 20 11:40:18 portable-alex io.github.Hexchat.desktop[27864]: hexchat: Fatal IO error 11 (Ressource temporairement non disponible) on X server :0. oct. 20 11:40:18 portable-alex systemd[3731]: org.gnome.Shell@wayland.service: Main process exited, code=killed, status=9/KILL ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Oct 20 12:03:36 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-07-04 (473 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 45.0-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to mantic on 2023-10-16 (4 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic wayland-session -- 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/2039958 Title: gnome-shell session dies when locking laptop screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2039958/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2020672] Re: Focus constantly moves to the secondary screen upon workspace switch
~~Just upgraded my laptop to 23.10 release, and I can confirm the issue is STILL present. This is NOT fixed.~~ It is indeed fixed, I am now facing bug 1969598, since running `gnome- extensions disable d...@rastersoft.com` helps. -- 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/2020672 Title: Focus constantly moves to the secondary screen upon workspace switch To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2020672/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2020672] Re: Focus constantly moves to the secondary screen upon workspace switch
Do you know if it's part of the lunar-updates 44.2-0ubuntu1 ? Looking at the changelog it's not clear to me. -- 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/2020672 Title: Focus constantly moves to the secondary screen upon workspace switch To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2020672/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2020672] Re: Focus constantly moves to the secondary screen upon workspace switch
Has upstream just reverted the offending change? https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2909 -- 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/2020672 Title: Focus constantly moves to the secondary screen upon workspace switch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2020672/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2020672] Re: Focus constantly moves to the secondary screen upon workspace switch
Disabling this extension and logging out / logging back in, I still have the problem -- 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/2020672 Title: Focus constantly moves to the secondary screen upon workspace switch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2020672/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2020672] Re: Focus constantly moves to the secondary screen upon workspace switch
Thanks, I just tried and for now it does not help. The other bug mentions one might need to restart the session which I can't do at the moment but will try later. -- 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/2020672 Title: Focus constantly moves to the secondary screen upon workspace switch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2020672/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2020672] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2020672/+attachment/5675434/+files/ProcCpuinfoMinimal.txt -- 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/2020672 Title: Focus constantly moves to the secondary screen upon workspace switch To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2020672/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2020672] Re: Focus constantly moves to the secondary screen upon workspace switch
apport information ** Tags added: apport-collected lunar wayland-session ** Description changed: I have two screen, side by side, with IDs (2) and (3) ; physically and within GNOME Control Center, the setup is as is: [ (3) ][ (2) ] The Screen with identifier (2) is defined as the main screen. My multiscreen setup in GNOME Control Center is: - Fixed number of workspace (12) - Workspaces only on main screen The issue is that whenever I move from one workspace to the other (using keyboard shortcuts CTRL+ALT+(<-|->), the system gives focus to the secondary screen, identifier (3) above. This is really super painful on a day-to-day basis because I spend half of my time fixing the focus and/or inputing in the wrong window. It already made me loose valuable work because of a CTRL+C in the wrong window. As much as I can recall, this was not the behavior in previous releases. + --- + ProblemType: Bug + ApportVersion: 2.26.1-0ubuntu2 + Architecture: amd64 + CasperMD5CheckResult: pass + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 23.04 + InstallationDate: Installed on 2022-07-04 (324 days ago) + InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) + NonfreeKernelModules: zen_workaround + Package: libmutter-12-0 44.0-2ubuntu4 + PackageArchitecture: amd64 + ProcEnviron: + LANG=fr_FR.UTF-8 + PATH=(custom, no user) + SHELL=/bin/bash + TERM=xterm-256color + XDG_RUNTIME_DIR= + ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 + RebootRequiredPkgs: Error: path contained symlinks. + Tags: lunar wayland-session + Uname: Linux 6.2.0-20-generic x86_64 + UpgradeStatus: Upgraded to lunar on 2023-04-21 (33 days ago) + UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/2020672/+attachment/5675433/+files/Dependencies.txt -- 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/2020672 Title: Focus constantly moves to the secondary screen upon workspace switch To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2020672/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2020672] [NEW] Focus constantly moves to the secondary screen upon workspace switch
Public bug reported: I have two screen, side by side, with IDs (2) and (3) ; physically and within GNOME Control Center, the setup is as is: [ (3) ][ (2) ] The Screen with identifier (2) is defined as the main screen. My multiscreen setup in GNOME Control Center is: - Fixed number of workspace (12) - Workspaces only on main screen The issue is that whenever I move from one workspace to the other (using keyboard shortcuts CTRL+ALT+(<-|->), the system gives focus to the secondary screen, identifier (3) above. This is really super painful on a day-to-day basis because I spend half of my time fixing the focus and/or inputing in the wrong window. It already made me loose valuable work because of a CTRL+C in the wrong window. As much as I can recall, this was not the behavior in previous releases. ** Affects: mutter Importance: Unknown Status: Unknown ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Focus constantly moves to the secondary screen upon desktop switch + Focus constantly moves to the secondary screen upon workspace switch ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #2548 https://gitlab.gnome.org/GNOME/mutter/-/issues/2548 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/-/issues/2548 Importance: Unknown Status: Unknown -- 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/2020672 Title: Focus constantly moves to the secondary screen upon workspace switch To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2020672/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2020672] Re: Focus constantly moves to the secondary screen upon workspace switch
Would it have been fixed by https://gitlab.gnome.org/GNOME/mutter/-/commit/0d69fabbe6895fdac31e044060ed16bd1f1c344a ? -- 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/2020672 Title: Focus constantly moves to the secondary screen upon workspace switch To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2020672/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2020655] [NEW] XDG Desktop Portal should show "nice" user path
Public bug reported: Users hould not see "/run/xxx" but rather e.g., "/tmp/" ** Affects: firefox-snap Importance: Unknown Status: Unknown ** Affects: xdg-desktop-portal Importance: Unknown Status: Unknown ** Affects: xdg-desktop-portal (Ubuntu) Importance: Undecided Status: New ** Bug watch added: github.com/flatpak/xdg-desktop-portal/issues #973 https://github.com/flatpak/xdg-desktop-portal/issues/973 ** Also affects: xdg-desktop-portal via https://github.com/flatpak/xdg-desktop-portal/issues/973 Importance: Unknown Status: Unknown ** Bug watch added: Mozilla Bugzilla #1775497 https://bugzilla.mozilla.org/show_bug.cgi?id=1775497 ** Also affects: firefox-snap via https://bugzilla.mozilla.org/show_bug.cgi?id=1775497 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to xdg-desktop-portal in Ubuntu. https://bugs.launchpad.net/bugs/2020655 Title: XDG Desktop Portal should show "nice" user path To manage notifications about this bug go to: https://bugs.launchpad.net/firefox-snap/+bug/2020655/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968929] Re: No Wayland support on my NVIDA laptop
While this might sound as fishy, I hit the same problem, but my laptop
is NOT with NVIDIA hardware ; it's a ThinkPad P14s Gen 2 AMD, with an
AMD GPU. I had to reboot over the last few days and got no issue, until
I rebooted one hour ago and got stuck on X11 instead of Wayland. After I
found about that bug report and commented around the lines mentionned in
comment #4, I could get back Wayland working.
Specifically, those:
> Check if suspend/resume services necessary for working wayland support
> is available
> ###TEST{0711}!="/usr/bin/nvidia-sleep.sh", GOTO="gdm_disable_wayland"
> ###TEST{0711}!="/usr/lib/systemd/system-sleep/nvidia",
> GOTO="gdm_disable_wayland"
> ###IMPORT{program}="/bin/sh -c \"sed -e 's/: /=/g' -e
> 's/\([^[:upper:]]\)\([[:upper:]]\)/\1_\2/g' -e 's/[[:lower:]]/\U&/g' -e
> 's/^/NVIDIA_/' /proc/driver/nvidia/params\""
> ###ENV{NVIDIA_PRESERVE_VIDEO_MEMORY_ALLOCATIONS}!="1",
> GOTO="gdm_disable_wayland"
> ###IMPORT{program}="/bin/sh -c 'echo NVIDIA_HIBERNATE=`systemctl is-enabled
> nvidia-hibernate`'"
> ###ENV{NVIDIA_HIBERNATE}!="enabled", GOTO="gdm_disable_wayland"
> ###IMPORT{program}="/bin/sh -c 'echo NVIDIA_RESUME=`systemctl is-enabled
> nvidia-resume`'"
> ###ENV{NVIDIA_RESUME}!="enabled", GOTO="gdm_disable_wayland"
> ###IMPORT{program}="/bin/sh -c 'echo NVIDIA_SUSPEND=`systemctl is-enabled
> nvidia-suspend`'"
> ###ENV{NVIDIA_SUSPEND}!="enabled", GOTO="gdm_disable_wayland"
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1968929
Title:
No Wayland support on my NVIDA laptop
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1968929/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1665394] [NEW] DNS resolution of irc.freenode.net or chat.freenode.net fails
Public bug reported: I am running Ubuntu 16.10 (from a base install upgraded several times), with proposed-updates enabled. Recently, I started having problems where I am unable to resolve irc.freenode.net. This is unrelated to the networks. I have been able to confirm that systemd-resolved is able to perform the name resolution. Yet, getaddrinfo() call returns -EAI_AGAIN error. This can be reproduced using getent: > $ getent ahosts irc.freenode.net > $ While testing v4 or v6 directly returns something valid: > $ getent ahostsv4 irc.freenode.net > 38.229.70.22STREAM chat.freenode.net > 38.229.70.22DGRAM > 38.229.70.22RAW > 130.239.18.119 STREAM > 130.239.18.119 DGRAM > 130.239.18.119 RAW [...] > $ > $ getent ahostsv6 irc.freenode.net > 2001:5a0:3604:1:64:86:243:181 STREAM chat.freenode.net > 2001:5a0:3604:1:64:86:243:181 DGRAM > 2001:5a0:3604:1:64:86:243:181 RAW > 2001:6b0:e:2a18::118 STREAM > 2001:6b0:e:2a18::118 DGRAM > 2001:6b0:e:2a18::118 RAW [...] > $ dpkg.log shows there has been some upgrade of systemd recently, though I cannot tell for sure if that directly relates to the problem, I do use suspend-to-ram a lot and reboot not that often. > $ lsb_release -a > LSB Version: > core-9.20160110ubuntu5-amd64:core-9.20160110ubuntu5-noarch:printing-9.20160110ubuntu5-amd64:printing-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9.20160110ubuntu5-noarch > Distributor ID: Ubuntu > Description: Ubuntu 16.10 > Release: 16.10 > Codename: yakkety ** Affects: systemd (Ubuntu) Importance: Undecided Status: Confirmed ** Package changed: glibc (Ubuntu) => systemd (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1665394 Title: DNS resolution of irc.freenode.net or chat.freenode.net fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1665394/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
