[Bug 1926062] Re: [hirsute/impish] Can't turn bluetooth on again after turning it off
Bluez bug (https://github.com/bluez/bluez/issues/162) closed and fix merged in bluez. https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/?id=c939747f543a76ffd556312f753cf9d36c047c94 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1926062 Title: [hirsute/impish] Can't turn bluetooth on again after turning it off To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1926062/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1933198] Re: [nvidia] Display mode after wake-up
You can install other desktop environments by: sudo apt install unity-session sudo apt install xfce4-session etc... Then on the login screen use the icon in the bottom right corner of the screen to select which one. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1933198 Title: [nvidia] Display mode after wake-up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1933198/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1926062] Re: [hirsute/impish] Can't turn bluetooth on again after turning it off
Robie, "Fix Committed" means the fix is committed here: https://git.launchpad.net/~bluetooth/bluez/commit/?id=04298c5e46 It's part of the 5.59 release for Impish that is awaiting sponsorship (bug 1933078). Declaring "Fix Committed" when a fix exists in an upstream tributary before anything has reached proposed is a procedure requested by seb128 and we now follow on the desktop team. ** Also affects: bluez via https://github.com/bluez/bluez/issues/162 Importance: Unknown Status: Unknown ** Tags added: fixed-in-bluez-5.60 fixed-upstream -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1926062 Title: [hirsute/impish] Can't turn bluetooth on again after turning it off To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1926062/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1925742] Re: Recent iCloud versions trigger an issue in IMAP x
I tested evolution-data-server version 3.40.0-1ubuntu1.1 from proposed in Hirsute. I can confirm that iCloud accounts can be accessed again. Thanks for your work, Brian, Sebastien and Iain! ** Tags removed: verification-needed verification-needed-hirsute ** Tags added: verification-done-hirsute -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1925742 Title: Recent iCloud versions trigger an issue in IMAP x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1925742/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1931088] Re: boot-and-services tests fails in impish on armhf (248.3)
Looks like I can at least reproduce the issue on an arm64 Canonistack machine, utilizing an armhf container: ubuntu@focal-arm64:~$ time autopkgtest systemd --test-name=boot-and-services -U -- lxd autopkgtest/ubuntu/impish/armhf [...] autopkgtest [15:59:21]: test boot-and-services: [--- lxc Created symlink /etc/systemd/system/default.target → /lib/systemd/system/graphical.target. bash: line 1: 3532 Killed /tmp/autopkgtest.OAYOpR/build.yrL/src/debian/tests/boot-and-services 2> >(tee -a /tmp/autopkgtest.OAYOpR/boot-and-services-stderr >&2) > >(tee -a /tmp/autopkgtest.OAYOpR/boot-and-services-stdout) autopkgtest [15:59:24]: test process requested reboot with marker boot1 Unexpected error: Traceback (most recent call last): File "/usr/share/autopkgtest/lib/VirtSubproc.py", line 738, in mainloop command() File "/usr/share/autopkgtest/lib/VirtSubproc.py", line 667, in command r = f(c, ce) File "/usr/share/autopkgtest/lib/VirtSubproc.py", line 363, in cmd_reboot caller.hook_wait_reboot() File "/usr/bin/autopkgtest-virt-lxd", line 231, in hook_wait_reboot wait_booted() File "/usr/bin/autopkgtest-virt-lxd", line 104, in wait_booted VirtSubproc.check_exec(['lxc', 'exec', container_name, '--', 'sh', '-ec', '[ ! -d /run/systemd/system ] || systemctl start network-online.target'], timeout=60) File "/usr/share/autopkgtest/lib/VirtSubproc.py", line 182, in check_exec (status, out, err) = execute_timeout(None, timeout, real_argv, File "/usr/share/autopkgtest/lib/VirtSubproc.py", line 144, in execute_timeout (out, err) = sp.communicate(instr) File "/usr/lib/python3.8/subprocess.py", line 1014, in communicate stderr = self.stderr.read() File "/usr/share/autopkgtest/lib/VirtSubproc.py", line 64, in alarm_handler raise Timeout() VirtSubproc.Timeout autopkgtest [16:01:18]: ERROR: testbed failure: unexpected eof from the testbed real8m29.354s user0m8.866s sys 0m8.141s Let's see what we can do about it. It looks like a dnsmasq (security-)update was pushed to Bionic++ on 2021-06-02 – about the same time that this test started failing on Bionic++ ... I wonder if this might somehow be related? ... need to further investigate. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1931088 Title: boot-and-services tests fails in impish on armhf (248.3) To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/1931088/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1929650] Re: Screen doesn't turn off when using Wayland on a Thinkpad E480
Same problem on Asus Zenbook 14/Ubuntu 21.04. Backlight stays on even in Suspend mode. Did not have that problem with 20.04 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1929650 Title: Screen doesn't turn off when using Wayland on a Thinkpad E480 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1929650/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1929650] Re: Screen doesn't turn off when using Wayland on a Thinkpad E480
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mutter (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1929650 Title: Screen doesn't turn off when using Wayland on a Thinkpad E480 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1929650/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1929650] Re: Screen doesn't turn off when using Wayland on a Thinkpad E480
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-settings-daemon (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1929650 Title: Screen doesn't turn off when using Wayland on a Thinkpad E480 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1929650/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1926062] Re: [hirsute/impish] Can't turn bluetooth on again after turning it off
Also, the current upload references bug 1933221 which is a dupe. I'm not sure how SRU tooling will handle this. Unless you can confirm that it will work, please could you reference the master bug in your upload instead? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1926062 Title: [hirsute/impish] Can't turn bluetooth on again after turning it off To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-bluetooth/+bug/1926062/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1926062] Re: [hirsute/impish] Can't turn bluetooth on again after turning it off
The fix for this seems missing in Impish. What does "Fix Committed" mean here? What are your plans to fix this in Impish? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1926062 Title: [hirsute/impish] Can't turn bluetooth on again after turning it off To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-bluetooth/+bug/1926062/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1933198] Re: [nvidia] Display mode after wake-up
I would need help on how to try that, and testing it would be rather inconvenient since the problem doesn't show up every time. But if you can provide instructions I could try (sorry I'm a regular user without any technical knowledge). I can say this is a recent problem though Le mer. 23 juin 2021 à 04:15, Daniel van Vugt <1933...@bugs.launchpad.net> a écrit : > Thanks. This is a recurring issue in mutter/gnome-shell so I don't think > it's driver specific. > > To confirm if it is a mutter bug only, are you able to test some other > desktop environment(s) that use Xorg? > > ** Package changed: nvidia-graphics-drivers-460 (Ubuntu) => xorg-server > (Ubuntu) > > ** Changed in: xorg-server (Ubuntu) >Status: New => Incomplete > > ** Changed in: mutter (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1933198 > > Title: > [nvidia] Display mode after wake-up > > Status in mutter package in Ubuntu: > Incomplete > Status in xorg-server package in Ubuntu: > Incomplete > > Bug description: > My dual display setup sometimes switches to a mirror display mode > (from joined display) when waking up from sleep. > > This could be totally unrelated but I have two graphic cards, and both > screens are connected to the same one (Hdmi and display port). > > ProblemType: Bug > DistroRelease: Ubuntu 21.04 > Package: xorg 1:7.7+22ubuntu1 > ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 > Uname: Linux 5.11.0-18-generic x86_64 > NonfreeKernelModules: nvidia_modeset nvidia > .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular > file. > .proc.driver.nvidia.capabilities.gpu1: Error: path was not a regular > file. > .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. > .proc.driver.nvidia.gpus..25.00.0: Error: path was not a regular > file. > .proc.driver.nvidia.gpus..26.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 460.80 Fri May 7 > 06:55:54 UTC 2021 >GCC version: gcc version 10.3.0 (Ubuntu 10.3.0-1ubuntu1) > ApportVersion: 2.20.11-0ubuntu65.1 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' > CasperMD5CheckResult: unknown > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Tue Jun 22 09:26:34 2021 > DistUpgraded: 2021-06-09 14:41:25,219 DEBUG Running PostInstallScript: > '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' > DistroCodename: hirsute > DistroVariant: ubuntu > DkmsStatus: >nvidia, 460.80, 5.11.0-18-generic, x86_64: installed >nvidia, 460.80, 5.8.0-55-generic, x86_64: installed > ExtraDebuggingInterest: Yes, if not too technical > GraphicsCard: >NVIDIA Corporation TU106 [GeForce RTX 2060 Rev. A] [10de:1f08] (rev a1) > (prog-if 00 [VGA controller]) > Subsystem: Gigabyte Technology Co., Ltd TU106 [GeForce RTX 2060 Rev. > A] [1458:37d9] >NVIDIA Corporation GA104 [GeForce RTX 3070] [10de:2484] (rev a1) > (prog-if 00 [VGA controller]) > Subsystem: NVIDIA Corporation GA104 [GeForce RTX 3070] [10de:146b] > InstallationDate: Installed on 2021-04-16 (66 days ago) > InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 > (20201022) > MachineType: Micro-Star International Co., Ltd MS-7B86 > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=fr_FR.UTF-8 >SHELL=/bin/bash > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic > root=UUID=cbccb375-44f4-4f88-a12a-2a70cc613676 ro quiet splash vt.handoff=7 > SourcePackage: xorg > Symptom: display > UpgradeStatus: Upgraded to hirsute on 2021-06-09 (12 days ago) > dmi.bios.date: 04/18/2020 > dmi.bios.release: 5.14 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: H.60 > dmi.board.asset.tag: To be filled by O.E.M. > dmi.board.name: B450 GAMING PLUS MAX (MS-7B86) > dmi.board.vendor: Micro-Star International Co., Ltd > dmi.board.version: 3.0 > dmi.chassis.asset.tag: To be filled by O.E.M. > dmi.chassis.type: 3 > dmi.chassis.vendor: Micro-Star International Co., Ltd > dmi.chassis.version: 3.0 > dmi.modalias: > dmi:bvnAmericanMegatrendsInc.:bvrH.60:bd04/18/2020:br5.14:svnMicro-StarInternationalCo.,Ltd:pnMS-7B86:pvr3.0:rvnMicro-StarInternationalCo.,Ltd:rnB450GAMINGPLUSMAX(MS-7B86):rvr3.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr3.0: > dmi.product.family: To be filled by O.E.M. > dmi.product.name: MS-7B86 > dmi.product.sku: To be filled by O.E.M. > dmi.product.version: 3.0 > dmi.sys.vendor: Micro-Star International Co., Ltd > version.compiz: compiz N/A > version.libdrm2: libdrm2
[Bug 1926062] Re: [hirsute/impish] Can't turn bluetooth on again after turning it off
Hi @Daniel, I created a public bug in github/bluez, mp is sent by maintainer. https://github.com/bluez/bluez/issues/162 ** Bug watch added: github.com/bluez/bluez/issues #162 https://github.com/bluez/bluez/issues/162 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1926062 Title: [hirsute/impish] Can't turn bluetooth on again after turning it off To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-bluetooth/+bug/1926062/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1838720] Re: Power button action not working
Thank you for reporting this bug to Ubuntu. Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. ** Tags added: disco ** Changed in: gnome-control-center (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1838720 Title: Power button action not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1838720/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1933310] Re: power_saving_bluetooth_toggle_button disables Bluetooth instead of power saving
*** This bug is a duplicate of bug 1751954 *** https://bugs.launchpad.net/bugs/1751954 Sounds like bug 1751954 ** This bug has been marked a duplicate of bug 1751954 Bluetooth and Wi-Fi items in Power are worded ambiguously -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1933310 Title: power_saving_bluetooth_toggle_button disables Bluetooth instead of power saving To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1933310/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1933310] [NEW] power_saving_bluetooth_toggle_button disables Bluetooth instead of power saving
Public bug reported: On the Settings window Power/Power Saving/Bluetooth there is a toggle button to turn off/on for power saving. but what it does, if its on the BT is on, if you toggle it to off, the BT gets turned off instantly. And if you go to Bluetooth devices and turn BT on, and you go back to power saving window, you see the toggle button turned on. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.5-0ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 23 08:54:49 2021 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2021-03-30 (84 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** 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 Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1933310 Title: power_saving_bluetooth_toggle_button disables Bluetooth instead of power saving To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1933310/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1926062] Re: [hirsute/impish] Can't turn bluetooth on again after turning it off
** Changed in: oem-priority Importance: Undecided => Critical -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1926062 Title: [hirsute/impish] Can't turn bluetooth on again after turning it off To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-bluetooth/+bug/1926062/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1926062] Re: [hirsute/impish] Can't turn bluetooth on again after turning it off
** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Assignee: (unassigned) => Andy Chi (andch) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1926062 Title: [hirsute/impish] Can't turn bluetooth on again after turning it off To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-bluetooth/+bug/1926062/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
