[Bug 1959888] Re: Wayland sessions can't use external monitors that are connected to an Nvidia GPU with the proprietary driver
** Changed in: mutter (Ubuntu) Status: Triaged => In Progress -- 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/1959888 Title: Wayland sessions can't use external monitors that are connected to an Nvidia GPU with the proprietary driver To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1959888/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1959888] Re: Wayland sessions can't use external monitors that are connected to an Nvidia GPU with the proprietary driver
Bug confirmed with Nvidia-510. External monitors connected to the secondary (Nvidia) GPU never light up in Wayland sessions. Also my log is full of: clutter_frame_clock_notify_presented: code should not be reached ** Changed in: mutter (Ubuntu) Status: Incomplete => Confirmed ** Changed in: mutter (Ubuntu) Status: Confirmed => Triaged -- 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/1959888 Title: Wayland sessions can't use external monitors that are connected to an Nvidia GPU with the proprietary driver To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1959888/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1963701] Re: [NVIDIA][Wayland] graphic target not able to reach as the only monitor connect to NV GPU only on I+N machine
Hi Daniel, yes, in hybrid system, different BIOS have their own way to configure it. We just need to make sure the memory point of efifb passed from BIOS is correct one and it's correct in this case, the boot_vga is dGPU. I'll risk this issue on upstream to discuss and share the upstream bug here. -- 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/1963701 Title: [NVIDIA][Wayland] graphic target not able to reach as the only monitor connect to NV GPU only on I+N machine To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1963701/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1964560] Re: file transfers have trouble finishing
Flash drives are usually very slow devices. Next time a transfer has trouble finishing please open a Terminal window and run: sync If the command returns immediately then this is a Nautilus bug. If the command does not return until the file transfer finishes then this is either a kernel bug or just the slowness of the flash drive. ** Package changed: wayland (Ubuntu) => nautilus (Ubuntu) ** Tags added: impish ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Changed in: nautilus (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1964560 Title: file transfers have trouble finishing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964560/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1964560] [NEW] file transfers have trouble finishing
You have been subscribed to a public bug: Ubuntu 21.10 with wayland windowing system sits on completed file transfers on and off usb and takes its time realising its finished and closing the little transfer progress logo. running an HP elitedesk 800 G1 SFF with 16gb ram, i5 4690 cpu and an HD 4600 onboard graphics card. It's either the linux system or old flash drives causing it. Don't think its the circuit boards. ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New -- file transfers have trouble finishing https://bugs.launchpad.net/bugs/1964560 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1964496] Re: [GS 42] display switching key does not work
Note to everyone else: A lot of machines don't have a display switching key. It is sometimes Fn+F8 or Fn+F7. ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Low -- 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/1964496 Title: [GS 42] display switching key does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964496/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1956390] Re: User profile picture color not selected until you unlock and click on the letter.
[Expired for gnome-control-center (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-control-center (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1956390 Title: User profile picture color not selected until you unlock and click on the letter. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1956390/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1964539] Re: 42beta: screen unlock gets stuck on primary display, secondary display is unlocked
Please still follow the steps in comments #2 and #3. Although something else stands out - that you're using the nouveau kernel driver. Nouveau is prolific for kernel crashes, freezes, and other bugs. So ideally please use the 'Additional Drivers' app to install a proprietary Nvidia driver instead. ** Tags added: nouveau -- 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/1964539 Title: 42beta: screen unlock gets stuck on primary display, secondary display is unlocked To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964539/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1964545] Re: 42beta: moving mouse as screen is fading to screensaver prevents input to shell
See also bug 1181666, although that's probably a different issue if it is still an issue at all. -- 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/1964545 Title: 42beta: moving mouse as screen is fading to screensaver prevents input to shell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964545/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1964554] Re: Brasero does not burn ISO IMAGE. Error message; "SCSI error on write(0,16): See MMC specs: Sense Key 5 "Illegal request"
apport information ** Tags added: apport-collected bionic ** Description changed: BraseroLibburn SCSI error condition on command 2Ah WRITE(10): See MMC specs: Sense Key 5 "Illegal request", ASC 21 ASCQ 04. BraseroLibburn called brasero_job_set_current_action BraseroLibburn Libburn reported an error SCSI error on write(0,16): See MMC specs: Sense Key 5 "Illegal request", ASC 21 ASCQ 04. BraseroLibburn called brasero_job_error BraseroLibburn finished with an error BraseroLibburn asked to stop because of an error error = 1 message = "SCSI error on write(0,16): See MMC specs: Sense Key 5 "Illegal request", ASC 21 ASCQ 04." BraseroLibburn stopping Session error : SCSI error on write(0,16): See MMC specs: Sense Key 5 "Illegal request", ASC 21 ASCQ 04. (brasero_burn_record brasero-burn.c:2856) + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.27 + Architecture: amd64 + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2021-01-31 (403 days ago) + InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) + Package: brasero 3.12.1-4ubuntu2 + PackageArchitecture: amd64 + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 5.4.0-100.113~18.04.1-generic 5.4.166 + Tags: bionic + Uname: Linux 5.4.0-100-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1964554/+attachment/5567877/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to brasero in Ubuntu. https://bugs.launchpad.net/bugs/1964554 Title: Brasero does not burn ISO IMAGE. Error message; "SCSI error on write(0,16): See MMC specs: Sense Key 5 "Illegal request" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/1964554/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1964554] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1964554/+attachment/5567878/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to brasero in Ubuntu. https://bugs.launchpad.net/bugs/1964554 Title: Brasero does not burn ISO IMAGE. Error message; "SCSI error on write(0,16): See MMC specs: Sense Key 5 "Illegal request" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/1964554/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1964554] [NEW] Brasero does not burn ISO IMAGE. Error message; "SCSI error on write(0,16): See MMC specs: Sense Key 5 "Illegal request"
Public bug reported: BraseroLibburn SCSI error condition on command 2Ah WRITE(10): See MMC specs: Sense Key 5 "Illegal request", ASC 21 ASCQ 04. BraseroLibburn called brasero_job_set_current_action BraseroLibburn Libburn reported an error SCSI error on write(0,16): See MMC specs: Sense Key 5 "Illegal request", ASC 21 ASCQ 04. BraseroLibburn called brasero_job_error BraseroLibburn finished with an error BraseroLibburn asked to stop because of an error error = 1 message = "SCSI error on write(0,16): See MMC specs: Sense Key 5 "Illegal request", ASC 21 ASCQ 04." BraseroLibburn stopping Session error : SCSI error on write(0,16): See MMC specs: Sense Key 5 "Illegal request", ASC 21 ASCQ 04. (brasero_burn_record brasero-burn.c:2856) ** Affects: brasero (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to brasero in Ubuntu. https://bugs.launchpad.net/bugs/1964554 Title: Brasero does not burn ISO IMAGE. Error message; "SCSI error on write(0,16): See MMC specs: Sense Key 5 "Illegal request" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/1964554/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1964136] Re: Settings item not shown in System menu
Hi Jeremy, Sorry, I should have rebooted first. The settings link is there and it works. Happy to say verified. -- 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/1964136 Title: Settings item not shown in System menu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1964136/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1964539] monitors.xml.txt
apport information ** Attachment added: "monitors.xml.txt" https://bugs.launchpad.net/bugs/1964539/+attachment/5567874/+files/monitors.xml.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/1964539 Title: 42beta: screen unlock gets stuck on primary display, secondary display is unlocked To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964539/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1964539] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1964539/+attachment/5567871/+files/ProcCpuinfoMinimal.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/1964539 Title: 42beta: screen unlock gets stuck on primary display, secondary display is unlocked To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964539/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1964539] ShellJournal.txt
apport information ** Attachment added: "ShellJournal.txt" https://bugs.launchpad.net/bugs/1964539/+attachment/5567873/+files/ShellJournal.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/1964539 Title: 42beta: screen unlock gets stuck on primary display, secondary display is unlocked To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964539/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1964539] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/1964539/+attachment/5567870/+files/GsettingsChanges.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/1964539 Title: 42beta: screen unlock gets stuck on primary display, secondary display is unlocked To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964539/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1964539] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1964539/+attachment/5567872/+files/ProcEnviron.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/1964539 Title: 42beta: screen unlock gets stuck on primary display, secondary display is unlocked To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964539/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1964539] Re: 42beta: screen unlock gets stuck on primary display, secondary display is unlocked
apport information ** Tags added: apport-collected package-from-proposed third-party- packages wayland-session ** Description changed: [Impact] Occasionally, when the screen has been locked for a medium length of time, > 5 mins, when you press the spacebar, enter your password, the primary display freezes and the lockscreen slider does not slide up. The secondary screen is fine, and unlocks. See screenshot for what it looks like. You can click, interact with the secondary screen. On the primary screen, you can super key and launch an application, but you won't be able to interact with it. You can't see what you are doing. The way to fix is to re-lock the screen, wait a bit, and attempt to unlock. Sometimes you won't be able to unlock immediately, as it is difficult to get the monitor to power on again, it appears gnome-shell does not send the wakeup signal. gnome-shell 42~beta-1ubuntu2 from -proposed. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu78 + Architecture: amd64 + CasperMD5CheckResult: pass + CurrentDesktop: ubuntu:GNOME + DisplayManager: gdm3 + DistroRelease: Ubuntu 22.04 + InstallationDate: Installed on 2022-01-02 (68 days ago) + InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220101) + Package: gnome-shell + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 + RelatedPackageVersions: mutter-common 42~beta-1ubuntu1 + Tags: wayland-session third-party-packages jammy package-from-proposed + Uname: Linux 5.15.0-22-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1964539/+attachment/5567869/+files/Dependencies.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/1964539 Title: 42beta: screen unlock gets stuck on primary display, secondary display is unlocked To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964539/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1964539] Re: 42beta: screen unlock gets stuck on primary display, secondary display is unlocked
Next time the problem happens please immediately run: journalctl -b0 journal.txt and attach the resulting text file here. ** Tags added: multimonitor -- 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/1964539 Title: 42beta: screen unlock gets stuck on primary display, secondary display is unlocked To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964539/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1964539] Re: 42beta: screen unlock gets stuck on primary display, secondary display is unlocked
Please try adding this to /etc/environment: MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 and then reboot. Also... 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 1964539 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. ** Changed in: gnome-shell (Ubuntu Jammy) Status: New => Incomplete -- 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/1964539 Title: 42beta: screen unlock gets stuck on primary display, secondary display is unlocked To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964539/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1964496] Re: [GS 42] display switching key does not work
** Tags added: jammy -- 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/1964496 Title: [GS 42] display switching key does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964496/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1964136] Re: Settings item not shown in System menu
Matthew, yes, the missing Settings link was basically an Ubuntu packaging bug and is fixed with https://launchpad.net/ubuntu/+source/gnome-shell/42~beta-1ubuntu2 I believe you would need to log out and log back in after installing that update. -- 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/1964136 Title: Settings item not shown in System menu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1964136/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1964296] Re: No desktop icons visible even though DING is enabled
Looks like it only fails in Xorg sessions. If you log into a Wayland session then the icons appear. ** Also affects: gjs (Ubuntu) Importance: Undecided Status: New ** Changed in: gjs (Ubuntu) Status: New => Confirmed ** Changed in: gjs (Ubuntu) Importance: Undecided => High ** Changed in: gnome-shell-extension-desktop-icons-ng (Ubuntu) Milestone: None => ubuntu-22.04-beta ** Changed in: gjs (Ubuntu) Milestone: None => ubuntu-22.04-beta ** Tags added: rls-jj-incoming ** Summary changed: - No desktop icons visible even though DING is enabled + No desktop icons in Xorg sessions -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1964296 Title: No desktop icons in Xorg sessions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1964296/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1964393] Re: gnome-shell crashed with assertion failure in meta_kms_update_set_power_save: !update->plane_assignments
This is definitely a bug in mutter (gnome-shell). Other people reported it to me in recent months per comment #3. ** Changed in: gnome-shell (Ubuntu) Status: Invalid => Confirmed ** Information type changed from Private to Public ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu) Status: New => Confirmed -- 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/1964393 Title: gnome-shell crashed with assertion failure in meta_kms_update_set_power_save: !update->plane_assignments To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964393/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1964541] Re: 42beta: Cannot re-arrange Firefox browser tabs
** Also affects: firefox (Ubuntu) Importance: Undecided Status: New ** No longer affects: gnome-shell (Ubuntu) ** No longer affects: gnome-shell (Ubuntu Jammy) -- 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/1964541 Title: 42beta: Cannot re-arrange Firefox browser tabs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1964541/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1964136] Re: Settings item not shown in System menu
Just to clarify, we will be adding the option to launch gnome-control- center from the system menu? I keep finding myself trying to launch it from there to check sound settings before meetings, but it is missing, and have to launch from overview instead. I think this is a feature that LTS users will want. -- 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/1964136 Title: Settings item not shown in System menu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1964136/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1964539] Re: 42beta: screen unlock gets stuck on primary display, secondary display is unlocked
** Also affects: gnome-shell (Ubuntu Jammy) Importance: Undecided Status: New ** Tags added: jammy -- 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/1964539 Title: 42beta: screen unlock gets stuck on primary display, secondary display is unlocked To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964539/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1964541] Re: 42beta: Cannot re-arrange Firefox browser tabs
** Also affects: gnome-shell (Ubuntu Jammy) Importance: Undecided Status: New ** Tags added: jammy -- 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/1964541 Title: 42beta: Cannot re-arrange Firefox browser tabs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964541/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1964545] [NEW] 42beta: moving mouse as screen is fading to screensaver prevents input to shell
Public bug reported: [Impact] If you move the mouse as the system fades into black for the screensaver, the screensaver will be prevented as normal, but the user will not be able to interact with the shell. Mouse clicks are ignored, and most key presses are ignored too. Workaround is to press super to enter shell overview, then super again to close, and mouse clicks will begin working again. gnome-shell 42~beta-1ubuntu2 from -proposed. [Testcase] 1) Leave your system idle, until the screen starts fading to black 2) As the screen is fading to black, move the mouse to prevent screensaver. 3) Attempt to click any window or type something ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Affects: gnome-shell (Ubuntu Jammy) Importance: Undecided Status: New ** Tags: jammy ** Description changed: [Impact] If you move the mouse as the system fades into black for the screensaver, the screensaver will be prevented as normal, but the user will not be able to interact with the shell. Mouse clicks are ignored, and most key presses are ignored too. Workaround is to press super to enter shell overview, then super again to close, and mouse clicks will begin working again. gnome-shell 42~beta-1ubuntu2 from -proposed. - [Testase] + [Testcase] 1) Leave your system idle, until the screen starts fading to black 2) As the screen is fading to black, move the mouse to prevent screensaver. 3) Attempt to click any window or type something ** Also affects: gnome-shell (Ubuntu Jammy) Importance: Undecided Status: New ** Tags added: jammy -- 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/1964545 Title: 42beta: moving mouse as screen is fading to screensaver prevents input to shell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964545/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1964541] [NEW] 42beta: Cannot re-arrange Firefox browser tabs
Public bug reported: Since 42~beta-1ubuntu1, and still present in 42~beta-1ubuntu2, attempting to re-arrange tabs in Firefox fails. Click and drag the tab and release, nothing changes. The next click to the tab is ignored. syslog has the following: Mar 11 13:06:47 desktop firefox[2192]: Attempting to add a widget with type GtkWindow to a container of type GtkWindow, but the widget is already inside a container of type GtkWindow, please remove the widget from its existing container first. Mar 11 13:06:48 desktop firefox[2192]: Attempting to add a widget with type GtkWindow to a container of type GtkWindow, but the widget is already inside a container of type GtkWindow, please remove the widget from its existing container first. Mar 11 13:06:50 desktop firefox[2192]: Attempting to add a widget with type GtkWindow to a container of type GtkWindow, but the widget is already inside a container of type GtkWindow, please remove the widget from its existing container first. Mar 11 13:06:51 desktop firefox[2192]: Attempting to add a widget with type GtkWindow to a container of type GtkWindow, but the widget is already inside a container of type GtkWindow, please remove the widget from its existing container first. gnome-shell 42~beta-1ubuntu2 Firefox Snap 98.0-3 (1073) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1964541 Title: 42beta: Cannot re-arrange Firefox browser tabs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964541/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1964539] Re: 42beta: screen unlock gets stuck on primary display, secondary display is unlocked
** Attachment added: "Primary screen stuck, secondary is unlocked" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964539/+attachment/5567839/+files/IMG_20220311_122713.jpg -- 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/1964539 Title: 42beta: screen unlock gets stuck on primary display, secondary display is unlocked To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964539/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1964539] [NEW] 42beta: screen unlock gets stuck on primary display, secondary display is unlocked
Public bug reported: [Impact] Occasionally, when the screen has been locked for a medium length of time, > 5 mins, when you press the spacebar, enter your password, the primary display freezes and the lockscreen slider does not slide up. The secondary screen is fine, and unlocks. See screenshot for what it looks like. You can click, interact with the secondary screen. On the primary screen, you can super key and launch an application, but you won't be able to interact with it. You can't see what you are doing. The way to fix is to re-lock the screen, wait a bit, and attempt to unlock. Sometimes you won't be able to unlock immediately, as it is difficult to get the monitor to power on again, it appears gnome-shell does not send the wakeup signal. gnome-shell 42~beta-1ubuntu2 from -proposed. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1964539 Title: 42beta: screen unlock gets stuck on primary display, secondary display is unlocked To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964539/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1962807] Re: segfault in libgtk-x11-2.0.so.0 with several programs
I used synaptic to install the package and then did a restart of the system after cleanly closing all running programs. That of course required me to log back in when the system restarted. Is there more I should do at this point? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1962807 Title: segfault in libgtk-x11-2.0.so.0 with several programs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1962807/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1960917] Re: Please remove gnome-desktop3, replaced by gnome-desktop
Already got picked up via process-removals. Generally no reason to file removal bugs for cases like this. ** Changed in: gnome-desktop3 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-desktop3 in Ubuntu. https://bugs.launchpad.net/bugs/1960917 Title: Please remove gnome-desktop3, replaced by gnome-desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1960917/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1962807] Re: segfault in libgtk-x11-2.0.so.0 with several programs
the earlier experience of having the segfault not resolved after removing it suggests that you might need to restart the session for the change to be active, did you try to logout and log in again? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1962807 Title: segfault in libgtk-x11-2.0.so.0 with several programs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1962807/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1962807] Re: segfault in libgtk-x11-2.0.so.0 with several programs
Installed libgail-common via synaptic as requested and restarted the system. The results are not what I expected: dhdurgee@z560:~/Downloads$ fcl Gtk-Message: 12:46:26.155: Failed to load module "gail" ** (fcl:2132): WARNING **: 12:46:26.238: (../atk-adaptor/bridge.c:1018):atk_bridge_adaptor_init: runtime check failed: (root) dhdurgee@z560:~/Downloads$ apt-cache showpkg libgail-common Package: libgail-common Versions: 2.24.32-4ubuntu4 (/var/lib/apt/lists/pubmirrors.dal.corespace.com_ubuntu_dists_focal_main_binary-amd64_Packages) Description Language: File: /var/lib/apt/lists/pubmirrors.dal.corespace.com_ubuntu_dists_focal_main_binary-amd64_Packages MD5: 97f579410f9d8e3edb5f60b6c06b9ef7 Description Language: File: /var/lib/apt/lists/pubmirrors.dal.corespace.com_ubuntu_dists_focal_main_binary-i386_Packages MD5: 97f579410f9d8e3edb5f60b6c06b9ef7 Description Language: en File: /var/lib/apt/lists/pubmirrors.dal.corespace.com_ubuntu_dists_focal_main_i18n_Translation-en MD5: 97f579410f9d8e3edb5f60b6c06b9ef7 Reverse Depends: libgail-common:i386,libgail-common 2.24.32-4ubuntu4 ubuntu-unity-desktop,libgail-common ubuntu-mate-desktop,libgail-common ubuntu-mate-core,libgail-common ubuntu-budgie-desktop,libgail-common multimedia-devel,libgail-common libgnomecanvas2-0,libgail-common libgail-dev,libgail-common 2.24.32-4ubuntu4 libgail-common:i386,libgail-common 2.24.32-4ubuntu4 libgtk2.0-0,libgail-common Dependencies: 2.24.32-4ubuntu4 - libatk1.0-0 (2 1.32.0) libc6 (2 2.4) libgail18 (5 2.24.32-4ubuntu4) libgdk-pixbuf2.0-0 (2 2.22.1) libglib2.0-0 (2 2.37.3) libgtk2.0-0 (2 2.24.0) libpango-1.0-0 (2 1.28.3) libx11-6 (0 (null)) libgail-common:i386 (35 2.24.32-4ubuntu4) libgail-common:i386 (38 2.24.32-4ubuntu4) Provides: 2.24.32-4ubuntu4 - Reverse Provides: dhdurgee@z560:~/Downloads$ Is this what you expected? I expected either the load failed message to go away or for the crash to return. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1962807 Title: segfault in libgtk-x11-2.0.so.0 with several programs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1962807/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
This bug was fixed in the package systemd - 249.10-0ubuntu2 --- systemd (249.10-0ubuntu2) jammy; urgency=medium * Fix deadlock between pid1 and dbus-daemon (LP: #1871538) File: debian/patches/pid1-set-SYSTEMD_NSS_DYNAMIC_BYPASS-1-env-var-for-dbus-da.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=100a7bfc2d0f82c3afbede04a022c655529cffac * Don't override Ubuntu's default sysctl values (LP: #1962038) File: debian/patches/debian/UBUNTU-Don-t-override-Ubuntu-s-default-sysctl-values-LP-1962038.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=b10cdb7da3539b3a3c3e619b470a75c83e46ef11 -- Lukas Märdian Tue, 08 Mar 2022 14:58:00 +0100 ** Changed in: systemd (Ubuntu Jammy) Status: In Progress => Fix Released -- 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/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1871538/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1964136] Re: Settings item not shown in System menu
IMHO we should still expose the new desktop file as NoDisplay, just to be sure that applications that will target GNOME 42 will be able to open settings. -- 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/1964136 Title: Settings item not shown in System menu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1964136/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1962807] Re: segfault in libgtk-x11-2.0.so.0 with several programs
yes, installing from synaptic is fine. The package comes from gtk2 that's why it's not on the gtk3 buildpage -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1962807 Title: segfault in libgtk-x11-2.0.so.0 with several programs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1962807/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1962807] Re: segfault in libgtk-x11-2.0.so.0 with several programs
How do I reinstall libgail-common? I used dpkg -i with libgail-3-0_3.24.20-0ubuntu1_amd64.deb with no change in behavior. I went back to https://launchpad.net/ubuntu/+source/gtk+3.0/3.24.20-0ubuntu1/+build/19437463 but I don't see a libgail-common file there. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1962807 Title: segfault in libgtk-x11-2.0.so.0 with several programs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1962807/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1962807] Re: segfault in libgtk-x11-2.0.so.0 with several programs
I just thought to look in synaptic and I see it there. Should I install from there, or is there a reason to do so in another manner? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1962807 Title: segfault in libgtk-x11-2.0.so.0 with several programs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1962807/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1964504] Re: gvfsd-mtp crashed with SIGSEGV in ___pthread_mutex_lock()
*** This bug is a duplicate of bug 1962628 *** https://bugs.launchpad.net/bugs/1962628 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1962628, so 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. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1964504/+attachment/5567776/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1964504/+attachment/5567778/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1964504/+attachment/5567781/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1964504/+attachment/5567782/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1964504/+attachment/5567783/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1964504/+attachment/5567784/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1964504/+attachment/5567785/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1962628 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1964504 Title: gvfsd-mtp crashed with SIGSEGV in ___pthread_mutex_lock() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1964504/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1964499] Re: [jammy] very slow start due to ModemManager timeout
I see. I did use 1.18.6-2 version for whatever reason, which has been deleted from Jammy. Reverting to the current *-1 version solves this. Sorry. ** Changed in: gnome-control-center (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1964499 Title: [jammy] very slow start due to ModemManager timeout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1964499/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1964499] [NEW] [jammy] very slow start due to ModemManager timeout
Public bug reported: Hi, In Jammy + GS 42, I get a very slow start for g-c-c. In logs: 17:33:32 gnome-control-c: Error connecting to ModemManager: Erreur lors de l’appel de StartServiceByName pour org.freedesktop.ModemManager1 : Failed to activate service 'org.freedesktop.ModemManager1': timed out (service_start_timeout=25000ms) 17:33:32 geoclue: Failed to connect to ModemManager: Erreur lors de l’appel de StartServiceByName pour org.freedesktop.ModemManager1 : Failed to activate service 'org.freedesktop.ModemManager1': timed out (service_start_timeout=25000ms) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1964499 Title: [jammy] very slow start due to ModemManager timeout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1964499/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1962346] Re: Ubuntu reboots instead of powering off if a software updates exists
** Changed in: packagekit (Ubuntu) Status: New => Invalid -- 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/1962346 Title: Ubuntu reboots instead of powering off if a software updates exists To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1962346/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1964496] [NEW] [GS 42] display switching key does not work
Public bug reported: Hi, Using GS 42 in Jammy, when I press the display switch key of my laptop keyboard, I get the usual pop-up but the selected item is not applied. I have to use gnome-control-center to configure my displays. (gcc is slow to start these days?) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1964496 Title: [GS 42] display switching key does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964496/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1964492] Re: gvfsd-mtp crashed with SIGSEGV in ___pthread_mutex_lock()
*** This bug is a duplicate of bug 1962628 *** https://bugs.launchpad.net/bugs/1962628 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1962628, so 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. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1964492/+attachment/5567736/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1964492/+attachment/5567738/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1964492/+attachment/5567741/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1964492/+attachment/5567742/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1964492/+attachment/5567743/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1964492/+attachment/5567744/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1964492/+attachment/5567745/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1962628 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1964492 Title: gvfsd-mtp crashed with SIGSEGV in ___pthread_mutex_lock() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1964492/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1964493] [NEW] gdm has a black baclground now
Public bug reported: Using the GNOME 42 updates in proposed the login screen background is black, that feels buggy, we should revert to the old style ** Affects: yaru-theme (Ubuntu) Importance: High Assignee: Marco Trevisan (Treviño) (3v1n0) Status: New ** Package changed: gdm3 (Ubuntu) => yaru-theme (Ubuntu) ** Changed in: yaru-theme (Ubuntu) Importance: Undecided => High ** Changed in: yaru-theme (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- 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/1964493 Title: gdm has a black baclground now To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1964493/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1962807] Re: segfault in libgtk-x11-2.0.so.0 with several programs
I will take a stab at this later today. Yesterday while searching a bit I may have encountered the reason these particular packages have a problem. I was doing a search and it may be that the packages having the problem I am seeing are all qt5 users. Could there be a problem between qt5 and the libgail under some circumstances? Is there a qt5 configuration file somewhere that might offer a way to tweak things? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1962807 Title: segfault in libgtk-x11-2.0.so.0 with several programs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1962807/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1964136] Re: Settings item not shown in System menu
** Changed in: gnome-shell (Ubuntu) Status: Triaged => Fix Committed ** Changed in: gnome-shell (Ubuntu) Assignee: (unassigned) => Jeremy Bicha (jbicha) -- 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/1964136 Title: Settings item not shown in System menu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1964136/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
** Changed in: evince (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1794064 Title: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
** Bug watch added: Debian Bug tracker #923345 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923345 ** Also affects: evince (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923345 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1794064 Title: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1962807] Re: segfault in libgtk-x11-2.0.so.0 with several programs
I would start by reinstalling libgail-common, restart and see if that brings the issue back. I also think you can install the pending upgrades, it shouldn't make a difference here -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1962807 Title: segfault in libgtk-x11-2.0.so.0 with several programs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1962807/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1964136] Re: Settings item not shown in System menu
You're right. We need both codesearch lists. I believe updating the distro packages is doable for Jammy but I am willing to wait for 22.10 if you don't think it's a good idea now. For our LTS users as long as they're using distro packages, it shouldn't make a difference which way we go. I think it may be slightly better for the few third-party app developers that call gnome-control-center to use the new name since they can use the new name and not worry about the old name as long as they don't care about old distro versions. I couldn't find any Snap packages that successfully call gnome-control- center. I'm curious to see how that would break. Maybe if we do the rename we can add a compatibility hidden .desktop. I've never done the compatibility D-Bus thing before but I think something in GNOME did it a few years ago. -- 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/1964136 Title: Settings item not shown in System menu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1964136/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1964458] Re: [jammy] gnome-shell crashes with SIGSEGV in js::gc::Cell::storeBuffer from js::gc::PostWriteBarrierImpl
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1964458 ** Tags added: iso-testing -- 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/1964458 Title: [jammy] gnome-shell crashes with SIGSEGV in js::gc::Cell::storeBuffer from js::gc::PostWriteBarrierImpl To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1964458/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1964458] Re: [jammy] gnome-shell crashes with SIGSEGV in js::gc::Cell::storeBuffer from js::gc::PostWriteBarrierImpl
** Description changed: - gnome-shell crashes on exit with SIGSEGV in: + 'gnome-shell --sm-disable --mode=ubiquity' crashes on exit with SIGSEGV + in: #0 0x7fd9229e61b4 in js::gc::Cell::storeBuffer (this=, this=) at .././js/src/gc/Cell.h:357 #1 js::gc::PostWriteBarrierImpl (next=, prev=, cellp=) at .././js/src/gc/StoreBuffer.h:654 #2 js::gc::PostWriteBarrier (next=, prev=, vp=) at .././js/src/gc/StoreBuffer.h:666 #3 js::InternalBarrierMethods::postBarrier (next=, prev=, vp=0x7fd910018210) at .././js/src/gc/Barrier.h:333 #4 js::InternalBarrierMethods::postBarrier (vp=0x7fd910018210, prev=, next=) at .././js/src/gc/Barrier.h:332 #5 0x7fd924858fd2 in js::BarrierMethods::postWriteBarrier (next=, prev=, vp=, vp=, prev=, next=) at /usr/include/mozjs-91/js/RootingAPI.h:770 #6 JS::Heap::postWriteBarrier (next=, prev=, this=, this=, prev=, next=) at /usr/include/mozjs-91/js/RootingAPI.h:361 #7 JS::Heap::~Heap (this=, this=) at /usr/include/mozjs-91/js/RootingAPI.h:323 #8 mozilla::detail::VectorImpl, 0ul, js::SystemAllocPolicy, false>::destroy ( aEnd=0x7fd910018228, aBegin=) at /usr/include/mozjs-91/mozilla/Vector.h:65 #9 mozilla::Vector, 0ul, js::SystemAllocPolicy>::~Vector (this=, this=) at /usr/include/mozjs-91/mozilla/Vector.h:901 #10 JS::GCVector, 0ul, js::SystemAllocPolicy>::~GCVector (this=, this=) at /usr/include/mozjs-91/js/GCVector.h:43 #11 GjsContextPrivate::~GjsContextPrivate (this=, this=) at ../gjs/context.cpp:483 #12 0x7fd92485a228 in gjs_context_finalize (object=0x55f0edb2b170) at ../gjs/context.cpp:496 #13 0x7fd9252f3e5d in g_object_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #14 0x7fd92553e77d in _shell_global_destroy_gjs_context (self=) at ../src/shell-global.c:703 #15 0x55f0ec173ece in main (argc=, argv=) at ../src/main.c:659 -- 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/1964458 Title: [jammy] gnome-shell crashes with SIGSEGV in js::gc::Cell::storeBuffer from js::gc::PostWriteBarrierImpl To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1964458/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1964463] Re: Ubuntu Jammy gnome-shell crashed with SIGSEGV
*** This bug is a duplicate of bug 1964458 *** https://bugs.launchpad.net/bugs/1964458 It looks like the crash address has shifted slightly in the latest mozjs version but this is almost certainly bug 1964458. Still waiting for the bots to try and retrace it. ** This bug has been marked a duplicate of bug 1964458 [jammy] gnome-shell crashes with SIGSEGV in js::gc::Cell::storeBuffer from js::gc::PostWriteBarrierImpl -- 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/1964463 Title: Ubuntu Jammy gnome-shell crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964463/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1963770] Re: gnome-shell crashed with SIGSEGV
*** This bug is a duplicate of bug 1964458 *** https://bugs.launchpad.net/bugs/1964458 I failed to notice this is from: gnome-shell --sm-disable --mode=ubiquity and the crash address XXX1b4 confirms it, this is bug 1964458. ** This bug is no longer a duplicate of bug 1964463 Ubuntu Jammy gnome-shell crashed with SIGSEGV ** This bug has been marked a duplicate of bug 1964458 [jammy] gnome-shell crashes with SIGSEGV in js::gc::Cell::storeBuffer from js::gc::PostWriteBarrierImpl -- 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/1963770 Title: gnome-shell crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1963770/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1964458] Re: [jammy] gnome-shell crashes with SIGSEGV in js::gc::Cell::storeBuffer from js::gc::PostWriteBarrierImpl
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mozjs91 (Ubuntu) Status: New => Confirmed -- 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/1964458 Title: [jammy] gnome-shell crashes with SIGSEGV in js::gc::Cell::storeBuffer from js::gc::PostWriteBarrierImpl To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1964458/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1964458] Re: [jammy] gnome-shell crashes with SIGSEGV in js::gc::Cell::storeBuffer from js::gc::PostWriteBarrierImpl
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- 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/1964458 Title: [jammy] gnome-shell crashes with SIGSEGV in js::gc::Cell::storeBuffer from js::gc::PostWriteBarrierImpl To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1964458/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1964458] Re: [jammy] gnome-shell crashes with SIGSEGV in js::gc::Cell::storeBuffer from js::gc::PostWriteBarrierImpl
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gjs (Ubuntu) Status: New => Confirmed -- 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/1964458 Title: [jammy] gnome-shell crashes with SIGSEGV in js::gc::Cell::storeBuffer from js::gc::PostWriteBarrierImpl To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1964458/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1964463] Ubuntu Jammy gnome-shell crashed with SIGSEGV
*** This bug is a duplicate of bug 1964458 *** https://bugs.launchpad.net/bugs/1964458 Stacktrace: #0 0x7f04cd0f7f44 in ?? () No symbol table info available. Backtrace stopped: Cannot access memory at address 0x7fff167a9950 StacktraceSource: #0 0x7f04cd0f7f44 in ?? () StacktraceTop: ?? () ** Tags removed: need-amd64-retrace -- 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/1964463 Title: Ubuntu Jammy gnome-shell crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964463/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1964463] Re: Ubuntu Jammy gnome-shell crashed with SIGSEGV
*** This bug is a duplicate of bug 1964458 ***
https://bugs.launchpad.net/bugs/1964458
** Description changed:
Testing Ubuntu Jammy Live session daily iso 10-03-2022
gnome-shell crashed after selecting Firefox snap
-
- This was originally reported bug 1963770 which i will mark as duplicate
- - I am refiling this as requested in the original bug reports comments.
ProblemType: Crash
DistroRelease: Ubuntu 22.04
Package: gnome-shell 41.3-1ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
Uname: Linux 5.15.0-22-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu78
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.467
CurrentDesktop: ubuntu:GNOME
Date: Thu Mar 10 10:13:28 2022
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:
- b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'41.3'"
- b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us'), ('xkb',
'au'), ('xkb', 'cm'), ('xkb', 'gb')]"
- b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
- b'org.gnome.desktop.notifications' b'application-children' b"['apport-gtk']"
+ b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'41.3'"
+ b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us'), ('xkb',
'au'), ('xkb', 'cm'), ('xkb', 'gb')]"
+ b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
+ b'org.gnome.desktop.notifications' b'application-children' b"['apport-gtk']"
LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220310)
ProcCmdline: gnome-shell --sm-disable --mode=ubiquity
ProcEnviron:
- PATH=(custom, no user)
- LANG=C.UTF-8
- XDG_RUNTIME_DIR=
+ PATH=(custom, no user)
+ LANG=C.UTF-8
+ XDG_RUNTIME_DIR=
RelatedPackageVersions: mutter-common 41.3-3ubuntu1
SegvAnalysis:
- Segfault happened at: 0x7f04cd0f7f44:mov(%rsi),%rax
- PC (0x7f04cd0f7f44) ok
- source "(%rsi)" (0x2d78d420) not located in a known VMA region (needed
readable region)!
- destination "%rax" ok
+ Segfault happened at: 0x7f04cd0f7f44:mov(%rsi),%rax
+ PC (0x7f04cd0f7f44) ok
+ source "(%rsi)" (0x2d78d420) not located in a known VMA region (needed
readable region)!
+ destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-shell
Stacktrace:
- #0 0x7f04cd0f7f44 in ?? ()
- No symbol table info available.
- Backtrace stopped: Cannot access memory at address 0x7fff167a9950
+ #0 0x7f04cd0f7f44 in ?? ()
+ No symbol table info available.
+ Backtrace stopped: Cannot access memory at address 0x7fff167a9950
StacktraceTop: ?? ()
Title: gnome-shell crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
separator:
--
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/1964463
Title:
Ubuntu Jammy gnome-shell crashed with SIGSEGV
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964463/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1963770] Re: gnome-shell crashed with SIGSEGV
*** This bug is a duplicate of bug 1964458 *** https://bugs.launchpad.net/bugs/1964458 ** This bug has been marked a duplicate of bug 1964463 Ubuntu Jammy gnome-shell crashed with SIGSEGV -- 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/1963770 Title: gnome-shell crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1963770/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1964458] Re: [jammy] gnome-shell crashes with SIGSEGV in js::gc::Cell::storeBuffer from js::gc::PostWriteBarrierImpl
It appears the mozjs Heap is a bogus pointer from very early on. Next steps: 1. See if the latest gjs update has changed the situation (waiting on new live images). 2. Look into gjs to see if the problem starts in there or if the whole gjs context from gnome-shell is invalid. -- 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/1964458 Title: [jammy] gnome-shell crashes with SIGSEGV in js::gc::Cell::storeBuffer from js::gc::PostWriteBarrierImpl To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1964458/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1964463] Re: Ubuntu Jammy gnome-shell crashed with SIGSEGV
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- 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/1964463 Title: Ubuntu Jammy gnome-shell crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964463/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1964463] [NEW] Ubuntu Jammy gnome-shell crashed with SIGSEGV
Public bug reported:
Testing Ubuntu Jammy Live session daily iso 10-03-2022
gnome-shell crashed after selecting Firefox snap
ProblemType: Crash
DistroRelease: Ubuntu 22.04
Package: gnome-shell 41.3-1ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
Uname: Linux 5.15.0-22-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu78
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.467
CurrentDesktop: ubuntu:GNOME
Date: Thu Mar 10 10:13:28 2022
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'41.3'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us'), ('xkb', 'au'),
('xkb', 'cm'), ('xkb', 'gb')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.notifications' b'application-children' b"['apport-gtk']"
LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220310)
ProcCmdline: gnome-shell --sm-disable --mode=ubiquity
ProcEnviron:
PATH=(custom, no user)
LANG=C.UTF-8
XDG_RUNTIME_DIR=
RelatedPackageVersions: mutter-common 41.3-3ubuntu1
SegvAnalysis:
Segfault happened at: 0x7f04cd0f7f44: mov(%rsi),%rax
PC (0x7f04cd0f7f44) ok
source "(%rsi)" (0x2d78d420) not located in a known VMA region (needed
readable region)!
destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-shell
Stacktrace:
#0 0x7f04cd0f7f44 in ?? ()
No symbol table info available.
Backtrace stopped: Cannot access memory at address 0x7fff167a9950
StacktraceTop: ?? ()
Title: gnome-shell crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
separator:
** Affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: Confirmed
** Tags: amd64 apport-crash jammy
** Information type changed from Private to Public
--
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/1964463
Title:
Ubuntu Jammy gnome-shell crashed with SIGSEGV
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964463/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1964458] Re: [jammy] gnome-shell crashes with SIGSEGV in js::gc::Cell::storeBuffer from js::gc::PostWriteBarrierImpl
** Also affects: gjs (Ubuntu) Importance: Undecided Status: New ** Description changed: - gnome-shell crashes with SIGSEGV in: + gnome-shell crashes on exit with SIGSEGV in: #0 0x7fd9229e61b4 in js::gc::Cell::storeBuffer (this=, this=) - at .././js/src/gc/Cell.h:357 + at .././js/src/gc/Cell.h:357 #1 js::gc::PostWriteBarrierImpl (next=, prev=, cellp=) - at .././js/src/gc/StoreBuffer.h:654 + at .././js/src/gc/StoreBuffer.h:654 #2 js::gc::PostWriteBarrier (next=, prev=, vp=) - at .././js/src/gc/StoreBuffer.h:666 - #3 js::InternalBarrierMethods::postBarrier (next=, prev=, - vp=0x7fd910018210) at .././js/src/gc/Barrier.h:333 - #4 js::InternalBarrierMethods::postBarrier (vp=0x7fd910018210, prev=, - next=) at .././js/src/gc/Barrier.h:332 - #5 0x7fd924858fd2 in js::BarrierMethods::postWriteBarrier (next=, - prev=, vp=, vp=, prev=, next=) - at /usr/include/mozjs-91/js/RootingAPI.h:770 - #6 JS::Heap::postWriteBarrier (next=, prev=, this=, - this=, prev=, next=) at /usr/include/mozjs-91/js/RootingAPI.h:361 + at .././js/src/gc/StoreBuffer.h:666 + #3 js::InternalBarrierMethods::postBarrier (next=, prev=, + vp=0x7fd910018210) at .././js/src/gc/Barrier.h:333 + #4 js::InternalBarrierMethods::postBarrier (vp=0x7fd910018210, prev=, + next=) at .././js/src/gc/Barrier.h:332 + #5 0x7fd924858fd2 in js::BarrierMethods::postWriteBarrier (next=, + prev=, vp=, vp=, prev=, next=) + at /usr/include/mozjs-91/js/RootingAPI.h:770 + #6 JS::Heap::postWriteBarrier (next=, prev=, this=, + this=, prev=, next=) at /usr/include/mozjs-91/js/RootingAPI.h:361 #7 JS::Heap::~Heap (this=, this=) - at /usr/include/mozjs-91/js/RootingAPI.h:323 + at /usr/include/mozjs-91/js/RootingAPI.h:323 #8 mozilla::detail::VectorImpl, 0ul, js::SystemAllocPolicy, false>::destroy ( - aEnd=0x7fd910018228, aBegin=) at /usr/include/mozjs-91/mozilla/Vector.h:65 - #9 mozilla::Vector, 0ul, js::SystemAllocPolicy>::~Vector (this=, - this=) at /usr/include/mozjs-91/mozilla/Vector.h:901 - #10 JS::GCVector, 0ul, js::SystemAllocPolicy>::~GCVector (this=, - this=) at /usr/include/mozjs-91/js/GCVector.h:43 + aEnd=0x7fd910018228, aBegin=) at /usr/include/mozjs-91/mozilla/Vector.h:65 + #9 mozilla::Vector, 0ul, js::SystemAllocPolicy>::~Vector (this=, + this=) at /usr/include/mozjs-91/mozilla/Vector.h:901 + #10 JS::GCVector, 0ul, js::SystemAllocPolicy>::~GCVector (this=, + this=) at /usr/include/mozjs-91/js/GCVector.h:43 #11 GjsContextPrivate::~GjsContextPrivate (this=, this=) at ../gjs/context.cpp:483 #12 0x7fd92485a228 in gjs_context_finalize (object=0x55f0edb2b170) at ../gjs/context.cpp:496 #13 0x7fd9252f3e5d in g_object_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #14 0x7fd92553e77d in _shell_global_destroy_gjs_context (self=) at ../src/shell-global.c:703 #15 0x55f0ec173ece in main (argc=, argv=) at ../src/main.c:659 ** Changed in: gnome-shell (Ubuntu) Milestone: None => ubuntu-22.04-beta -- 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/1964458 Title: [jammy] gnome-shell crashes with SIGSEGV in js::gc::Cell::storeBuffer from js::gc::PostWriteBarrierImpl To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1964458/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1964392] Re: gimp refuse to start
Hello, In fact, my installation is not quite standard, and apport is no longer installed. On the other hand, I have the problem changed a few minutes ago by replacing the obsolete PPA of otto-kesselgulasch by that of ubuntuhandbook, and by uninstalling, then reinstalling Gimp. Another error message appeared: -- christophe@Arcturus:~$ gimp GEGL-Message: 10:32:48.007: Erreur de chargement du module « /usr/lib/x86_64-linux-gnu/gegl-0.4/sdl2-display.so » : /usr/lib/x86_64-linux-gnu/libSDL2-2.0.so.0: undefined symbol: wl_proxy_get_tag thread '' panicked at 'cannot access a Thread Local Storage value during or after destruction: AccessError', /usr/src/rustc-1.43.0/src/libstd/thread/local.rs:239:9 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace fatal runtime error: failed to initiate panic, error 5 gimp: fatal error: Abandon 26 ../sysdeps/unix/sysv/linux/read.c: Aucun fichier ou dossier de ce type. christophe@Arcturus:~$ export RUST_BACKTRACE=1 christophe@Arcturus:~$ gimp GEGL-Message: 10:34:44.855: Erreur de chargement du module « /usr/lib/x86_64-linux-gnu/gegl-0.4/sdl2-display.so » : /usr/lib/x86_64-linux-gnu/libSDL2-2.0.so.0: undefined symbol: wl_proxy_get_tag thread panicked while processing panic. aborting. Instruction non permise -- I think the original problem arose during a failed attempt to update FFmpeg for a recent version of Blender which I was unable to clean completely. I continue to investigate on my side, but perhaps should close the open bug since the symptoms have changed? Best regards Le jeu. 10 mars 2022 à 10:25, lotuspsychje <1964...@bugs.launchpad.net> a écrit : > 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 1964392 > > 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 subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1964392 > > Title: > gimp refuse to start > > Status in gimp package in Ubuntu: > New > > Bug description: > > > > ``` > GNU Image Manipulation Program version 2.10.30 > git-describe: GIMP_2_10_30 > Build: unknown rev 0 for linux > # C compiler # > Using built-in specs. > COLLECT_GCC=gcc > COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/9/lto-wrapper > OFFLOAD_TARGET_NAMES=nvptx-none:hsa > OFFLOAD_TARGET_DEFAULT=1 > Target: x86_64-linux-gnu > Configured with: ../src/configure -v --with-pkgversion='Ubuntu > 9.3.0-17ubuntu1~20.04' > --with-bugurl=file:///usr/share/doc/gcc-9/README.Bugs > --enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++,gm2 > --prefix=/usr --with-gcc-major-version-only --program-suffix=-9 > --program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id > --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix > --libdir=/usr/lib --enable-nls --enable-clocale=gnu > --enable-libstdcxx-debug --enable-libstdcxx-time=yes > --with-default-libstdcxx-abi=new --enable-gnu-unique-object > --disable-vtable-verify --enable-plugin --enable-default-pie > --with-system-zlib --with-target-system-zlib=auto --enable-objc-gc=auto > --enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64 > --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic > --enable-offload-targets=nvptx-none=/build/gcc-9-HskZEa/gcc-9-9.3.0/debian/tmp-nvptx/usr,hsa > --without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu > --host=x86_64-linux-gnu --target=x86_64-linux-gnu > Thread model: posix > gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) > > # Libraries # > using babl version 0.1.88 (compiled against version 0.1.88) > using GEGL version 0.4.34 (compiled against version 0.4.34) > using GLib version 2.64.6 (compiled against version 2.64.6) > using GdkPixbuf version 2.40.0 (compiled against version 2.40.0) > using GTK+ version 2.24.32 (compiled against version 2.24.32) > using Pango version 1.44.7 (compiled against version 1.44.7) > using Fontconfig version 2.13.1 (compiled against version 2.13.1) > using Cairo version 1.16.0 (compiled against version 1.16.0) > > ``` > > fatal error: Erreur de segmentation > > Stack trace: > ``` > > # Stack traces obtained from PID 37855 - Thread 37855 # > > [New LWP 37856] > [New LWP 37857] > [New LWP 37858] > [New LWP 37859] > [New LWP 37860] > [New LWP 37861] > [New LWP 37862] > [New LWP 37863] > [New LWP 37864] > [New LWP 37865] > [New LWP 37866] > [Thread debugging using libthread_db enabled] > Using host
[Bug 1947130] Re: gnome-shell crashed with SIGSEGV in js::gc::Cell::storeBuffer from JSObject::writeBarrierPost from js::InternalBarrierMethods from js::InternalBarrierMethods from js::BarrierMethods
The crash is indeed slightly different now that we've moved to mozjs91. It's being tracked in bug 1964458. We don't need to keep this one open for mozjs78. ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Won't Fix -- 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/1947130 Title: gnome-shell crashed with SIGSEGV in js::gc::Cell::storeBuffer from JSObject::writeBarrierPost from js::InternalBarrierMethods from js::InternalBarrierMethods from js::BarrierMethods To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1947130/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1964458] Re: [jammy] gnome-shell crashes with SIGSEGV in js::gc::Cell::storeBuffer from js::gc::PostWriteBarrierImpl
See also bug 1947130, bug 1962513. -- 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/1964458 Title: [jammy] gnome-shell crashes with SIGSEGV in js::gc::Cell::storeBuffer from js::gc::PostWriteBarrierImpl To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964458/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1964458] Re: [jammy] gnome-shell crashes with SIGSEGV in js::gc::Cell::storeBuffer from js::gc::PostWriteBarrierImpl
This is the crash that happens during jammy live sessions. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1964458 Title: [jammy] gnome-shell crashes with SIGSEGV in js::gc::Cell::storeBuffer from js::gc::PostWriteBarrierImpl To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964458/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1964458] [NEW] [jammy] gnome-shell crashes with SIGSEGV in js::gc::Cell::storeBuffer from js::gc::PostWriteBarrierImpl
Public bug reported: gnome-shell crashes with SIGSEGV in: #0 0x7fd9229e61b4 in js::gc::Cell::storeBuffer (this=, this=) at .././js/src/gc/Cell.h:357 #1 js::gc::PostWriteBarrierImpl (next=, prev=, cellp=) at .././js/src/gc/StoreBuffer.h:654 #2 js::gc::PostWriteBarrier (next=, prev=, vp=) at .././js/src/gc/StoreBuffer.h:666 #3 js::InternalBarrierMethods::postBarrier (next=, prev=, vp=0x7fd910018210) at .././js/src/gc/Barrier.h:333 #4 js::InternalBarrierMethods::postBarrier (vp=0x7fd910018210, prev=, next=) at .././js/src/gc/Barrier.h:332 #5 0x7fd924858fd2 in js::BarrierMethods::postWriteBarrier (next=, prev=, vp=, vp=, prev=, next=) at /usr/include/mozjs-91/js/RootingAPI.h:770 #6 JS::Heap::postWriteBarrier (next=, prev=, this=, this=, prev=, next=) at /usr/include/mozjs-91/js/RootingAPI.h:361 #7 JS::Heap::~Heap (this=, this=) at /usr/include/mozjs-91/js/RootingAPI.h:323 #8 mozilla::detail::VectorImpl, 0ul, js::SystemAllocPolicy, false>::destroy ( aEnd=0x7fd910018228, aBegin=) at /usr/include/mozjs-91/mozilla/Vector.h:65 #9 mozilla::Vector, 0ul, js::SystemAllocPolicy>::~Vector (this=, this=) at /usr/include/mozjs-91/mozilla/Vector.h:901 #10 JS::GCVector, 0ul, js::SystemAllocPolicy>::~GCVector (this=, this=) at /usr/include/mozjs-91/js/GCVector.h:43 #11 GjsContextPrivate::~GjsContextPrivate (this=, this=) at ../gjs/context.cpp:483 #12 0x7fd92485a228 in gjs_context_finalize (object=0x55f0edb2b170) at ../gjs/context.cpp:496 #13 0x7fd9252f3e5d in g_object_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #14 0x7fd92553e77d in _shell_global_destroy_gjs_context (self=) at ../src/shell-global.c:703 #15 0x55f0ec173ece in main (argc=, argv=) at ../src/main.c:659 ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Affects: mozjs91 (Ubuntu) Importance: Undecided Status: New ** Tags: jammy ** Also affects: mozjs91 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1964458 Title: [jammy] gnome-shell crashes with SIGSEGV in js::gc::Cell::storeBuffer from js::gc::PostWriteBarrierImpl To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964458/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1962823] Re: gnome-shell crashed with SIGABRT in __pthread_kill_implementation() from __pthread_kill_internal() from __GI___pthread_kill() from __GI_raise() from __GI_abort()
Yes it has changed again. Back to having an unusable stack trace: https://errors.ubuntu.com/problem/bc718fcc290d04f4e23c6246836d992f140e7058 So this bug is invalid. It's going to keep jumping between different stack traces due to issues with errors.ubuntu.com. ** This bug is no longer a duplicate of bug 1868293 gnome-shell crashed in meta_workspace_index: Workspace does not exist to index! ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Invalid -- 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/1962823 Title: gnome-shell crashed with SIGABRT in __pthread_kill_implementation() from __pthread_kill_internal() from __GI___pthread_kill() from __GI_raise() from __GI_abort() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1962823/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1964392] Re: gimp refuse to start
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 1964392 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 Ubuntu Desktop Bugs, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/1964392 Title: gimp refuse to start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1964392/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
