[Bug 1962819] Re: pip fails to install pathlib in Ubuntu 22.04 with "setuptools is not available in the build environment"
Importing setuptools in a python interpreter works fine:
rocko@ubuntu:~$ python3
Python 3.10.2 (main, Feb 26 2022, 08:21:15) [GCC 11.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> try:
... import setuptools
... print('ok')
... except ImportError as error:
... print('failed')
...
ok
>>>
But this same code fails when pip tries to install pathlib:
rocko@ubuntu:~$ pip -v install pathlib
Using pip 22.0.2 from /usr/lib/python3/dist-packages/pip (python 3.10)
Defaulting to user installation because normal site-packages is not writeable
Collecting pathlib
Using cached pathlib-1.0.1.tar.gz (49 kB)
Running command python setup.py egg_info
ERROR: Can not execute `setup.py` since setuptools is not available in the
build environment.
error: subprocess-exited-with-error
× python setup.py egg_info did not run successfully.
│ exit code: 1
╰─> See above for output.
note: This error originates from a subprocess, and is likely not a problem
with pip.
full command: /usr/bin/python3 -c '
exec(compile('"'"''"'"''"'"'
# This is -- a caller that pip uses to run setup.py
#
# - It imports setuptools before invoking setup.py, to enable projects that
directly
# import from `distutils.core` to work with newer packaging standards.
# - It provides a clear error message when setuptools is not installed.
# - It sets `sys.argv[0]` to the underlying `setup.py`, when invoking
`setup.py` so
# setuptools doesn'"'"'t think the script is `-c`. This avoids the
following warning:
# manifest_maker: standard file '"'"'-c'"'"' not found".
# - It generates a shim setup.py, for handling setup.cfg-only projects.
import os, sys, tokenize
try:
import setuptools
except ImportError as error:
print(
"ERROR: Can not execute `setup.py` since setuptools is not available
in "
"the build environment.",
file=sys.stderr,
)
sys.exit(1)
__file__ = %r
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1962819
Title:
pip fails to install pathlib in Ubuntu 22.04 with "setuptools is not
available in the build environment"
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1962819/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962819] [NEW] pip fails to install pathlib in Ubuntu 22.04 with "setuptools is not available in the build environment"
Public bug reported: The latest 22.04 updates have broken pathlib. pip complains that setuptools is not available in the build environment even though the package python3-setuptools v59.6.0-1.2 is installed. This breaks any package relying on pathlib. The output from the install command is: rocko@ubuntu:~$ pip install pathlib Defaulting to user installation because normal site-packages is not writeable Collecting pathlib Downloading pathlib-1.0.1.tar.gz (49 kB) ━━━ 49.3/49.3 KB 117.3 kB/s eta 0:00:00 Preparing metadata (setup.py) ... error error: subprocess-exited-with-error × python setup.py egg_info did not run successfully. │ exit code: 1 ╰─> [1 lines of output] ERROR: Can not execute `setup.py` since setuptools is not available in the build environment. [end of output] note: This error originates from a subprocess, and is likely not a problem with pip. error: metadata-generation-failed × Encountered error while generating package metadata. ╰─> See above for output. note: This is an issue with the package mentioned above, not pip. hint: See above for details. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: python3-pip 22.0.2+dfsg-1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Mar 3 15:13:02 2022 InstallationDate: Installed on 2021-09-28 (156 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Beta amd64 (20210924) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: python-pip UpgradeStatus: Upgraded to jammy on 2022-02-18 (12 days ago) ** Affects: python-pip (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962819 Title: pip fails to install pathlib in Ubuntu 22.04 with "setuptools is not available in the build environment" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1962819/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956040] Re: Malformed TLS handshake with OpenSSL 3.0 (breaks subversion)
Just a note that the duplicate bug https://bugs.launchpad.net/ubuntu/+source/subversion/+bug/1960280 has a workaround, which is to install the version of libserf-1-1 from 21.10 (you also have to pin it to stop apt from updating it automatically). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956040 Title: Malformed TLS handshake with OpenSSL 3.0 (breaks subversion) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/serf/+bug/1956040/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960280] Re: subverion's svn fails against https servers
*** This bug is a duplicate of bug 1956040 *** https://bugs.launchpad.net/bugs/1956040 ** This bug has been marked a duplicate of bug 1956040 Malformed TLS handshake with OpenSSL 3.0 (breaks subversion) ** Summary changed: - subverion's svn fails against https servers + subversion's svn fails against https servers -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960280 Title: subversion's svn fails against https servers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subversion/+bug/1960280/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960280] Re: subverion's svn fails against https servers
The problem seems to be in libserf. If I install the 21.10 version of libserf with dpkg from http://archive.ubuntu.com/ubuntu/pool/universe/s/serf/libserf-1-1_1.3.9-10_amd64.deb, subversion starts working again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960280 Title: subverion's svn fails against https servers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subversion/+bug/1960280/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960280] Re: subverion's svn fails against https servers
Ubuntu 21.10 and 22.04 have exactly the same reported version of svn (1.14.1) and the plugin that handles https, ra_serf (version 1.3.9). However, 21.04 reports it was compiled on Feb 18 2021, while 22.04 reports it was compiled on Dec 3 2021. On both my 22.04 VM and my 22.04 wsl running under Windows, the command "svn list " times out. But it used to work on my 21.10 VM and still works on my 21.10 NUC. Using wireshark, I do see TCP packets being exchanged regularly between the Ubuntu 22.04 machine and the server machine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960280 Title: subverion's svn fails against https servers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subversion/+bug/1960280/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944667] Re: High CPU usage in Xorg with NVIDIA reverse prime external monitor
Thanks for looking so quickly. I'm almost certain the problem will go away without the nvidia driver because the nouveau driver didn't recognise the hardware when I booted off the USB installer, so reverse prime won't work and there will be no external monitor, which is a completely new problem. I was logged into a clean profile with no non-standard gnome-shell extensions running, and 'top' showed Xorg (40%) and irq/93-nvidia (1%) and nvidia-modeset/ (0.3%) as the top three CPU hogs, so it's unlikely to be extensions causing it. FYI, when I checked the journal log for those nv_drm_master_set errors right now, I can see a bunch at 11:47 and another bunch at 11:54, but nothing since (it's now 12:43). But the CPU usage is still high. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944667 Title: High CPU usage in Xorg with NVIDIA reverse prime external monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1944667/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944667] [NEW] High CPU usage in Xorg with NVIDIA reverse prime external monitor
Public bug reported: With my Legion Slim 7 in hybrid graphics mode (using amdgpu to drive the laptop display) and an external monitor connected via the nvidia card on a USB-C/HDMI connection, Xorg consistently uses around 40% CPU even with no apps running. If I put the laptop in discrete graphics mode so the nvidia card drives both the laptop display and the external monitor Xorg uses close to 0% CPU, which is what I would expect it to be in hybrid mode. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xserver-xorg-core 2:1.20.13-1ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.63.01 Tue Aug 3 20:44:16 UTC 2021 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-5ubuntu1) ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None Date: Thu Sep 23 11:48:15 2021 DistUpgraded: Fresh install DistroCodename: impish DistroVariant: ubuntu DkmsStatus: nvidia, 470.63.01, 5.13.0-16-generic, x86_64: installed nvidia, 470.63.01, 5.14.5-051405-generic, x86_64: installed nvidia, 470.63.01, 5.15.0-051500rc2-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GA106M [GeForce RTX 3060 Mobile / Max-Q] [10de:2560] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo GA106M [GeForce RTX 3060 Mobile / Max-Q] [17aa:3801] Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev c5) (prog-if 00 [VGA controller]) Subsystem: Lenovo Cezanne [17aa:380c] InstallationDate: Installed on 2021-09-15 (8 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210910) MachineType: LENOVO 82K8 ProcEnviron: LANGUAGE=en_AU:en TERM=xterm-256color PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.13.0-16-generic root=UUID=99f436de-d37c-4b3e-adb2-612443efc197 ro rootflags=subvol=@ quiet splash amdgpu.backlight=0 vt.handoff=7 SourcePackage: xorg-server UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2021 dmi.bios.release: 1.27 dmi.bios.vendor: LENOVO dmi.bios.version: HACN27WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion S7 15ACH6 dmi.ec.firmware.release: 1.27 dmi.modalias: dmi:bvnLENOVO:bvrHACN27WW:bd08/02/2021:br1.27:efr1.27:svnLENOVO:pn82K8:pvrLegionS715ACH6:skuLENOVO_MT_82K8_BU_idea_FM_LegionS715ACH6:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrLegionS715ACH6: dmi.product.family: Legion S7 15ACH6 dmi.product.name: 82K8 dmi.product.sku: LENOVO_MT_82K8_BU_idea_FM_Legion S7 15ACH6 dmi.product.version: Legion S7 15ACH6 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.1-2ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944667 Title: High CPU usage in Xorg with NVIDIA reverse prime external monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1944667/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944094] [NEW] Can't adjust screen backlight on Legion Slim 7 AMD
Public bug reported: The screen brightness controls don't work on the Legion Slim 7 (AMD) laptop running in hybrid/dynamic mode. The backlight control files appear in /sys/class/backlight/amdgpu_bl0, and writing to /sys/class/backlight/amdgpu_bl0/brightness changes the value in /sys/class/backlight/amdgpu_bl0/actual_brightness, but the screen brightness always remains at 100%. I have tried kernel boot parameters: acpi_backlight=vendor amdgpu.backlight=0 but neither makes any difference. I have read that users with the Legion 7 AMD and Legion 5 Pro AMD can get the backlight working with the amdgpu.backlight=0 kernel boot parameter. One difference between them and this laptop is that it has advanced optimus, meaning that it can switch the laptop display between the amdgpu and nvidia card without rebooting, if that is at all relevant. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-16-generic 5.13.0-16.16 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rocko 1978 F pulseaudio /dev/snd/controlC1: rocko 1978 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Sep 20 09:20:33 2021 InstallationDate: Installed on 2021-09-15 (5 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210910) MachineType: LENOVO 82K8 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.13.0-16-generic root=UUID=99f436de-d37c-4b3e-adb2-612443efc197 ro rootflags=subvol=@ quiet splash amdgpu.backlight=0 vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: XDG_RUNTIME_DIR (/run/user/1001) is not owned by us (uid 0), but by uid 1001! (This could e.g. happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.) No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-16-generic N/A linux-backports-modules-5.13.0-16-generic N/A linux-firmware 1.200 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2021 dmi.bios.release: 1.27 dmi.bios.vendor: LENOVO dmi.bios.version: HACN27WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion S7 15ACH6 dmi.ec.firmware.release: 1.27 dmi.modalias: dmi:bvnLENOVO:bvrHACN27WW:bd08/02/2021:br1.27:efr1.27:svnLENOVO:pn82K8:pvrLegionS715ACH6:skuLENOVO_MT_82K8_BU_idea_FM_LegionS715ACH6:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrLegionS715ACH6: dmi.product.family: Legion S7 15ACH6 dmi.product.name: 82K8 dmi.product.sku: LENOVO_MT_82K8_BU_idea_FM_Legion S7 15ACH6 dmi.product.version: Legion S7 15ACH6 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944094 Title: Can't adjust screen backlight on Legion Slim 7 AMD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944094/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944039] [NEW] Ubiquity installs non-bootable hyrbrid system when nvidia graphics is available
Public bug reported: I installed Ubuntu 21.10 using ubiquity on a Legion Slim 7 with an amd cpu/gpu using the amd gpu to drive the laptop screen but also an nvidia graphics card. The installer ran fine but the installed image failed to boot, just showing a blank screen. The installer had installed both the amdgpu and nvidia drivers but was trying to use only the nvidia driver, which failed to display the login screen on either the laptop screen driven through the amd gpu or on the external monitor driven through the nvidia card. The solution turned out to be to run "sudo prime-select intel" (or more appropriately, "sudo prime-select on-demand", so I could also use prime and reverse prime), which fixed the problem. (Running prime-select intel was a bit counter-intuitive because the cpu is not intel so it me took a long time to figure out the problem.) When hybrid graphics are in use and ubiquity installs the nvidia driver, shouldn't it default to prime-select on-demand instead of prime-select nvidia? ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Sep 18 20:31:57 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2021-09-15 (3 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210910) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish ubiquity-21.10.5 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944039 Title: Ubiquity installs non-bootable hyrbrid system when nvidia graphics is available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1944039/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942684] Re: Kernel 5.14.X / 5.13.14 fails to boot
Just to confirm, Ubuntu's mainline 5.14.5 kernel does boot successfully on my machine with CONFIG_UBSAN_TRAP not set. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942684 Title: Kernel 5.14.X / 5.13.14 fails to boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942684/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942684] Re: Kernel 5.14.X / 5.13.14 fails to boot
I also can't boot the mainline 5.14-4 or 5.14-5 kernels on a Lenovo S7 (AMD 5800H and NVIDIA GPU) - it goes to a blank screen when trying to boot graphics and freezes - I can't open a tty and have to hard reset the system. It looks like I have the laptop in the same mode as the other posters, ie hybrid/dynamic graphics mode using the amdgpu driver for the laptop screen. I can't see any relevant errors in the output "journalctl -b -1" for the failed boot - I think the hang occurs before it has a chance to log them. However, when booting the stock Ubuntu 21.10 5.13.0-16 kernel I do see some nvidia_drm RIP errors in the log in nv_drm_master_set(). Presumably these errors in combination with CONFIG_UBSAN_TRAP are causing the hang? The documentation says that in order to save around 5% of the kernel size, CONFIG_UBSAN_TRAP "reduces the kernel size overhead but turns all warnings (including potentially harmless conditions) into full exceptions that abort the running kernel code (regardless of context, locks held, etc), which may destabilize the system." It seems like a pretty aggressive config option to set! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942684 Title: Kernel 5.14.X / 5.13.14 fails to boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942684/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898395] Re: [nvidia] [amdgpu] Problem with external monitor
Could this be the problem described here: https://forums.developer.nvidia.com/t/ryzen-7-gtx-1660ti-blank-screen- on-external-outputs-in-hybrid-graphics-mode/157800 ie (and this is the case if the external display is connected to the NVIDIA card): "Using amdgpu as a display offload source is currently not supported due to an incompatibility between how the amdgpu driver creates “transparent huge pages” without the compound page flag set and how the NVIDIA driver tries to map them. You can see that this is happening in the dmesg log: [ 49.852234] Unhandled error in __nv_drm_gem_user_memory_handle_vma_fault: -22 Unfortunately, the only current workaround is to recompile the kernel without the CONFIG_TRANSPARENT_HUGEPAGE flag enabled. We’re investigating other ways to work around the problem." -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898395 Title: [nvidia] [amdgpu] Problem with external monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-450/+bug/1898395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918666] Re: Cannot close the modal "Connect to Wifi" window to return to desktop
** Description changed: When I select the task bar menu, click on the Wifi and select "Select to network", a modal window appears that allows me to select a Wifi network. - Normally, when I click Cancel or Connect, the modal window disappears - and returns me to the desktop. + After I have clicked on one of the networks, normally, when I click + Cancel or Connect, the modal window disappears and returns me to the + desktop. With the current gnome-shell, this modal window persists and I cannot - access the desktop - this is both in Wayland and in X. + access the desktop - this is both in Wayland and in X. Connect doesn't + seem to work - it's like the buttons are no longer accepting clicks. The + ESC key also doesn't do anything. (If I don't click on a network, the + ESC key does work, and so does Cancel.) I think I once managed to get Alt-Ctrl-F1 to bring back the GDM login window, but the modal window was still there when I went back into the desktop. Alt-F2 didn't work so I couldn't try re-starting gnome-shell. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.3-3ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Mar 11 20:35:24 2021 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.38.3-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-02-24 (15 days ago) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918666 Title: Cannot close the modal "Connect to Wifi" window to return to desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1918666/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918666] [NEW] Cannot close the modal "Connect to Wifi" window to return to desktop
Public bug reported: When I select the task bar menu, click on the Wifi and select "Select to network", a modal window appears that allows me to select a Wifi network. After I have clicked on one of the networks, normally, when I click Cancel or Connect, the modal window disappears and returns me to the desktop. With the current gnome-shell, this modal window persists and I cannot access the desktop - this is both in Wayland and in X. Connect doesn't seem to work - it's like the buttons are no longer accepting clicks. The ESC key also doesn't do anything. (If I don't click on a network, the ESC key does work, and so does Cancel.) I think I once managed to get Alt-Ctrl-F1 to bring back the GDM login window, but the modal window was still there when I went back into the desktop. Alt-F2 didn't work so I couldn't try re-starting gnome-shell. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.3-3ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Mar 11 20:35:24 2021 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.38.3-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-02-24 (15 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918666 Title: Cannot close the modal "Connect to Wifi" window to return to desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1918666/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917787] Re: evdi-dkms fails to build on hirsute with the latest 5.11 kernel
It has been a known issue for a while: https://github.com/DisplayLink/evdi/issues/249 The trouble is we can patch and build it against 5.11 and it works at first, but it freezes the system if you rearrange the layout, change the resolution, unplug the screen, etc. ** Bug watch added: github.com/DisplayLink/evdi/issues #249 https://github.com/DisplayLink/evdi/issues/249 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917787 Title: evdi-dkms fails to build on hirsute with the latest 5.11 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evdi/+bug/1917787/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917926] Re: Window focus/clicking/moving failures for Xorg sessions in 3.38.3-3ubuntu1
The new mutter fixes things for me too, thanks for the quick turnaround (Wayland still has some annoying issues) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917926 Title: Window focus/clicking/moving failures for Xorg sessions in 3.38.3-3ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1917926/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918377] [NEW] In Wayland after the screensaver, some maximized windows appear behind the ubuntu dock
Public bug reported: In Wayland, some maximized windows such as gnome-terminal and Eclipse get moved to behind the dock when the screensaver is unlocked, ie the window starts maximized and drawn next to the dock, but after locking and unlocking the screen it is now behind the dock (see attached screenshot). Other windows like nautilus don't have this problem. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.3-3ubuntu1 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu59 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Mar 10 13:36:38 2021 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.38.3-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-02-24 (13 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute wayland-session ** Attachment added: "Screenshot from 2021-03-10 13-35-14.png" https://bugs.launchpad.net/bugs/1918377/+attachment/5475243/+files/Screenshot%20from%202021-03-10%2013-35-14.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918377 Title: In Wayland after the screensaver, some maximized windows appear behind the ubuntu dock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1918377/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918278] [NEW] geeqie displays blank window under Wayland (fails to render image)
Public bug reported: This is https://github.com/BestImageViewer/geeqie/issues/539. It is fixed in git now but is still present in the current version of geeqie shipped with Ubuntu 21.04. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: geeqie 1:1.6-6 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu59 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Mar 9 21:39:34 2021 SourcePackage: geeqie UpgradeStatus: Upgraded to hirsute on 2021-02-24 (13 days ago) ** Affects: geeqie (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918278 Title: geeqie displays blank window under Wayland (fails to render image) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geeqie/+bug/1918278/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918213] Re: Can't move windows by dragging title bar; can't resize windows
*** This bug is a duplicate of bug 1917926 *** https://bugs.launchpad.net/bugs/1917926 Yep, I'd say it's that bug. It's fine under Wayland. In 21.04 will it be possible to select a Wayland session from the login screen without commenting out the gdm rule that disables Wayland if the nvidia module is loaded? I've got prime-select set to on-demand, so nvidia is loaded even though intel is the main driver, but Wayland still works - it's just not presented by default and there is no indication given as to why. (It'd be even better if nvidia-prime actually worked in Wayland...) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918213 Title: Can't move windows by dragging title bar; can't resize windows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1918213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918213] Re: Can't move windows by dragging title bar; can't resize windows
*** This bug is a duplicate of bug 1917926 *** https://bugs.launchpad.net/bugs/1917926 ** Description changed: - After a recent update in 21.04, I can no longer move windows by clicking + After a recent update in 21.04, I can no longer move windows with + integrated title bars (eg nautilus, firefox, gnome-terminal) by clicking on the taskbar and dragging. I can't resize them either - although the mouse icon changes, when I click and move the mouse the window doesn't resize. I can move a window holding the Super key and clicking near the window, but it's a bit hit-and-miss - sometimes it moves a different window. + + Windows without an integrated titlebar seem to be fine (eg thunderbird, + synaptic). ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.3-3ubuntu1 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu59 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Mar 9 09:10:45 2021 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.38.3-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-02-24 (12 days ago) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918213 Title: Can't move windows by dragging title bar; can't resize windows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1918213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918213] [NEW] Can't move windows by dragging title bar; can't resize windows
Public bug reported: After a recent update in 21.04, I can no longer move windows by clicking on the taskbar and dragging. I can't resize them either - although the mouse icon changes, when I click and move the mouse the window doesn't resize. I can move a window holding the Super key and clicking near the window, but it's a bit hit-and-miss - sometimes it moves a different window. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.3-3ubuntu1 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu59 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Mar 9 09:10:45 2021 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.38.3-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-02-24 (12 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918213 Title: Can't move windows by dragging title bar; can't resize windows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1918213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899361] Re: udisk prevent disk from standby, standby timer is broken
Actually, I don't think this bug was ever fixed. IIRC we suggested putting in a configurable time for checking the SMART mon status but the gnome dev said that the bug was due to buggy hard drive firmware and so he wasn't going to do anything about it. It's a pain because each time udisks2 is updated I have to edit the source to make the check time longer and then rebuild and re-install it on each of my machines. It seems the "buggy" firmware is quite common in WD drives. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899361 Title: udisk prevent disk from standby, standby timer is broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks/+bug/1899361/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'
systemd 246.6-1ubuntu1 and apport 2.20.11-0ubuntu48 fix this issue for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891657 Title: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1891657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'
I'm still seeing this bug with apport 2.20.11-0ubuntu48 and systemd 246.5-1ubuntu1. Do we need systemd 246.6 before it is fixed? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891657 Title: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1891657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'
I changed [Path] PathChangedGlob=/var/crash/*.crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891657 Title: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1891657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'
Also, if you want to reduce the massive size of the journal logs that this bug creates, do something like this: sudo journalctl --rotate sudo journalctl --vacuum-size=100M That second command reduces it to 100 MB, but you can specify larger or smaller sizes. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891657 Title: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1891657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'
Trying again... After reading the linked systemd bug report, I changed /usr/lib/systemd/system/apport-autoreport.path from having PathExistsGlob to PathChangedGlob and ran sudo systemctl daemon-reload, and this seemed to fix the problem: [Unit] Description=Process error reports when automatic reporting is enabled (file watch) ConditionPathExists=/var/lib/apport/autoreport [Path] PathChangedGlob=/var/crash/*.crash [Install] WantedBy=paths.target Now journalctl -e shows: Sep 23 18:00:35 xps15 whoopsie-upload-all[12306]: /var/crash/_opt_wine-devel_bin_wine-preloader.1000.cr> Sep 23 18:00:35 xps15 whoopsie-upload-all[12306]: All reports processed Sep 23 18:00:35 xps15 systemd[1]: apport-autoreport.service: Succeeded. Sep 23 18:00:35 xps15 systemd[1]: Finished Process error reports when automatic reporting is enabled. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891657 Title: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1891657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'
Doesn't systemd normally stop trying to start a service if it fails too often? That's clearly not happening here, though. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891657 Title: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1891657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894031] Re: Ubuntu 20.10 gnome-control-center dropdowns missing for screen resolution and primary screen
I think this might be fixed now - g-c-c hasn't updated, but I am seeing the dropdowns for resolution and primary display now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1894031 Title: Ubuntu 20.10 gnome-control-center dropdowns missing for screen resolution and primary screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1894031/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'
I ran into this and applied the workaround of deleting all the files in /var/crash to stop the journalctl spam and 100% CPU usage. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891657 Title: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1891657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880099] Re: ubuntu-dock no longer loads under gnome-shell 3.37: JS ERROR: Extension ubuntu-d...@ubuntu.com: Error: No signal 'allocation-changed' on object 'Gjs_ubuntu-dock_ubuntu_com_dash_DashT
However, the gnome-3-38 branch in dash-to-dock does work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880099 Title: ubuntu-dock no longer loads under gnome-shell 3.37: JS ERROR: Extension ubuntu-d...@ubuntu.com: Error: No signal 'allocation- changed' on object 'Gjs_ubuntu- dock_ubuntu_com_dash_DashToDock_MyDashActor' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1880099/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880099] Re: ubuntu-dock no longer loads under gnome-shell 3.37: JS ERROR: Extension ubuntu-d...@ubuntu.com: Error: No signal 'allocation-changed' on object 'Gjs_ubuntu-dock_ubuntu_com_dash_DashT
I think this affects me, at least I no longer get dash-to-dock or ubuntu-dock now that groovy has updated to 3.37. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880099 Title: ubuntu-dock no longer loads under gnome-shell 3.37: JS ERROR: Extension ubuntu-d...@ubuntu.com: Error: No signal 'allocation- changed' on object 'Gjs_ubuntu- dock_ubuntu_com_dash_DashToDock_MyDashActor' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1880099/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894031] Re: Ubuntu 20.10 gnome-control-center dropdowns missing for screen resolution and primary screen
Also may be of interest: if I set either laptop or external monitor to a non-native resolution, I do get a dropdown for the screen set to non- native resolution and can change the resolution in g-c-c. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1894031 Title: Ubuntu 20.10 gnome-control-center dropdowns missing for screen resolution and primary screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1894031/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894031] Re: Ubuntu 20.10 gnome-control-center dropdowns missing for screen resolution and primary screen
Perhaps of interest: if I set the primary monitor to the external monitor via xrandr and then run g-c-c, g-c-c shows a dropdown that allows me to select the laptop monitor as primary. Then if I close g-c-c and re-run it, the dropdown doesn't appear any more. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1894031 Title: Ubuntu 20.10 gnome-control-center dropdowns missing for screen resolution and primary screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1894031/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893579] Re: Ctrl + Alt + T and Fn keys not working
Thanks Sebastien: reverting to gnome-settings-daemon 3.36.1-1ubuntu2 (and rebooting) fixed all the hotkey issues for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893579 Title: Ctrl + Alt + T and Fn keys not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1893579/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893579] Re: Ctrl + Alt + T and Fn keys not working
@Geziel: well, Ubuntu 20.10 *is* a development version, so you expect some bugs. It is normally more usable at this stage of the development cycle, though. FWIW, I ran evtest, and the keys are mostly being reported the same in groovy and focal - they just don't work in groovy. eg the function keys all report their expected values (eg KEY_VOLUMEDOWN, KEY_VOLUMEUP, KEY_MUTE), with the exception of the brightness up/down keys, which aren't reported in either focal or groovy. One exception to this is that Alt-PrtScr is reported in groovy as unknown, whereas it's reported in focal as KEY_SYSRQ and KEY_LEFTALT. PrtScr is reported correctly in both as KEY_SYSRQ. It's still possible to read and change the system brightness in groovy via the kernel, ie on my Dell XPS 15 by catting or echoing an appropriate number to /sys/class/backlight/intel_backlight/brightness, but the function keys don't work and nor does the task bar system menu's dropdown menu slider. The dropdown menu slider is initially set to zero, so it looks like it can't read the brightness, either. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893579 Title: Ctrl + Alt + T and Fn keys not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1893579/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894031] [NEW] Ubuntu 20.10 gnome-control-center dropdowns missing for screen resolution and primary screen
Public bug reported: The Ubuntu 20.10 version of g-c-c lacks the dropdown controls for changing screen resolution or selecting the primary monitor. Where there is normally a dropdown, there is just a label showing the current screen resolution or primary monitor. In some cases the dropdown is there, eg it might be there for the laptop monitor but not the external monitor(s). Changing the resolution of a monitor using xrandr sometimes makes the dropdown appear in g-c-c. I have attached a screenshot showing the issue. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-control-center 1:3.37.90-1ubuntu2 Uname: Linux 5.9.0-050900rc3-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Sep 3 12:55:12 2020 InstallationDate: Installed on 2019-07-01 (429 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to groovy on 2020-09-01 (1 days ago) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy third-party-packages ** Attachment added: "g-c-c window missing dropdowns for primary display and resolution" https://bugs.launchpad.net/bugs/1894031/+attachment/5407264/+files/g-c-c%20missing%20dropdowns.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1894031 Title: Ubuntu 20.10 gnome-control-center dropdowns missing for screen resolution and primary screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1894031/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893579] Re: Ctrl + Alt + T and Fn keys not working
PrtScr and Alt-PrtScr are also not working for me. (Alt-F2 does work, though.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893579 Title: Ctrl + Alt + T and Fn keys not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1893579/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892296] Re: gnome-control-center cannot change resolution of external monitor
FWIW, in Ubuntu 20.10 you can't change the resolution of the external monitor with g-c-c at all, because there is no dropdown for the resolution, just a label showing the current resolution. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892296 Title: gnome-control-center cannot change resolution of external monitor To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1892296/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892296] Re: gnome-control-center cannot change resolution of external monitor
I reported it here: https://gitlab.gnome.org/GNOME/mutter/-/issues/1402 ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1402 https://gitlab.gnome.org/GNOME/mutter/-/issues/1402 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892296 Title: gnome-control-center cannot change resolution of external monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1892296/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892296] Re: gnome-control-center cannot change resolution of external monitor
@Daniel: That current mode is from the xrandr.txt when the working 2560x1440 resolution is set. Lionel and I got the 23.98 Hz figure from monitors.xml that I generated after the 1920x1080 change is applied and the monitor has no signal. With the monitor receiving no signal in 1920x1080, the verbose xrandr shows: 1920x1080 (0xc6) 74.176MHz +HSync +VSync *current h: width 1920 start 2558 end 2602 total 2750 skew0 clock 26.97KHz v: height 1080 start 1084 end 1089 total 1125 clock 23.98Hz So g-c-c is definitely choosing the lowest refresh rate, whereas if I use xrandr's --mode option to set 1920x1080, it choose the 60 Hz rate, which works. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892296 Title: gnome-control-center cannot change resolution of external monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1892296/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892296] Re: gnome-control-center cannot change resolution of external monitor
But why does g-c-c choose the lowest frequency refresh instead of the highest? If I set the resolution to 1920x1080 using xrandr, it chooses the 60 Hz option: 1920x1080 60.00* 50.0059.9430.0025.0024.00 29.9723.98 which is this modeline: 1920x1080 (0xbc) 148.500MHz +HSync +VSync h: width 1920 start 2008 end 2052 total 2200 skew0 clock 67.50KHz v: height 1080 start 1084 end 1089 total 1125 clock 60.00Hz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892296 Title: gnome-control-center cannot change resolution of external monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1892296/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892296] Re: gnome-control-center cannot change resolution of external monitor
This is monitors.xml after changing to the (non-working) 1920x1080 configuration. It seems to have chosen a refresh rate of 23.976079940795898 Hz (is that the last option in xrandr's modeline "1920x1080 60.0050.0059.9430.0025.0024.00 29.9723.98"?). When I use xrandr to (successfully) change the resolution to 1920x1080, it chooses the 60 Hz option. ** Attachment added: "monitors-1920x1080.xml" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1892296/+attachment/5405209/+files/monitors-1920x1080.xml -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892296 Title: gnome-control-center cannot change resolution of external monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1892296/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892296] Re: gnome-control-center cannot change resolution of external monitor
This is after changing to the (working) 2560x1440 resolution. ** Attachment added: "monitors-2560x1440.xml" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1892296/+attachment/5405199/+files/monitors-2560x1440.xml -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892296 Title: gnome-control-center cannot change resolution of external monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1892296/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892296] Re: gnome-control-center cannot change resolution of external monitor
No, that doesn't help - the screen stays blank if I set it to 1920x1080 using g-c-c and then run the set max bpc command. I also tried setting 1920x1080i using xrandr in case that's what g-c-c was choosing but it worked fine. With the 1920x1080 setting chosen in g-c-c (and the monitor consequently getting no signal), this is what xrandr says for HDMI-1: HDMI-1 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 597mm x 336mm 2560x1440 59.95 + 1920x1080 60.0050.0059.9430.0025.0024.0029.97 23.98* 1920x1080i60.0050.0059.94 1600x1200 60.00 1280x1024 75.0260.02 1280x960 60.00 1360x768 60.02 1280x720 60.0050.0059.94 1024x768 75.0370.0760.00 800x600 75.0060.32 720x576 50.00 720x576i 50.00 720x480 60.0059.94 720x480i 60.0059.94 640x480 75.0060.0059.94 720x400 70.08 ie it looks like g-c-c has chosen a mode that doesn't actually exist for xrandr, because none of the modes have an asterisk next to them. Fwiw, I *think* that g-c-c did use to be able to successfully set the resolution to 1920x1080 on this monitor. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892296 Title: gnome-control-center cannot change resolution of external monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1892296/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892296] Re: gnome-control-center cannot change resolution of external monitor
** Attachment added: "xrandr.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1892296/+attachment/5404255/+files/xrandr.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892296 Title: gnome-control-center cannot change resolution of external monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1892296/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892296] Re: gnome-control-center cannot change resolution of external monitor
** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1892296/+attachment/5404256/+files/journal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892296 Title: gnome-control-center cannot change resolution of external monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1892296/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892296] Re: gnome-control-center cannot change resolution of external monitor
It doesn't work in Wayland, either. ** Attachment added: "lspci.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1892296/+attachment/5404254/+files/lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892296 Title: gnome-control-center cannot change resolution of external monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1892296/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892296] [NEW] gnome-control-center cannot change resolution of external monitor
Public bug reported: g-c-c is unable to change the resolution on my external 2560x1440 monitor to 1920x1080 - when I try, the monitor turns off. However, the command "xrandr --output HDMI-1 --mode 1920x1080" does successfully change the resolution. xrandr for the monitor shows: HDMI-1 connected 2560x1440+0+0 (normal left inverted right x axis y axis) 597mm x 336mm 2560x1440 59.95*+ 1920x1080 60.0050.0059.9430.0025.0024.0029.97 23.98 1920x1080i60.0050.0059.94 1600x1200 60.00 1280x1024 75.0260.02 1280x960 60.00 1360x768 60.02 1280x720 60.0050.0059.94 1024x768 75.0370.0760.00 800x600 75.0060.32 720x576 50.00 720x576i 50.00 720x480 60.0059.94 720x480i 60.0059.94 640x480 75.0060.0059.94 720x400 70.08 I tried changing the resolution to 1600x1200 using g-c-c and this did work. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.4-0ubuntu1 Uname: Linux 5.8.1-050801-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Aug 20 11:28:08 2020 InstallationDate: Installed on 2019-07-01 (415 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to focal on 2019-12-08 (255 days ago) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892296 Title: gnome-control-center cannot change resolution of external monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1892296/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1889509] Re: grub boot error : "symbol 'grub_calloc' not found
Is this the same as https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1889556? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1889509 Title: grub boot error : "symbol 'grub_calloc' not found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1889509/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1715435] Re: Can't lock screen with keyboard shortcuts when using lightdm
My Ubuntu 20.04 installation just did this - something changed the org.gnome.desktop.lockdown disable-lock-screen to true and also the blank screen to never (did an update do this?). But there's nothing I can see in gnome-control-center to modify this value, making this bug pretty obscure when it happens. Wouldn't a setting in g-c-c make a lot of sense if you can actually disable the screen lock completely? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1715435 Title: Can't lock screen with keyboard shortcuts when using lightdm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1715435/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849249] Re: gnome-shell crashed with SIGABRT: mutter:ERROR:../src/core/window.c:4841:set_workspace_state: assertion failed: (workspace == NULL)
Ok, I've reported it as bug #1871554. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849249 Title: gnome-shell crashed with SIGABRT: mutter:ERROR:../src/core/window.c:4841:set_workspace_state: assertion failed: (workspace == NULL) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1849249/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849249] Re: gnome-shell crashed with SIGABRT: mutter:ERROR:../src/core/window.c:4841:set_workspace_state: assertion failed: (workspace == NULL)
Do you mean I should recreate this exact same bug and then report it as another one? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849249 Title: gnome-shell crashed with SIGABRT: mutter:ERROR:../src/core/window.c:4841:set_workspace_state: assertion failed: (workspace == NULL) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1849249/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849249] Re: gnome-shell crashed with SIGABRT: mutter:ERROR:../src/core/window.c:4841:set_workspace_state: assertion failed: (workspace == NULL)
Do you mean a link to the original crash? This one has the same date as the bug report: https://errors.ubuntu.com/oops/4bb4a564-f475-11e9-b5e5-fa163e102db1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849249 Title: gnome-shell crashed with SIGABRT: mutter:ERROR:../src/core/window.c:4841:set_workspace_state: assertion failed: (workspace == NULL) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1849249/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849249] Re: gnome-shell crashed with SIGABRT: mutter:ERROR:../src/core/window.c:4841:set_workspace_state: assertion failed: (workspace == NULL)
** Attachment added: "Output of journal -b0" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1849249/+attachment/5348700/+files/journal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849249 Title: gnome-shell crashed with SIGABRT: mutter:ERROR:../src/core/window.c:4841:set_workspace_state: assertion failed: (workspace == NULL) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1849249/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849249] Re: gnome-shell crashed with SIGABRT: mutter:ERROR:../src/core/window.c:4841:set_workspace_state: assertion failed: (workspace == NULL)
Oh, I spoke too soon. I tested it yesterday and it passed, but today it failed. I had geany on the primary monitor this time. ** Changed in: gnome-shell (Ubuntu) Status: Fix Released => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849249 Title: gnome-shell crashed with SIGABRT: mutter:ERROR:../src/core/window.c:4841:set_workspace_state: assertion failed: (workspace == NULL) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1849249/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849249] Re: gnome-shell crashed with SIGABRT: mutter:ERROR:../src/core/window.c:4841:set_workspace_state: assertion failed: (workspace == NULL)
This is fixed for me in gnome-shell 3.36.0-2ubuntu2, thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849249 Title: gnome-shell crashed with SIGABRT: mutter:ERROR:../src/core/window.c:4841:set_workspace_state: assertion failed: (workspace == NULL) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1849249/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866368] Re: gnome-shell crashed with SIGSEGV in wl_resource_get_version(resource=0x0)
I think this might be fixed in gnome-shell 3.36.0-2ubuntu2 - I can't reproduce my duplicate bug https://bugs.launchpad.net/bugs/1868418 anymore. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866368 Title: gnome-shell crashed with SIGSEGV in wl_resource_get_version(resource=0x0) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866368/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868896] Re: Minimized windows reappear when closing the overview
It looks like it's fixed here in gnome-shell 3.36.0-2ubuntu2, thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868896 Title: Minimized windows reappear when closing the overview To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1868896/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868896] Re: Minimized windows reappear when closing the overview
How quickly is Ubuntu likely to be refreshed with the fix? I don't mind minimized windows pseudo-reappearing after the overview screen closes, but they also do the same on every right mouse click in many apps, and then it's a right pain when you keep clicking on them and wonder why they aren't responding! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868896 Title: Minimized windows reappear when closing the overview To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1868896/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869344] Re: gnome-shell right mouse click brings minimized windows to foreground
This doesn't happen with every application, eg right-clicking in Firefox, nautilus, and gnome-terminal demonstrates the bug, but right- clicking in google-chrome doesn't. Also, the behaviour is slightly different in Wayland vs X11 - in X11 I can't interact with the backgrounded window's titlebar but I can move the window using the super key and mouse. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869344 Title: gnome-shell right mouse click brings minimized windows to foreground To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1869344/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869344] [NEW] gnome-shell right mouse click brings minimized windows to foreground
Public bug reported: In today's update of Ubuntu 20.04, if I do this: * Run Firefox non-maximized * Run another app (eg nautilus or gnome-terminal) * Minimize the other app * Right-click on the firefox window then the other app suddenly re-appears. You can only interact with its titlebar, though - you can't type into gnome-terminal or choose a file in nautilus. Using the titlebar, you can move it around and if you click on the maximize icon or double-click to maximize it, it explodes out into nothingness (effectively, it re-minimizes). You can't minimize it, though, using the minimize button. This happens both in Wayland and in X11 and it happens with all extensions disabled. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu1 Uname: Linux 5.6.0-050600rc7-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 27 17:50:39 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-07-01 (270 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606) RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2019-12-08 (110 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869344 Title: gnome-shell right mouse click brings minimized windows to foreground To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1869344/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849249] Re: gnome-shell crashed with SIGABRT: mutter:ERROR:../src/core/window.c:4841:set_workspace_state: assertion failed: (workspace == NULL)
Still happens every time in gnome-shell 3.36.0-2ubuntu1 / geany 1.36-1build1. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849249 Title: gnome-shell crashed with SIGABRT: mutter:ERROR:../src/core/window.c:4841:set_workspace_state: assertion failed: (workspace == NULL) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1849249/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866228] Re: Gnome shell extensions are badly broken
I know we're not supposed to comment on this bug, but this is just to quickly note that almost all of the issues I noted in comment #7 have disappeared now in gnome-shell 3.36.0-2ubuntu1. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866228 Title: Gnome shell extensions are badly broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866228/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866228] Re: Gnome shell extensions are badly broken
Extensions are pretty badly buggy for me on Focal. Some work, but many don't, and won't upgrade, can't be configured, and don't give any information about why they have failed. If I go to https://extensions.gnome.org/, the installed extensions page tells me that there are extensions like gsconnect and night-light-slider have an unspecified error but that they can be upgraded, but when I tell them to upgrade I just get another unspecified error and when I refresh the page, it says again that I can upgrade them. Both those extensions do apparently have 3.36 versions - I just can't upgrade them. Likewise, trying to install these extensions from git doesn't work. I still get an error but with no indication what it is. The new gnome-shell Extensions application doesn't show any extensiosn unless I use the On/Off button to disable and then re-enable them. Then it shows some extensions, but not all, and some of the manually installed ones appear in the Built-In section. None of the configuration/settings windows work, whether I try to launch them from gnome-tweaks, https://extensions.gnome.org/, or the new gnome- shell Extensions application. Coverflow-alt-tab is just broken in X11 (but works in Wayland) - see https://github.com/dmo60/CoverflowAltTab/issues/117. There are some errors in journalctl -e, such as this one: JS ERROR: Error: Wrong type number; string expected: _updateState@resource:///org/gnome/shell/extensionPrefs/main.js:706:9 I read somewhere that the configuration/settings windows not working is a known issue in 3.35, so I'm looking forward to 3.36 arriving in Focal and hopefully fixing some of these things. ** Bug watch added: github.com/dmo60/CoverflowAltTab/issues #117 https://github.com/dmo60/CoverflowAltTab/issues/117 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866228 Title: Gnome shell extensions are badly broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866228/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849249] Re: gnome-shell crashed with SIGABRT: mutter:ERROR:../src/core/window.c:4841:set_workspace_state: assertion failed: (workspace == NULL)
This is still 100% reproducible with with an up-to-date Ubuntu 20.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849249 Title: gnome-shell crashed with SIGABRT: mutter:ERROR:../src/core/window.c:4841:set_workspace_state: assertion failed: (workspace == NULL) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1849249/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842886] Re: Yaru-dark shell menus are not dark
@Carlo: > This premise seems incorrect to me. Gnome-tweaks variant switch worked for gtk applications only, not for shell theme. But that is actually how it used to work. The gnome-shell popups (such as when you press Alt-F2) were indeed light, but the dropdown menus from the top bar were dark. I filed the bug when this changed. For me it's a usability bug: it used to look good with dark theme and dark themed top-bar dropdowns, and it still does, so long as you manually apply the dark user gnome-shell theme. If you don't apply the dark user gnome-shell theme, it looks really jarring. I'm grateful for the yaru dark theme, because I much prefer it to the light theme. I just think it would be much better if it were easy to configure it to be consistent. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842886 Title: Yaru-dark shell menus are not dark To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1842886/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849249] Re: gnome-shell crashed with SIGABRT: mutter:ERROR:../src/core/window.c:4841:set_workspace_state: assertion failed: (workspace == NULL)
I updated the description to note that the text being searched for is not found in the document (which is the case of course for an empty document). ** Description changed: https://errors.ubuntu.com/problem/8317377ffa8b8148baa481d490fd876111eb3c4b gnome-shell crashes with this bug every time that: * I am editing a file in geany * I open the Find window (CTRL-F) and it opens on another monitor - * I type in some text in the find window and press ENTER (or click the Next button) + * I type in some un-findable text in the find window and press ENTER (or click the Next button) + + The system beeps to indicate that the text isn't found, but then + crashes. Note especially that the find window must be on the other monitor - if it's on the same monitor as geany, gnome-shell doesn't crash. (Note: I originally thought that if I moved the find window to the other window and then searched, gnome-shell crashed, but I think what happens is a) I open the window, b) I move it, search for something, and it works, c) I close it and re-open it - it then opens on the other monitor and searching will crash gnome-shell.) gnome-shell restarts, but the crash causes data loss, as most of the running applications don't reappear when it restarts. In case it's relevant, I have a laptop screen set at 2048x1152 and an external monitor configured to be above it at 2560x1440. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 Uname: Linux 5.4.0-050400rc4-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 22 10:37:36 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1570619894 InstallationDate: Installed on 2019-07-01 (112 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606) ProcCmdline: /usr/bin/gnome-shell ProcCwd: /home/rocko ProcEnviron: LANG=en_AU.UTF-8 LANGUAGE=en_AU:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 Signal: 6 SourcePackage: gnome-shell StacktraceTop: () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /lib/x86_64-linux-gnu/libmutter-5.so.0 () at /lib/x86_64-linux-gnu/libmutter-5.so.0 () at /lib/x86_64-linux-gnu/libmutter-5.so.0 Title: gnome-shell crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo separator: -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849249 Title: gnome-shell crashed with SIGABRT: mutter:ERROR:../src/core/window.c:4841:set_workspace_state: assertion failed: (workspace == NULL) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1849249/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848277] Re: Won't start, get "cannot open display: :0" message
The snap version was the only version available in 19.04, and it doesn't run for me in 19.10, but I see there's a non-snap version now available in 19.10 that does run. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848277 Title: Won't start, get "cannot open display: :0" message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1848277/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1841556] Re: cpu frequency stuck below min frequency with power_save governor
I've not had a chance to test it recently - I haven't seen it happen for a while, but I'm not switching between the nvidia and intel cards, either, so I don't expect to. If I get a chance to try it on the weekend I'll report back. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1841556 Title: cpu frequency stuck below min frequency with power_save governor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1841556/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849249] Re: gnome-shell crashed with SIGABRT: mutter:ERROR:../src/core/window.c:4841:set_workspace_state: assertion failed: (workspace == NULL)
I just discovered that on my laptop this bug only applies to X11 sessions, not to Wayland sessions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849249 Title: gnome-shell crashed with SIGABRT: mutter:ERROR:../src/core/window.c:4841:set_workspace_state: assertion failed: (workspace == NULL) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1849249/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849249] Re: gnome-shell crashed with SIGABRT: mutter:ERROR:../src/core/window.c:4841:set_workspace_state: assertion failed: (workspace == NULL)
@jagosta: does it only crash if the dialogs are on different monitors? That's what I find. FWIW, I tried the live USB, but ootb Ubuntu 19.10 doesn't recognise the HDMI monitor, so I can't do dual displays, and I also tried a VirtualBox guest, but even after installing Ubuntu 19.10 and guest drivers, Ubuntu 19.10 doesn't correctly recognise the second monitor, so I can't do dual displays. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849249 Title: gnome-shell crashed with SIGABRT: mutter:ERROR:../src/core/window.c:4841:set_workspace_state: assertion failed: (workspace == NULL) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1849249/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851189] [NEW] gnome-control-center can't configure second virtualbox display
Public bug reported: On a VirtualBox 6.0.14 host, with a fresh install of Ubuntu 19.10 and the virtualbox guest drivers installed, I can't configure a second display, although xrandr shows it to be present. Steps: 1. Install VirtualBox 2. Install Ubuntu 19.10 as a guest with 2 displays (note: at least 2048 MB RAM is required or the guest is chronically slow during installation; I gave the displays 32 MB RAM as well). 3. In the guest, install virtualbox guest drivers and reboot. 4. Run g-c-c and go to the Devices / Displays section. Expected result: I can choose to Join the displays, move them around with the mouse and Apply the new settings successfuly. Actual result: Display 2 is shown normally but Display 1 is just a number (see attached) - I can't move it around or Apply changes. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.34.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 Date: Mon Nov 4 11:49:05 2019 ProcEnviron: LANGUAGE=en_AU:en TERM=xterm-256color PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2019-11-04T11:48:33.047928 ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ** Attachment added: "g-c-c display settings" https://bugs.launchpad.net/bugs/1851189/+attachment/5302623/+files/g-c-c.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851189 Title: gnome-control-center can't configure second virtualbox display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1851189/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851189] Re: gnome-control-center can't configure second virtualbox display
Here's the xrandr. It looks like 0x0 is selected for display Virtual2 and maybe this is confusing g-c-c. ** Attachment added: "xrandr" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1851189/+attachment/5302626/+files/xrandr -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851189 Title: gnome-control-center can't configure second virtualbox display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1851189/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849249] Re: gnome-shell crashed with SIGABRT: mutter:ERROR:../src/core/window.c:4841:set_workspace_state: assertion failed: (workspace == NULL)
I also removed solaar, which had an indicator (but I think it's showing through app-indicators), with no luck. I also tried changing the screen configuration to laptop on the left, monitor on the right, and the bug is still present. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849249 Title: gnome-shell crashed with SIGABRT: mutter:ERROR:../src/core/window.c:4841:set_workspace_state: assertion failed: (workspace == NULL) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1849249/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849249] Re: gnome-shell crashed with SIGABRT: mutter:ERROR:../src/core/window.c:4841:set_workspace_state: assertion failed: (workspace == NULL)
I removed all those extensions (and mate-optimus as well), so ~/.local/share/gnome-shell/extensions/ is completely empty, but the bug is still there. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849249 Title: gnome-shell crashed with SIGABRT: mutter:ERROR:../src/core/window.c:4841:set_workspace_state: assertion failed: (workspace == NULL) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1849249/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849249] Re: gnome-shell crashed with SIGABRT: mutter:ERROR:../src/core/window.c:4841:set_workspace_state: assertion failed: (workspace == NULL)
Can I provide any other information to help speed this along? This is a pretty severe problem - it's annoying because gnome-shell freezes for a long time before restarting, and then it's extremely annoying because you lose any data in applications that don't survive the restart. ** Description changed: https://errors.ubuntu.com/problem/8317377ffa8b8148baa481d490fd876111eb3c4b gnome-shell crashes with this bug every time that: * I am editing a file in geany - * I open the Find window (CTRL-F) - * I move the find window to another monitor, + * I open the Find window (CTRL-F) and it opens on another monitor * I type in some text in the find window and press ENTER (or click the Next button) Note especially that the find window must be on the other monitor - if - it's on the same monitor as geany, gnome-shell doesn't crash. If the - find window opens on the second monitor (so I don't need to move it), - gnome-shell still crashes. + it's on the same monitor as geany, gnome-shell doesn't crash. + + (Note: I originally thought that if I moved the find window to the other + window and then searched, gnome-shell crashed, but I think what happens + is a) I open the window, b) I move it, search for something, and it + works, c) I close it and re-open it - it then opens on the other monitor + and searching will crash gnome-shell.) gnome-shell restarts, but the crash causes data loss, as most of the running applications don't reappear when it restarts. In case it's relevant, I have a laptop screen set at 2048x1152 and an external monitor configured to be above it at 2560x1440. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 Uname: Linux 5.4.0-050400rc4-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 22 10:37:36 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1570619894 InstallationDate: Installed on 2019-07-01 (112 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606) ProcCmdline: /usr/bin/gnome-shell ProcCwd: /home/rocko ProcEnviron: LANG=en_AU.UTF-8 LANGUAGE=en_AU:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 Signal: 6 SourcePackage: gnome-shell StacktraceTop: () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /lib/x86_64-linux-gnu/libmutter-5.so.0 () at /lib/x86_64-linux-gnu/libmutter-5.so.0 () at /lib/x86_64-linux-gnu/libmutter-5.so.0 Title: gnome-shell crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo separator: -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849249 Title: gnome-shell crashed with SIGABRT: mutter:ERROR:../src/core/window.c:4841:set_workspace_state: assertion failed: (workspace == NULL) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1849249/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842882] Re: gnome-control-center no longer shows all the xrandr resolutions
I think it's fixed now, so closing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842882 Title: gnome-control-center no longer shows all the xrandr resolutions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1842882/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1758243] Re: bumblebee needs configuration changes to work with nvidia-driver-390 and libglvnd0
@Matthieu: Yes, nvidia on-demand works great in Ubuntu 19.10 with those two variables. I also include this one (it's to make Vulkan only use the nvidia card - Vulkan works really well for running DX 11 wine apps using dxvk): __VK_LAYER_NV_optimus=NVIDIA_only -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1758243 Title: bumblebee needs configuration changes to work with nvidia-driver-390 and libglvnd0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bumblebee/+bug/1758243/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842882] Re: gnome-control-center no longer shows all the xrandr resolutions
I think it's resolved now. ** Changed in: mutter (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842882 Title: gnome-control-center no longer shows all the xrandr resolutions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1842882/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842882] Re: gnome-control-center no longer shows all the xrandr resolutions
Even with the POP OS! PPA removed, this is still happening. Sometimes the resolutions are all there and sometimes not. ** Changed in: mutter (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842882 Title: gnome-control-center no longer shows all the xrandr resolutions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1842882/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842882] Re: gnome-control-center no longer shows all the xrandr resolutions
I think this might have been caused by the Pop OS! PPA (ppa:system76/pop). I think I must have installed it months ago for some icon set without realising that it loads a ton of other stuff. Its latest iteration of g-c-c segfaults, which is how I realised what was going on. Purging the PPA and using g-c-c 1:3.34.0.1-1ubuntu2, I can now see all the resolutions again. ** Changed in: mutter (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842882 Title: gnome-control-center no longer shows all the xrandr resolutions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1842882/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842882] Re: gnome-control-center no longer shows all the xrandr resolutions
This bug is still an issue with mutter 3.34.0-3ubuntu1. Is there any more info I can provide? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842882 Title: gnome-control-center no longer shows all the xrandr resolutions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1842882/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1758243] Re: bumblebee needs configuration changes to work with nvidia-driver-390 and libglvnd0
@Pete: Yes, more recent kernels now can automatically power down the nvidia card off when it's not in use, so you don't need bbswitch anymore. What's even more cool is that with the nvidia 435.21 driver and the version of X that comes with Ubuntu 19.10, you don't even need bumblebee any more: if you enable nvidia load-on-demand in nvidia-settings, you get an intel desktop with the nvidia card pretty much powered down but you can run any application using the nvidia card by exporting these variables first: export __NV_PRIME_RENDER_OFFLOAD=1 export __GLX_VENDOR_LIBRARY_NAME=nvidia Of course, when the application finishes, the kernel powers down the nvidia card again. VUlkan is also very cool: I export this variable as well to ensure it gets used for the nvidia card: export __VK_LAYER_NV_optimus=NVIDIA_only -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1758243 Title: bumblebee needs configuration changes to work with nvidia-driver-390 and libglvnd0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bumblebee/+bug/1758243/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1843520] Re: ubuntu-dock right-click menu appears at the top-left corner of the desktop (which in some cases is the wrong monitor) and is permanent
It's fixed for me, too, thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1843520 Title: ubuntu-dock right-click menu appears at the top-left corner of the desktop (which in some cases is the wrong monitor) and is permanent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1843520/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1843520] Re: ubuntu-dock right-click menu appears at the top-left corner of the desktop (which in some cases is the wrong monitor) and is permanent
@seb128: Is the fix in the pull request at https://github.com/micheleg /dash-to-dock/pull/975? That version of dash-to-dock works fine for me in Eoan. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1843520 Title: ubuntu-dock right-click menu appears at the top-left corner of the desktop (which in some cases is the wrong monitor) and is permanent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1843520/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1843520] Re: ubuntu-dock right-click menu appears at the top-left corner of the desktop (which in some cases is the wrong monitor) and is permanent
Unfortunately there isn't a working version of dash-to-dock for gnome 33/34, but dash-to-panel is a nice workaround for this issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1843520 Title: ubuntu-dock right-click menu appears at the top-left corner of the desktop (which in some cases is the wrong monitor) and is permanent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1843520/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1843520] Re: ubuntu-dock right-click menu appears on wrong monitor and is permanent
This is probably the relevant error: Sep 11 12:24:12 xps15 gnome-shell[16574]: JS ERROR: TypeError: mutterWindow.get_texture(...).get_size is not a function _cloneTexture@/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/windowPreview.js:382:62 _init@/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/windowPreview.js:371:9 _populateAllWindowMenu@/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/appIcons.js:982:32 update@/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/appIcons.js:943:15 _redisplay@/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/appIcons.js:909:9 popup@resource:///org/gnome/shell/ui/appDisplay.js:2341:9 popupMenu@/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/appIcons.js:351:9 _onButtonPress@resource:///org/gnome/shell/ui/appDisplay.js:1947:13 Se -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1843520 Title: ubuntu-dock right-click menu appears on wrong monitor and is permanent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1843520/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1843520] [NEW] ubuntu-dock right-click menu appears on wrong monitor and is permanent
Public bug reported: Very recently the ubuntu-dock has started displaying some right-click menus for pinned apps on the wrong monitor. It doesn't happen for all the apps, but when it does, the menu is permanent but you can't click on it and you have to restart gnome-shell with ALT-F2 'r' (which now always kills some apps like firefox). See attached screenshot where the menu for gnome-tweaks has appeared at the top left of the top monitor. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell-extension-ubuntu-dock 66ubuntu19.10.1 Uname: Linux 5.3.0-050300rc8-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Sep 11 11:42:07 2019 InstallationDate: Installed on 2019-07-01 (71 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan third-party-packages ** Attachment added: "Dock with permanent popup menu on wrong monitor.jpg" https://bugs.launchpad.net/bugs/1843520/+attachment/5287930/+files/Dock%20with%20permanent%20popup%20menu%20on%20wrong%20monitor.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1843520 Title: ubuntu-dock right-click menu appears on wrong monitor and is permanent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1843520/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842882] Re: gnome-control-center no longer shows all the xrandr resolutions
After resuming from suspend, the extra resolutions have disappeared from g-c-c (but are still available via xrandr), so something is still triggering the bug. ** Changed in: gnome-control-center (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842882 Title: gnome-control-center no longer shows all the xrandr resolutions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1842882/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842882] Re: gnome-control-center no longer shows all the xrandr resolutions
Looks like it's fixed now. ** Changed in: gnome-control-center (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842882 Title: gnome-control-center no longer shows all the xrandr resolutions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1842882/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842882] Re: gnome-control-center no longer shows all the xrandr resolutions
A side-effect of this is that after resuming, gnome-shell will have often (but not always) reverted to a different resolution from the one set when it suspended. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842882 Title: gnome-control-center no longer shows all the xrandr resolutions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1842882/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842886] Re: Yaru-dark shell menus are not dark
Do you mean is it the same bug what I described in comment #10? My comment #11 is more of a easy workaround to get the dark menus (you can easily switch between dark and light with this, as well). Regarding comment #10, I haven't confirmed the problem with the dark user shell themes is a regression yet but it seems pretty likely that it is, since it's pretty unlikely that anyone would post a theme to www .gnome-look.org with menus that you can't read. But it's a different issue from this bug, which is really more of a wish that Ubuntu supplied both yaru and yaru-dark shell themes. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842886 Title: Yaru-dark shell menus are not dark To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1842886/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842886] Re: Yaru-dark shell menus are not dark
> Maybe see https://github.com/ubuntu/yaru/issues/1483 Great, thanks for that link! So I got dark menus working by doing the following: * I cloned the source from https://github.com/ubuntu/yaru.git: git clone https://github.com/ubuntu/yaru.git * After changing into the yaru folder, I changed the build variant to dark in ./gtk/src/light/gtk-3.0/gtk.scss by changing "$variant: 'light';" to "$variant: 'dark';" (as per https://discourse.ubuntu.com/t /yaru-dark-variant/7936) * I built it based on instructions at http://www.ubuntubuzz.com/2019/03 /ubuntus-yaru-theme-on-fedora.html: sudo apt build-dep yaru-theme # ie to get required packages for building cd yaru # ie to cd into the yaru git folder meson build cd build ninja sudo mkdir /usr/share/themes/Yaru-dark/gnome-shell cp gnome-shell/src/* /usr/share/themes/Yaru-dark/gnome-shell Then, after restarting gnome-tweaks, there's a Yaru-dark shell theme available that gives great-looking dark toolbar menus (and, bonus, shell popup windows)! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842886 Title: Yaru-dark shell menus are not dark To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1842886/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842886] Re: Yaru-dark shell menus are not dark
Another issue with it is that if you do install a dark shell theme in Eoan, the system menu often has unreadable text. An example is pop-dark - see https://askubuntu.com/questions/1149991/dark-shell-theme-that- fits-yaru-dark. I think the menus are supposed to look something like this: https://www.deviantart.com/nayamabite/art/Equilux-Pop-Slim-Dark- mod-730578726, but instead the text in the menus is the same colour as the background until you hover over it. I suspect this is related to the changes done to make yaru the default shell theme. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842886 Title: Yaru-dark shell menus are not dark To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1842886/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842886] Re: gnome-shell top bar menus no longer honour application theme settings, eg dark themes
For me the best solution would be if Ubuntu shipped with a yaru-dark shell theme so you could make the desktop visually consistent out-of- the-box. But that's just my 2 cents... when I suggested this in another bug report about the system pop-up boxes, it wasn't received with any enthusiasm! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842886 Title: gnome-shell top bar menus no longer honour application theme settings, eg dark themes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1842886/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842886] Re: gnome-shell top bar menus no longer honour application theme settings, eg dark themes
Ok, I know what has happened. In Disco the default shell theme has dark topbar menus (and light popup windows eg ALT F2) so the topbar menus are always dark. But now in Eoan the topbar menus have changed to always be "light". See the attached screenshot, where I have selected "Try Ubuntu" from the default installer ISOs for each release. It must be an Ubuntu thing, because gnome-shell 34 still has the dark menus (eg see screenshots at https://www.omgubuntu.co.uk/2019/06/a -quick-look-at-gnome-shell-3-34-theme-improvements). I guess the devs are trying to make yaru appear everywhere, except maybe they forgot all about yaru-dark. It looks much worse IMHO, because the menus don't match the dark toolbar (and definitely don't match the applications if you choose yaru-dark). Unfortunately, Ubuntu doesn't include a dark shell theme, so you have to jump through an annoying number of hoops to get it set up to look the way you want. But then, isn't that the gnome-shell philosophy?! :) ** Attachment added: "Eoan vs Disco.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1842886/+attachment/5287050/+files/Eoan%20vs%20Disco.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842886 Title: gnome-shell top bar menus no longer honour application theme settings, eg dark themes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1842886/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842886] Re: gnome-shell top bar menus no longer honour application theme settings, eg dark themes
But user themes *is* installed and *is* working - here's a screenshot of gnome-tweaks/Extensions showing the user themes extension with no exclamation mark. It most definitely is working, because I can change the themes (application and shell themes) to my user-installed ones. I think the user themes thing is a red herring. On Disco (and until recently on Eoan), if you select, say, the adwaita-dark theme for applications, the topbar menus change to match this new application theme. This includes if you are using the default shell theme - so it works even if you don't have user themes installed. I just confirmed this on another PC running Disco. The behaviour has changed in Eoan so that the topbar menus now always use the yaru-light theme unless you change the shell theme to another. In other words, it appears that the topbar menus now renders using the system theme, whereas before it rendered using the application theme. This might be deliberate, but in my book it's a regression. If it *is* deliberate, shouldn't there be an adwaita-dark and yaru-dark theme supplied as a system shell theme? ** Attachment added: "gnome-tweaks showing user themes extension.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1842886/+attachment/5287046/+files/gnome-tweaks%20showing%20user%20themes%20extension.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842886 Title: gnome-shell top bar menus no longer honour application theme settings, eg dark themes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1842886/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842886] Re: gnome-shell top bar menus no longer honour application theme settings, eg dark themes
** Summary changed: - gnome-shell top bar menus no longer honour dark theme settings + gnome-shell top bar menus no longer honour application theme settings, eg dark themes ** Description changed: - When you selected a dark theme, the gnome-shell top bar menus used to - also switch to match the theme (ie light text on a dark background) - eg - see the screenshot showing the top-bar calendar at + When you selected a dark application theme, the gnome-shell top bar + menus used to also switch to match the theme (ie light text on a dark + background) - eg see the screenshot showing the top-bar calendar at https://micheleg.github.io/dash-to-dock/news/2015/03/01/approaching- gnome-3.16.html). This is no longer the case - see attached screenshot for yark-dark. It's the same with adwaita-dark. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.33.91-1ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9 Uname: Linux 5.2.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 5 16:01:07 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-07-01 (65 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606) RelatedPackageVersions: mutter-common 3.33.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842886 Title: gnome-shell top bar menus no longer honour application theme settings, eg dark themes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1842886/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
