[Desktop-packages] [Bug 1981117] [NEW] Bluetooth icon appears and disappears after reboot
Public bug reported: This morning I tried to use my laptop. I think it was suspended, but not deep suspended (screen off, but was attached to AC). When I tried resuming it, the screen went on, but instead of the gnome login, I was greeted by a black screen with some errors. ``` Bluetooth: hci0: Timed out waiting for suspend events Bluetooth: hci0: Suspend timeout bit: 6 Bluetooth: hci0: Suspend notifier action (3) failed: -110 ``` As I could do nothing, I rebooted the laptop (force off with power button and turned on). As I logged in, the Bluetooth indicator in the top right panel started appearing and disappearing continuously. I normally have a Bluetooth mouse connected, so I thought it was trying to pair with it. So I went into the Bluetooth tab from Settings and I was asked permission to pair the device. After allowing that permission appear / disappear issue went out. I think something is wrong with this flow. I think the service for the Bluetooth should handle these issues better, not blinking, but asking such permission that it required from the beginning. As it is it looks broken and poorly discoverable. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 Uname: Linux 5.15.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Jul 9 10:31:18 2022 InstallationDate: Installed on 2020-04-03 (826 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. XPS 15 7590 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-40-generic root=UUID=4f215b94-50a2-44af-b8c6-faf7cea8214a ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/09/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0VYV0G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd12/09/2021:br1.15:svnDellInc.:pnXPS157590:pvr:rvnDellInc.:rn0VYV0G:rvrA00:cvnDellInc.:ct10:cvr:sku0905: dmi.product.family: XPS dmi.product.name: XPS 15 7590 dmi.product.sku: 0905 dmi.sys.vendor: Dell Inc. hciconfig: hci0: Type: Primary Bus: USB BD Address: 84:C5:A6:94:9C:96 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:233857 acl:2324 sco:0 events:14387 errors:0 TX bytes:892713 acl:1283 sco:0 commands:8484 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1981117 Title: Bluetooth icon appears and disappears after reboot Status in bluez package in Ubuntu: New Bug description: This morning I tried to use my laptop. I think it was suspended, but not deep suspended (screen off, but was attached to AC). When I tried resuming it, the screen went on, but instead of the gnome login, I was greeted by a black screen with some errors. ``` Bluetooth: hci0: Timed out waiting for suspend events Bluetooth: hci0: Suspend timeout bit: 6 Bluetooth: hci0: Suspend notifier action (3) failed: -110 ``` As I could do nothing, I rebooted the laptop (force off with power button and turned on). As I logged in, the Bluetooth indicator in the top right panel started appearing and disappearing continuously. I normally have a Bluetooth mouse connected, so I thought it was trying to pair with it. So I went into the Bluetooth tab from Settings and I was asked permission to pair the device. After allowing that permission appear / disappear issue went out. I think something is wrong with this flow. I think the service for the Bluetooth should handle these issues better, not blinking, but asking such permission that it required from the beginning. As it is it looks broken and poorly discoverable. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 Uname: Linux 5.15.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Jul 9 10:31:18 2022 InstallationDate: Installed on 2020-04-03 (826 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. XPS 15 7590 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-40-generic root=UUID=4f215b94-50a2-44af-b8c6-faf7cea8214a ro quiet splash vt.handoff=7 SourcePackage:
[Desktop-packages] [Bug 1975454] [NEW] Cannot resume after suspend
Public bug reported: For some weeks I notice that my laptop cannot resume after suspend. When I try to resume it, instead of the usual password prompt, I'm greeted by a black screen with the following text: ``` Bluetooth hcio: Timed out waiting for suspend events Bluetooth hcio: Suspend timeout bit: 6 Bluetooth hcio: Suspend notifier action (3) failed: -110 ``` (There might be typos, I retyped it from a photo) Then, I don't seem able to do anything, not even change virtual terminal. So I need to reboot and lose my previous session. I noticed it seemed to happen since 22.04 came out of beta, but the timing also coincides with me starting using a Bluetooth mouse, so that might be connected. Let me know if you need more information or digging into the logs ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-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.129.06 Thu May 12 22:52:02 UTC 2022 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-19ubuntu1) ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 23 08:44:30 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/470.129.06, 5.15.0-27-generic, x86_64: installed nvidia/470.129.06, 5.15.0-30-generic, x86_64: installed virtualbox/6.1.32, 5.15.0-27-generic, x86_64: installed virtualbox/6.1.32, 5.15.0-30-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Several times a week GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Since a couple weeks or more GraphicsCard: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell CoffeeLake-H GT2 [UHD Graphics 630] [1028:0905] Subsystem: Dell TU117M [GeForce GTX 1650 Mobile / Max-Q] [1028:0905] InstallationDate: Installed on 2020-04-03 (779 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) MachineType: Dell Inc. XPS 15 7590 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic root=UUID=4f215b94-50a2-44af-b8c6-faf7cea8214a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/09/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0VYV0G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd12/09/2021:br1.15:svnDellInc.:pnXPS157590:pvr:rvnDellInc.:rn0VYV0G:rvrA00:cvnDellInc.:ct10:cvr:sku0905: dmi.product.family: XPS dmi.product.name: XPS 15 7590 dmi.product.sku: 0905 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug freeze jammy ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1975454 Title: Cannot resume after suspend Status in xorg package in Ubuntu: New Bug description: For some weeks I notice that my laptop cannot resume after suspend. When I try to resume it, instead of the usual password prompt, I'm greeted by a black screen with the following text: ``` Bluetooth hcio: Timed out waiting for suspend events Bluetooth hcio: Suspend timeout bit: 6 Bluetooth hcio: Suspend notifier action (3) failed: -110 ``` (There might be typos, I retyped it from a photo) Then, I don't seem able to do anything, not even change virtual terminal. So I need to reboot and lose my previous session.
[Desktop-packages] [Bug 1959676] [NEW] Pastes additional characters when doing copy/paste
Public bug reported: When I copy/paste some text (e.g. from the browser) into gnome-terminal, sometimes there are additional characters. E.g. I wanted to paste "sudo apt install systemd-oomd", but obtained "^[[200~sudo apt install systemd-oomd~" instead. P.S. This behaviour does not happen every time, I noticed that it seems related to me mistakenly pressing Ctrl+V instead of Ctrl+Shift+V when pasting. Not sure what it does, but it's definitely confusing. I noticed this behaviour only after updating to 22.04, I was on 20.04 before. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-terminal 3.42.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19 Uname: Linux 5.13.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Feb 1 16:24:07 2022 InstallationDate: Installed on 2020-04-03 (668 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1959676 Title: Pastes additional characters when doing copy/paste Status in gnome-terminal package in Ubuntu: New Bug description: When I copy/paste some text (e.g. from the browser) into gnome- terminal, sometimes there are additional characters. E.g. I wanted to paste "sudo apt install systemd-oomd", but obtained "^[[200~sudo apt install systemd-oomd~" instead. P.S. This behaviour does not happen every time, I noticed that it seems related to me mistakenly pressing Ctrl+V instead of Ctrl+Shift+V when pasting. Not sure what it does, but it's definitely confusing. I noticed this behaviour only after updating to 22.04, I was on 20.04 before. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-terminal 3.42.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19 Uname: Linux 5.13.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Feb 1 16:24:07 2022 InstallationDate: Installed on 2020-04-03 (668 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1959676/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1906792] Re: Chromium tabs freeze with two windows on Wayland (Xwayland)
Since few days, I'm experiencing the same behaviour under X. Shall I open a separate report for that? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1906792 Title: Chromium tabs freeze with two windows on Wayland (Xwayland) Status in Mutter: Unknown Status in mutter package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: Original description: When using Chromium (snap) on Wayland (gnome-session), if I keep two windows open on different workspaces, sometimes the current tab becomes unusable as it freezes or is super-slow. This usually happens with specific pages open, like youtube, mattermost, google drive. Minimizing one of the two windows makes the other work fine. The issues does not happen if both windows are on the same workspace. I've seen this issue in 20.04 and 20.10, always on Wayland sessions. The same behavior doesn't happen on a plain X11 session. --- Updates: As for #1916458 this behaviour may happen also on the same workspace and with Google Chrome ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.1-1ubuntu1.1 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Fri Dec 4 09:39:08 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-10-18 (46 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930) RelatedPackageVersions: mutter-common 3.38.1-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1906792/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1906792] Re: Chromium tabs freeze with two windows on Wayland (Xwayland)
I recently noted that if I put a window over the other, the bug appears, but if I put one next to the other, then everything works fine and smooth -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1906792 Title: Chromium tabs freeze with two windows on Wayland (Xwayland) Status in Mutter: Unknown Status in mutter package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: Original description: When using Chromium (snap) on Wayland (gnome-session), if I keep two windows open on different workspaces, sometimes the current tab becomes unusable as it freezes or is super-slow. This usually happens with specific pages open, like youtube, mattermost, google drive. Minimizing one of the two windows makes the other work fine. The issues does not happen if both windows are on the same workspace. I've seen this issue in 20.04 and 20.10, always on Wayland sessions. The same behavior doesn't happen on a plain X11 session. --- Updates: As for #1916458 this behaviour may happen also on the same workspace and with Google Chrome ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.1-1ubuntu1.1 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Fri Dec 4 09:39:08 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-10-18 (46 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930) RelatedPackageVersions: mutter-common 3.38.1-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1906792/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1906792] Re: Chromium tabs freeze with two windows on Wayland (Xwayland)
** Description changed: Original description: When using Chromium (snap) on Wayland (gnome-session), if I keep two windows open on different workspaces, sometimes the current tab becomes unusable as it freezes or is super-slow. This usually happens with specific pages open, like youtube, mattermost, google drive. Minimizing one of the two windows makes the other work fine. The issues does not happen if both windows are on the same workspace. I've seen this issue in 20.04 and 20.10, always on Wayland sessions. The same behavior doesn't happen on a plain X11 session. --- Updates: - As for #1916458 this behaviour may happen also on the same workspace - + As for #1916458 this behaviour may happen also on the same workspace and with Google Chrome ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.1-1ubuntu1.1 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Fri Dec 4 09:39:08 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-10-18 (46 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930) RelatedPackageVersions: mutter-common 3.38.1-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1906792 Title: Chromium tabs freeze with two windows on Wayland (Xwayland) Status in Mutter: Unknown Status in mutter package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: Original description: When using Chromium (snap) on Wayland (gnome-session), if I keep two windows open on different workspaces, sometimes the current tab becomes unusable as it freezes or is super-slow. This usually happens with specific pages open, like youtube, mattermost, google drive. Minimizing one of the two windows makes the other work fine. The issues does not happen if both windows are on the same workspace. I've seen this issue in 20.04 and 20.10, always on Wayland sessions. The same behavior doesn't happen on a plain X11 session. --- Updates: As for #1916458 this behaviour may happen also on the same workspace and with Google Chrome ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.1-1ubuntu1.1 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Fri Dec 4 09:39:08 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-10-18 (46 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930) RelatedPackageVersions: mutter-common 3.38.1-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1906792/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1906792] Re: Chromium tabs freeze with two windows on Wayland (Xwayland)
** Description changed: - When using Chromium (snap) on Wayland (gnome-session), if I keep two - windows open on different workspaces, sometimes the current tab becomes - unusable as it freezes or is super-slow. + Original description: + When using Chromium (snap) on Wayland (gnome-session), if I keep two windows open on different workspaces, sometimes the current tab becomes unusable as it freezes or is super-slow. This usually happens with specific pages open, like youtube, mattermost, google drive. Minimizing one of the two windows makes the other work fine. The issues does not happen if both windows are on the same workspace. I've seen this issue in 20.04 and 20.10, always on Wayland sessions. The same behavior doesn't happen on a plain X11 session. + + --- + + Updates: + As for #1916458 this behaviour may happen also on the same workspace + ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.1-1ubuntu1.1 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Fri Dec 4 09:39:08 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-10-18 (46 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930) RelatedPackageVersions: mutter-common 3.38.1-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1906792 Title: Chromium tabs freeze with two windows on Wayland (Xwayland) Status in Mutter: Unknown Status in mutter package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: Original description: When using Chromium (snap) on Wayland (gnome-session), if I keep two windows open on different workspaces, sometimes the current tab becomes unusable as it freezes or is super-slow. This usually happens with specific pages open, like youtube, mattermost, google drive. Minimizing one of the two windows makes the other work fine. The issues does not happen if both windows are on the same workspace. I've seen this issue in 20.04 and 20.10, always on Wayland sessions. The same behavior doesn't happen on a plain X11 session. --- Updates: As for #1916458 this behaviour may happen also on the same workspace ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.1-1ubuntu1.1 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Fri Dec 4 09:39:08 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-10-18 (46 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930) RelatedPackageVersions: mutter-common 3.38.1-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1906792/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1916458] Re: Chrome on Wayland: having more than one window makes it stutter
*** This bug is a duplicate of bug 1906792 *** https://bugs.launchpad.net/bugs/1906792 Hi, Daniel, I'm not sure if this is the same bug, because: 1. Minimizing one of the two windows doesn't always make the other work fine, only sometimes. 2. The issues DOES happen if both windows are on the same workspace. Especially point 2 makes me think it might be something different 樂 ** Description changed: If I'm using Chrome (Version 88.0.4324.182 (Official Build) (64-bit)) under Wayland, and I pick a tab, and drag it out of the current window, it correctly creates a new window. But this new window has performance issues, and often freezes for a few seconds while using it. The original window seems to be affected as well, but to a lesser degree, in my experiments. Other windows seem to be unaffected. I also checked it was not a one-session problem, so I logged-out and back in, tried again, same result. This behaviour renders Chrome very poorly usable when this happens. Update: Closing any additional window, makes Chrome work smoothly again. The same issue happens when opening a new window from the panel or from the menu, so the issue appears to be about handling more than one window. Doing the same on X doesn't result in any apparent performance degradation. - Chromium (Version 88.0.4324.182 (Official Build) snap (64-bit)) and - Firefox (85.0.1 (64-bit)) don't appear to have the same issue. + Works fine on: + - Chromium (Version 88.0.4324.182 (Official Build) snap (64-bit)) + - Firefox (85.0.1 (64-bit)) + - Microsoft Edge (Version 90.0.796.0 (Official build) dev (64-bit)) --- Affects: - Chrome Stable: Version 88.0.4324.182 (Official Build) (64-bit) - Chrome Dev: Version 90.0.4421.5 (Official Build) dev (64-bit) + - Chrome Stable: Version 88.0.4324.182 (Official Build) (64-bit) + - Chrome Dev: Version 90.0.4421.5 (Official Build) dev (64-bit) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Feb 22 11:24:08 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-03 (324 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.apport.crashdb.conf: 2020-09-16T18:33:51.843197 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1916458 Title: Chrome on Wayland: having more than one window makes it stutter Status in gnome-shell package in Ubuntu: New Bug description: If I'm using Chrome (Version 88.0.4324.182 (Official Build) (64-bit)) under Wayland, and I pick a tab, and drag it out of the current window, it correctly creates a new window. But this new window has performance issues, and often freezes for a few seconds while using it. The original window seems to be affected as well, but to a lesser degree, in my experiments. Other windows seem to be unaffected. I also checked it was not a one-session problem, so I logged-out and back in, tried again, same result. This behaviour renders Chrome very poorly usable when this happens. Update: Closing any additional window, makes Chrome work smoothly again. The same issue happens when opening a new window from the panel or from the menu, so the issue appears to be about handling more than one window. Doing the same on X doesn't result in any apparent performance degradation. Works fine on: - Chromium (Version 88.0.4324.182 (Official Build) snap (64-bit)) - Firefox (85.0.1 (64-bit)) - Microsoft Edge (Version 90.0.796.0 (Official build) dev (64-bit)) --- Affects: - Chrome Stable: Version 88.0.4324.182 (Official Build) (64-bit) - Chrome Dev: Version 90.0.4421.5 (Official Build) dev (64-bit) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Feb 22 11:24:08 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-03 (324 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.apport.crashdb.conf: 2020-09-16T18:33:51.843197 To manage notifications
[Desktop-packages] [Bug 1916458] Re: Chrome on Wayland: having more than one window makes it stutter
*** This bug is a duplicate of bug 1906792 *** https://bugs.launchpad.net/bugs/1906792 ** Description changed: If I'm using Chrome (Version 88.0.4324.182 (Official Build) (64-bit)) under Wayland, and I pick a tab, and drag it out of the current window, it correctly creates a new window. But this new window has performance issues, and often freezes for a few seconds while using it. The original window seems to be affected as well, but to a lesser degree, in my experiments. Other windows seem to be unaffected. I also checked it was not a one-session problem, so I logged-out and back in, tried again, same result. This behaviour renders Chrome very poorly usable when this happens. Update: Closing any additional window, makes Chrome work smoothly again. The same issue happens when opening a new window from the panel or from the menu, so the issue appears to be about handling more than one window. Doing the same on X doesn't result in any apparent performance degradation. Chromium (Version 88.0.4324.182 (Official Build) snap (64-bit)) and Firefox (85.0.1 (64-bit)) don't appear to have the same issue. + --- - - Chrome Version 88.0.4324.182 (Official Build) (64-bit) + Affects: + Chrome Stable: Version 88.0.4324.182 (Official Build) (64-bit) + Chrome Dev: Version 90.0.4421.5 (Official Build) dev (64-bit) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Feb 22 11:24:08 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-03 (324 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.apport.crashdb.conf: 2020-09-16T18:33:51.843197 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1916458 Title: Chrome on Wayland: having more than one window makes it stutter Status in gnome-shell package in Ubuntu: New Bug description: If I'm using Chrome (Version 88.0.4324.182 (Official Build) (64-bit)) under Wayland, and I pick a tab, and drag it out of the current window, it correctly creates a new window. But this new window has performance issues, and often freezes for a few seconds while using it. The original window seems to be affected as well, but to a lesser degree, in my experiments. Other windows seem to be unaffected. I also checked it was not a one-session problem, so I logged-out and back in, tried again, same result. This behaviour renders Chrome very poorly usable when this happens. Update: Closing any additional window, makes Chrome work smoothly again. The same issue happens when opening a new window from the panel or from the menu, so the issue appears to be about handling more than one window. Doing the same on X doesn't result in any apparent performance degradation. Chromium (Version 88.0.4324.182 (Official Build) snap (64-bit)) and Firefox (85.0.1 (64-bit)) don't appear to have the same issue. --- Affects: Chrome Stable: Version 88.0.4324.182 (Official Build) (64-bit) Chrome Dev: Version 90.0.4421.5 (Official Build) dev (64-bit) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Feb 22 11:24:08 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-03 (324 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.apport.crashdb.conf: 2020-09-16T18:33:51.843197 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1916458/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1916458] Re: Chrome on Wayland: having more than one window makes it stutter
*** This bug is a duplicate of bug 1906792 *** https://bugs.launchpad.net/bugs/1906792 Update: Tested in Chromium (latest snap) and Firefox, no issue when opening multiple windows. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1916458 Title: Chrome on Wayland: having more than one window makes it stutter Status in gnome-shell package in Ubuntu: New Bug description: If I'm using Chrome (Version 88.0.4324.182 (Official Build) (64-bit)) under Wayland, and I pick a tab, and drag it out of the current window, it correctly creates a new window. But this new window has performance issues, and often freezes for a few seconds while using it. The original window seems to be affected as well, but to a lesser degree, in my experiments. Other windows seem to be unaffected. I also checked it was not a one-session problem, so I logged-out and back in, tried again, same result. This behaviour renders Chrome very poorly usable when this happens. Update: Closing any additional window, makes Chrome work smoothly again. The same issue happens when opening a new window from the panel or from the menu, so the issue appears to be about handling more than one window. Doing the same on X doesn't result in any apparent performance degradation. Chromium (Version 88.0.4324.182 (Official Build) snap (64-bit)) and Firefox (85.0.1 (64-bit)) don't appear to have the same issue. Chrome Version 88.0.4324.182 (Official Build) (64-bit) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Feb 22 11:24:08 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-03 (324 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.apport.crashdb.conf: 2020-09-16T18:33:51.843197 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1916458/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1916458] Re: Chrome on Wayland: having more than one window makes it stutter
*** This bug is a duplicate of bug 1906792 *** https://bugs.launchpad.net/bugs/1906792 ** Description changed: - If I'm using Chrome under Wayland, and I pick a tab, and drag it out of - the current window, it correctly creates a new window. But this new - window has performance issues, and often freezes for a few seconds while - using it. The original window seems to be affected as well, but to a - lesser degree, in my experiments. Other windows seem to be unaffected. + If I'm using Chrome (Version 88.0.4324.182 (Official Build) (64-bit)) + under Wayland, and I pick a tab, and drag it out of the current window, + it correctly creates a new window. But this new window has performance + issues, and often freezes for a few seconds while using it. The original + window seems to be affected as well, but to a lesser degree, in my + experiments. Other windows seem to be unaffected. I also checked it was not a one-session problem, so I logged-out and back in, tried again, same result. This behaviour renders Chrome very poorly usable when this happens. Update: Closing any additional window, makes Chrome work smoothly again. The same issue happens when opening a new window from the panel or from the menu, so the issue appears to be about handling more than one window. Doing the same on X doesn't result in any apparent performance degradation. + + Chromium (Version 88.0.4324.182 (Official Build) snap (64-bit)) and + Firefox (85.0.1 (64-bit)) don't appear to have the same issue. + + + + Chrome Version 88.0.4324.182 (Official Build) (64-bit) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Feb 22 11:24:08 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-03 (324 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.apport.crashdb.conf: 2020-09-16T18:33:51.843197 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1916458 Title: Chrome on Wayland: having more than one window makes it stutter Status in gnome-shell package in Ubuntu: New Bug description: If I'm using Chrome (Version 88.0.4324.182 (Official Build) (64-bit)) under Wayland, and I pick a tab, and drag it out of the current window, it correctly creates a new window. But this new window has performance issues, and often freezes for a few seconds while using it. The original window seems to be affected as well, but to a lesser degree, in my experiments. Other windows seem to be unaffected. I also checked it was not a one-session problem, so I logged-out and back in, tried again, same result. This behaviour renders Chrome very poorly usable when this happens. Update: Closing any additional window, makes Chrome work smoothly again. The same issue happens when opening a new window from the panel or from the menu, so the issue appears to be about handling more than one window. Doing the same on X doesn't result in any apparent performance degradation. Chromium (Version 88.0.4324.182 (Official Build) snap (64-bit)) and Firefox (85.0.1 (64-bit)) don't appear to have the same issue. Chrome Version 88.0.4324.182 (Official Build) (64-bit) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Feb 22 11:24:08 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-03 (324 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.apport.crashdb.conf: 2020-09-16T18:33:51.843197 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1916458/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1916458] Re: Wayland: Using Chrome, taking a tab out in a new window makes it stutter
Update: Closing any additional window, makes Chrome work smoothly again. The same issue happens when opening a new window from the panel or from the menu, so the issue appears to be about handling more than one window. ** Summary changed: - Wayland: Using Chrome, taking a tab out in a new window makes it stutter + Chrome on Wayland: having more than one window makes it stutter ** Description changed: If I'm using Chrome under Wayland, and I pick a tab, and drag it out of the current window, it correctly creates a new window. But this new window has performance issues, and often freezes for a few seconds while using it. The original window seems to be affected as well, but to a lesser degree, in my experiments. Other windows seem to be unaffected. I also checked it was not a one-session problem, so I logged-out and back in, tried again, same result. This behaviour renders Chrome very poorly usable when this happens. + + Update: + Closing any additional window, makes Chrome work smoothly again. + + The same issue happens when opening a new window from the panel or from + the menu, so the issue appears to be about handling more than one + window. + + Doing the same on X doesn't result in any apparent performance + degradation. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Feb 22 11:24:08 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-03 (324 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.apport.crashdb.conf: 2020-09-16T18:33:51.843197 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1916458 Title: Chrome on Wayland: having more than one window makes it stutter Status in gnome-shell package in Ubuntu: New Bug description: If I'm using Chrome under Wayland, and I pick a tab, and drag it out of the current window, it correctly creates a new window. But this new window has performance issues, and often freezes for a few seconds while using it. The original window seems to be affected as well, but to a lesser degree, in my experiments. Other windows seem to be unaffected. I also checked it was not a one-session problem, so I logged-out and back in, tried again, same result. This behaviour renders Chrome very poorly usable when this happens. Update: Closing any additional window, makes Chrome work smoothly again. The same issue happens when opening a new window from the panel or from the menu, so the issue appears to be about handling more than one window. Doing the same on X doesn't result in any apparent performance degradation. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Feb 22 11:24:08 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-03 (324 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.apport.crashdb.conf: 2020-09-16T18:33:51.843197 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1916458/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1916458] [NEW] Chrome on Wayland: having more than one window makes it stutter
Public bug reported: If I'm using Chrome under Wayland, and I pick a tab, and drag it out of the current window, it correctly creates a new window. But this new window has performance issues, and often freezes for a few seconds while using it. The original window seems to be affected as well, but to a lesser degree, in my experiments. Other windows seem to be unaffected. I also checked it was not a one-session problem, so I logged-out and back in, tried again, same result. This behaviour renders Chrome very poorly usable when this happens. Update: Closing any additional window, makes Chrome work smoothly again. The same issue happens when opening a new window from the panel or from the menu, so the issue appears to be about handling more than one window. Doing the same on X doesn't result in any apparent performance degradation. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Feb 22 11:24:08 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-03 (324 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.apport.crashdb.conf: 2020-09-16T18:33:51.843197 ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1916458 Title: Chrome on Wayland: having more than one window makes it stutter Status in gnome-shell package in Ubuntu: New Bug description: If I'm using Chrome under Wayland, and I pick a tab, and drag it out of the current window, it correctly creates a new window. But this new window has performance issues, and often freezes for a few seconds while using it. The original window seems to be affected as well, but to a lesser degree, in my experiments. Other windows seem to be unaffected. I also checked it was not a one-session problem, so I logged-out and back in, tried again, same result. This behaviour renders Chrome very poorly usable when this happens. Update: Closing any additional window, makes Chrome work smoothly again. The same issue happens when opening a new window from the panel or from the menu, so the issue appears to be about handling more than one window. Doing the same on X doesn't result in any apparent performance degradation. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Feb 22 11:24:08 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-03 (324 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.apport.crashdb.conf: 2020-09-16T18:33:51.843197 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1916458/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870794] Re: Missing some unicode 13 emojis
If I get it correctly, in order to backport this, including sequences, there should be at least 2 SRU: - 1 for fonts-noto-color-emoji, with the latest emojis - 1 for pango, with those 2 commits Did I get it correctly? If yes, we could first SRU fonts-noto-color-emoji package and pango later to bring the sequences. I can check if I can work on that on late next month. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fonts-noto-color-emoji in Ubuntu. https://bugs.launchpad.net/bugs/1870794 Title: Missing some unicode 13 emojis Status in fonts-noto-color-emoji package in Ubuntu: Fix Released Bug description: The current version is missing some emojis which are already available upstream. I didn't check them all but it seems they are v13 emojis. You can see the missing ones as tofu from here: https://unicode.org/emoji/charts/full-emoji-list.html ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: fonts-noto-color-emoji 0~20191119-1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Apr 4 17:25:41 2020 Dependencies: InstallationDate: Installed on 2020-04-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) PackageArchitecture: all SourcePackage: fonts-noto-color-emoji UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-noto-color-emoji/+bug/1870794/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870794] Re: Missing some unicode 13 emojis
** Summary changed: - Update for Unicode 13 + Missing some unicode 13 emojis -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fonts-noto-color-emoji in Ubuntu. https://bugs.launchpad.net/bugs/1870794 Title: Missing some unicode 13 emojis Status in fonts-noto-color-emoji package in Ubuntu: Fix Released Bug description: The current version is missing some emojis which are already available upstream. I didn't check them all but it seems they are v13 emojis. You can see the missing ones as tofu from here: https://unicode.org/emoji/charts/full-emoji-list.html ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: fonts-noto-color-emoji 0~20191119-1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Apr 4 17:25:41 2020 Dependencies: InstallationDate: Installed on 2020-04-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) PackageArchitecture: all SourcePackage: fonts-noto-color-emoji UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-noto-color-emoji/+bug/1870794/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1894437] [NEW] Nautilus does not release memory
Public bug reported: I copied a large amount of files, viewed many thumbnails and done other activities which may possibly require allocating more memory in the system. I reached 6.6GB of memory. Then I closed all nautilus windows, but the memory usage didn't lower. I would have expected that after closing all nautilus windows it would have reduced to normal levels, but it didn't. I don't think this is normal. Memory usage was checked on gnome-system-monitor. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Sun Sep 6 18:28:50 2020 InstallationDate: Installed on 2020-04-03 (155 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.apport.crashdb.conf: 2020-05-04T09:26:46.106768 usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1894437 Title: Nautilus does not release memory Status in nautilus package in Ubuntu: New Bug description: I copied a large amount of files, viewed many thumbnails and done other activities which may possibly require allocating more memory in the system. I reached 6.6GB of memory. Then I closed all nautilus windows, but the memory usage didn't lower. I would have expected that after closing all nautilus windows it would have reduced to normal levels, but it didn't. I don't think this is normal. Memory usage was checked on gnome-system-monitor. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Sun Sep 6 18:28:50 2020 InstallationDate: Installed on 2020-04-03 (155 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.apport.crashdb.conf: 2020-05-04T09:26:46.106768 usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1894437/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1878076] [NEW] GTK save-dialogs input-focus moves from filename to file search if a folder is selected
Public bug reported: This bug is also reported on GNOME's GTK GitLab: https://gitlab.gnome.org/GNOME/gtk/issues/326 ## Steps to reproduce 1. Open any GTK app which uses save dialogs (e.g. gedit) 2. Press save 3. A save dialog appears and the filename is highlighted (if typing at this point you edit the file name) 4. Click on a different folder (e.g. Downloads) 5. The filename is still highlighted, hinting that the focus is still there 6. Type and find yourself searching for a file in the selected folder -- Current behavior -- The higlighting (on the file name) hints a focus which is not the actual input focus, and the actual input focus (the search bar) is hidden until one starts to type, which I think to be confusing and unexpected. Also, clicking back on the highlighted filename you lose the highlighting, so you have to highlight again some already highlighted text; I think this to be confusing and counterintuitive. -- Expected outcome -- Highlighting and focus need to match. If they don't that's a UX bug, and there are several options to solve it, some examples: - keep highlighting as is and keep focus on the filename, this whould require finding a different path for file search (I think this is the most productive option, because I assume a user wants to change the folder and eventually rename or name the file, which I consider more likely than a user wanting to search for a file within a save-file dialog); - keep filesearch as is, but show its bar before typing begins, and remove any highlighting from filename. For reference, Windows 10's native save-file dialogs disables the highlighting when clicking on a different folder. Typing does nothing at that point. Tested on gedit 3.36.1 on Ubuntu 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgtk-3-0 3.24.18-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon May 11 21:53:37 2020 InstallationDate: Installed on 2020-04-03 (37 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.apport.crashdb.conf: 2020-05-04T10:26:46.106768 ** Affects: gtk Importance: Unknown Status: Unknown ** Affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Bug watch added: gitlab.gnome.org/GNOME/gtk/issues #326 https://gitlab.gnome.org/GNOME/gtk/issues/326 ** Also affects: gtk via https://gitlab.gnome.org/GNOME/gtk/issues/326 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1878076 Title: GTK save-dialogs input-focus moves from filename to file search if a folder is selected Status in GTK+: Unknown Status in gtk+3.0 package in Ubuntu: New Bug description: This bug is also reported on GNOME's GTK GitLab: https://gitlab.gnome.org/GNOME/gtk/issues/326 ## Steps to reproduce 1. Open any GTK app which uses save dialogs (e.g. gedit) 2. Press save 3. A save dialog appears and the filename is highlighted (if typing at this point you edit the file name) 4. Click on a different folder (e.g. Downloads) 5. The filename is still highlighted, hinting that the focus is still there 6. Type and find yourself searching for a file in the selected folder -- Current behavior -- The higlighting (on the file name) hints a focus which is not the actual input focus, and the actual input focus (the search bar) is hidden until one starts to type, which I think to be confusing and unexpected. Also, clicking back on the highlighted filename you lose the highlighting, so you have to highlight again some already highlighted text; I think this to be confusing and counterintuitive. -- Expected outcome -- Highlighting and focus need to match. If they don't that's a UX bug, and there are several options to solve it, some examples: - keep highlighting as is and keep focus on the filename, this whould require finding a different path for file search (I think this is the most productive option, because I assume a user wants to change the folder and eventually rename or name the file, which I consider more likely than a user wanting to search for a file within a save-file dialog); - keep filesearch as is, but show its bar before typing begins, and remove any highlighting from filename. For reference, Windows 10's native save-file dialogs disables the highlighting when clicking on a different folder. Typing does nothing at that point. Tested on gedit 3.36.1 on Ubuntu 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package:
[Desktop-packages] [Bug 1876879] Re: gnome-software cannot install classic snaps if a channel is selected
** Attachment added: "Screenshot-20200505111850-1252x899.png" https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1876879/+attachment/5366681/+files/Screenshot-20200505111850-1252x899.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1876879 Title: gnome-software cannot install classic snaps if a channel is selected Status in gnome-software package in Ubuntu: New Bug description: I tried installing Android Studio from gnome-software. In the top right dropdown, it asks for the source. For Andoid Studio it displays Ubuntu. I was suspicious of it being a deb and not a snap. So I clicked on it and it shown me 3 Snap channel options. I selected latest/stable. The source changed according to my selection. Then I tried installing it but it failed saying: Unable to install "Android Studio": snap "android-studio" requires classic confinement I was puzzled. So I went back to the search menu, I clicked again on Android Studio and the source was now again on Ubuntu (note that this is not an option available in the dropdown). I checked the details and indeed it's the snap package from channel latest/stable, just the source is somehow misleading. Now it installed the software without issues. What doesn't work: - Source dropdown (top-right) shows "Ubuntu" instead of the snap channel - Selecting a channel breaks the install functionality for classic snaps (it seems like it attempts to install them without --classic) Workaround: Do not select any channel, just use what is provided, and it works. If needing to use a different channel, use the command line (or perhaps check if this works in the Snap Store, if it has not the same issue). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-software 3.36.0-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Tue May 5 11:09:26 2020 InstallationDate: Installed on 2020-04-03 (31 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) InstalledPlugins: gnome-software-plugin-flatpak 3.36.0-0ubuntu3 gnome-software-plugin-snap3.36.0-0ubuntu3 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2020-05-04T10:26:46.106768 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1876879/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876879] [NEW] gnome-software cannot install classic snaps if a channel is selected
Public bug reported: I tried installing Android Studio from gnome-software. In the top right dropdown, it asks for the source. For Andoid Studio it displays Ubuntu. I was suspicious of it being a deb and not a snap. So I clicked on it and it shown me 3 Snap channel options. I selected latest/stable. The source changed according to my selection. Then I tried installing it but it failed saying: Unable to install "Android Studio": snap "android-studio" requires classic confinement I was puzzled. So I went back to the search menu, I clicked again on Android Studio and the source was now again on Ubuntu (note that this is not an option available in the dropdown). I checked the details and indeed it's the snap package from channel latest/stable, just the source is somehow misleading. Now it installed the software without issues. What doesn't work: - Source dropdown (top-right) shows "Ubuntu" instead of the snap channel - Selecting a channel breaks the install functionality for classic snaps (it seems like it attempts to install them without --classic) Workaround: Do not select any channel, just use what is provided, and it works. If needing to use a different channel, use the command line (or perhaps check if this works in the Snap Store, if it has not the same issue). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-software 3.36.0-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Tue May 5 11:09:26 2020 InstallationDate: Installed on 2020-04-03 (31 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) InstalledPlugins: gnome-software-plugin-flatpak 3.36.0-0ubuntu3 gnome-software-plugin-snap3.36.0-0ubuntu3 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2020-05-04T10:26:46.106768 ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "Screenshot-20200505111815-1252x899.png" https://bugs.launchpad.net/bugs/1876879/+attachment/5366676/+files/Screenshot-20200505111815-1252x899.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1876879 Title: gnome-software cannot install classic snaps if a channel is selected Status in gnome-software package in Ubuntu: New Bug description: I tried installing Android Studio from gnome-software. In the top right dropdown, it asks for the source. For Andoid Studio it displays Ubuntu. I was suspicious of it being a deb and not a snap. So I clicked on it and it shown me 3 Snap channel options. I selected latest/stable. The source changed according to my selection. Then I tried installing it but it failed saying: Unable to install "Android Studio": snap "android-studio" requires classic confinement I was puzzled. So I went back to the search menu, I clicked again on Android Studio and the source was now again on Ubuntu (note that this is not an option available in the dropdown). I checked the details and indeed it's the snap package from channel latest/stable, just the source is somehow misleading. Now it installed the software without issues. What doesn't work: - Source dropdown (top-right) shows "Ubuntu" instead of the snap channel - Selecting a channel breaks the install functionality for classic snaps (it seems like it attempts to install them without --classic) Workaround: Do not select any channel, just use what is provided, and it works. If needing to use a different channel, use the command line (or perhaps check if this works in the Snap Store, if it has not the same issue). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-software 3.36.0-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Tue May 5 11:09:26 2020 InstallationDate: Installed on 2020-04-03 (31 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) InstalledPlugins: gnome-software-plugin-flatpak 3.36.0-0ubuntu3 gnome-software-plugin-snap3.36.0-0ubuntu3 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2020-05-04T10:26:46.106768 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1876879/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to
[Desktop-packages] [Bug 1876871] [NEW] gnome-software cannot find snaps suggested from shell search
Public bug reported: Searching for Android Studio in the shell, thinking it was already installed, I got a suggetion for installing it from gnome-software. It opened gnome-software but it says: Unable to find "system/snap/Snap Store/desktop/-io.snapcraft.android- studio-VNTeli51l6clZ1gaWHwx0PoP7JaCb61c/latest/stable" It makes me think that it was trying to open the snap Snap Store (which is not installed on my system). I think in the focal transition for having Snap Store as the default store, something was changed in the way snap suggestions are handled to suggest the Snap Store instead of gnome- software. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-software 3.36.0-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Tue May 5 10:49:22 2020 InstallationDate: Installed on 2020-04-03 (31 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) InstalledPlugins: gnome-software-plugin-flatpak 3.36.0-0ubuntu3 gnome-software-plugin-snap3.36.0-0ubuntu3 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2020-05-04T10:26:46.106768 ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1876871 Title: gnome-software cannot find snaps suggested from shell search Status in gnome-software package in Ubuntu: New Bug description: Searching for Android Studio in the shell, thinking it was already installed, I got a suggetion for installing it from gnome-software. It opened gnome-software but it says: Unable to find "system/snap/Snap Store/desktop/-io.snapcraft.android- studio-VNTeli51l6clZ1gaWHwx0PoP7JaCb61c/latest/stable" It makes me think that it was trying to open the snap Snap Store (which is not installed on my system). I think in the focal transition for having Snap Store as the default store, something was changed in the way snap suggestions are handled to suggest the Snap Store instead of gnome-software. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-software 3.36.0-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Tue May 5 10:49:22 2020 InstallationDate: Installed on 2020-04-03 (31 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) InstalledPlugins: gnome-software-plugin-flatpak 3.36.0-0ubuntu3 gnome-software-plugin-snap3.36.0-0ubuntu3 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2020-05-04T10:26:46.106768 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1876871/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876871] Re: gnome-software cannot find snaps suggested from shell search
Screenshot ** Attachment added: "Screenshot-20200505105558-1252x899.png" https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1876871/+attachment/5366671/+files/Screenshot-20200505105558-1252x899.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1876871 Title: gnome-software cannot find snaps suggested from shell search Status in gnome-software package in Ubuntu: New Bug description: Searching for Android Studio in the shell, thinking it was already installed, I got a suggetion for installing it from gnome-software. It opened gnome-software but it says: Unable to find "system/snap/Snap Store/desktop/-io.snapcraft.android- studio-VNTeli51l6clZ1gaWHwx0PoP7JaCb61c/latest/stable" It makes me think that it was trying to open the snap Snap Store (which is not installed on my system). I think in the focal transition for having Snap Store as the default store, something was changed in the way snap suggestions are handled to suggest the Snap Store instead of gnome-software. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-software 3.36.0-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Tue May 5 10:49:22 2020 InstallationDate: Installed on 2020-04-03 (31 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) InstalledPlugins: gnome-software-plugin-flatpak 3.36.0-0ubuntu3 gnome-software-plugin-snap3.36.0-0ubuntu3 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2020-05-04T10:26:46.106768 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1876871/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876879] Re: gnome-software cannot install classic snaps if a channel is selected
** Attachment added: "Screenshot-20200505111956-1252x899.png" https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1876879/+attachment/5366682/+files/Screenshot-20200505111956-1252x899.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1876879 Title: gnome-software cannot install classic snaps if a channel is selected Status in gnome-software package in Ubuntu: New Bug description: I tried installing Android Studio from gnome-software. In the top right dropdown, it asks for the source. For Andoid Studio it displays Ubuntu. I was suspicious of it being a deb and not a snap. So I clicked on it and it shown me 3 Snap channel options. I selected latest/stable. The source changed according to my selection. Then I tried installing it but it failed saying: Unable to install "Android Studio": snap "android-studio" requires classic confinement I was puzzled. So I went back to the search menu, I clicked again on Android Studio and the source was now again on Ubuntu (note that this is not an option available in the dropdown). I checked the details and indeed it's the snap package from channel latest/stable, just the source is somehow misleading. Now it installed the software without issues. What doesn't work: - Source dropdown (top-right) shows "Ubuntu" instead of the snap channel - Selecting a channel breaks the install functionality for classic snaps (it seems like it attempts to install them without --classic) Workaround: Do not select any channel, just use what is provided, and it works. If needing to use a different channel, use the command line (or perhaps check if this works in the Snap Store, if it has not the same issue). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-software 3.36.0-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Tue May 5 11:09:26 2020 InstallationDate: Installed on 2020-04-03 (31 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) InstalledPlugins: gnome-software-plugin-flatpak 3.36.0-0ubuntu3 gnome-software-plugin-snap3.36.0-0ubuntu3 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2020-05-04T10:26:46.106768 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1876879/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1874107] Re: qt theming issue: error 6 in libgdk-x11-2.0.so
# Symple application failing
import sys
from PySide2.QtWidgets import QApplication, QDialog, QLineEdit, QPushButton
class Form(QDialog):
def __init__(self, parent=None):
super(Form, self).__init__(parent)
self.setWindowTitle("My Form")
if __name__ == '__main__':
# Create the Qt Application
app = QApplication(sys.argv)
app.setStyle('gtk2')
# Create and show the form
form = Form()
form.show()
# Run the main Qt loop
sys.exit(app.exec_())
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtk+2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1874107
Title:
qt theming issue: error 6 in libgdk-x11-2.0.so
Status in gtk+2.0 package in Ubuntu:
New
Bug description:
As for related bug
https://bugs.launchpad.net/ubuntu/+source/qtstyleplugins-src/+bug/1874102 ,
theming a qt application with the "gtk2" theme causes the app to crash with
segfault:
```
segfault at 114 ip 7f0439c6caa5 sp 7fff05b55770 error 6 in
libgdk-x11-2.0.so.0.2400.32[7f0439c36000+5e000]
```
Also the following code is available:
```
Code: 64 24 10 4c 8d 6c 24 40 e8 d8 fe ff ff 31 f6 48 8d 5c 24 38 48 89 c7 31
c0 e8 77 c9 fc ff 31 d2 48 8d 35 0e fe ff ff 48 89 ef 80 14 01 00 00 01 00
00 00 49 89 c7 48 89 a8 d8 00 00 00 e8 12
```
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: libgtk2.0-0 2.24.32-4ubuntu4
ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30
Uname: Linux 5.4.0-24-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: GNOME
Date: Tue Apr 21 18:08:47 2020
InstallationDate: Installed on 2020-04-03 (17 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401)
SourcePackage: gtk+2.0
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1874107/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1874107] Re: qt theming issue: error 6 in libgdk-x11-2.0.so
You need the following packages to run the script: sudo apt install libpyside2-py3-5.14 python3-pyside2.qtcore python3-pyside2.qtuitools python3-pyside2.qtwidgets qt5-style-plugins qt5-gtk2-platformtheme -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1874107 Title: qt theming issue: error 6 in libgdk-x11-2.0.so Status in gtk+2.0 package in Ubuntu: New Bug description: As for related bug https://bugs.launchpad.net/ubuntu/+source/qtstyleplugins-src/+bug/1874102 , theming a qt application with the "gtk2" theme causes the app to crash with segfault: ``` segfault at 114 ip 7f0439c6caa5 sp 7fff05b55770 error 6 in libgdk-x11-2.0.so.0.2400.32[7f0439c36000+5e000] ``` Also the following code is available: ``` Code: 64 24 10 4c 8d 6c 24 40 e8 d8 fe ff ff 31 f6 48 8d 5c 24 38 48 89 c7 31 c0 e8 77 c9 fc ff 31 d2 48 8d 35 0e fe ff ff 48 89 ef 80 14 01 00 00 01 00 00 00 49 89 c7 48 89 a8 d8 00 00 00 e8 12 ``` ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgtk2.0-0 2.24.32-4ubuntu4 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Tue Apr 21 18:08:47 2020 InstallationDate: Installed on 2020-04-03 (17 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) SourcePackage: gtk+2.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1874107/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1874107] [NEW] qt theming issue: error 6 in libgdk-x11-2.0.so
Public bug reported: As for related bug https://bugs.launchpad.net/ubuntu/+source/qtstyleplugins-src/+bug/1874102 , theming a qt application with the "gtk2" theme causes the app to crash with segfault: ``` segfault at 114 ip 7f0439c6caa5 sp 7fff05b55770 error 6 in libgdk-x11-2.0.so.0.2400.32[7f0439c36000+5e000] ``` Also the following code is available: ``` Code: 64 24 10 4c 8d 6c 24 40 e8 d8 fe ff ff 31 f6 48 8d 5c 24 38 48 89 c7 31 c0 e8 77 c9 fc ff 31 d2 48 8d 35 0e fe ff ff 48 89 ef 80 14 01 00 00 01 00 00 00 49 89 c7 48 89 a8 d8 00 00 00 e8 12 ``` ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgtk2.0-0 2.24.32-4ubuntu4 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Tue Apr 21 18:08:47 2020 InstallationDate: Installed on 2020-04-03 (17 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) SourcePackage: gtk+2.0 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gtk+2.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1874107 Title: qt theming issue: error 6 in libgdk-x11-2.0.so Status in gtk+2.0 package in Ubuntu: New Bug description: As for related bug https://bugs.launchpad.net/ubuntu/+source/qtstyleplugins-src/+bug/1874102 , theming a qt application with the "gtk2" theme causes the app to crash with segfault: ``` segfault at 114 ip 7f0439c6caa5 sp 7fff05b55770 error 6 in libgdk-x11-2.0.so.0.2400.32[7f0439c36000+5e000] ``` Also the following code is available: ``` Code: 64 24 10 4c 8d 6c 24 40 e8 d8 fe ff ff 31 f6 48 8d 5c 24 38 48 89 c7 31 c0 e8 77 c9 fc ff 31 d2 48 8d 35 0e fe ff ff 48 89 ef 80 14 01 00 00 01 00 00 00 49 89 c7 48 89 a8 d8 00 00 00 e8 12 ``` ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgtk2.0-0 2.24.32-4ubuntu4 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Tue Apr 21 18:08:47 2020 InstallationDate: Installed on 2020-04-03 (17 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) SourcePackage: gtk+2.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1874107/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1859926] Re: fonts-noto-color-emoji not making pretty emojis in google chrome
The issue seem to appear when multiple fonts can provide the emojis. What seems to me is that the noto-color-emojis are not necessarily the first in the list. I had for exaple other font-noto packages and they were hiding the color emojis. I removed all the others and now I can see the color ones again. The fact that user fonts have priority over system fonts is the reason for why the previous workaround works. However, in order to fix this bug, we need to think first, what should be fixed? Option 1: the issue is just that the user is unaware -> keep the current behaviour and eventually find a way to inform the user of what font has the highest priority to provide emojis, possibly at install time. (This should be possible, given that Chrome does this) Option 2: the issue is the mechanism -> we could have some configuration for a default emoji-provider, and have it handled with update- alternatives, the same way one can set the vanilla or ubuntu or pop gdm theme. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fonts-noto-color-emoji in Ubuntu. https://bugs.launchpad.net/bugs/1859926 Title: fonts-noto-color-emoji not making pretty emojis in google chrome Status in fonts-noto-color-emoji package in Ubuntu: Confirmed Bug description: Google-Chrome and emoji's is being a weird headache. Something's causing it not to find the right font to make emoji's: "[13743:1:0115/225907.016533:ERROR:child_process_sandbox_support_impl_linux.cc(79)] FontService unique font name matching request did not receive a response. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-noto-color-emoji/+bug/1859926/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872011] Re: Google chrome sometimes stops displaying color emojis
*** This bug is a duplicate of bug 1859926 *** https://bugs.launchpad.net/bugs/1859926 ** Description changed: - I recently noticed that after reboots or possibly after Google Chrome - get updated, I cannot anymore see color emojis (I can only see the old - black and white ones instead). Reinstalling the package seem to solve - the issue temporarily but after the a reboot or Chrome update the issue - arises again. - - A discussion on what appears to be the same issue: - https://askubuntu.com/questions/1029661/18-04-color-emoji-not-showing- - up-at-all-in-chrome-only-partially-in-firefox + I recently noticed that after reboots or possibly after Google Chrome get updated, I cannot anymore see color emojis (I can only see the old black and white ones instead). Reinstalling the package seem to solve the issue temporarily but after the a reboot or Chrome update the issue arises again. + Similar issue on Brave (Chrome-based) browser: https://community.brave.com/t/emoji-are-monochrome-line-art-or-blank-boxes-brave-1-1-23/100111/7 + Discussion on AskUbuntu on similar issue: https://askubuntu.com/questions/1029661/18-04-color-emoji-not-showing-up-at-all-in-chrome-only-partially-in-firefox ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: fonts-noto-color-emoji 0~20191119-1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Apr 10 09:51:14 2020 Dependencies: InstallationDate: Installed on 2020-04-03 (6 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) PackageArchitecture: all SourcePackage: fonts-noto-color-emoji UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: I recently noticed that after reboots or possibly after Google Chrome get updated, I cannot anymore see color emojis (I can only see the old black and white ones instead). Reinstalling the package seem to solve the issue temporarily but after the a reboot or Chrome update the issue arises again. Similar issue on Brave (Chrome-based) browser: https://community.brave.com/t/emoji-are-monochrome-line-art-or-blank-boxes-brave-1-1-23/100111/7 Discussion on AskUbuntu on similar issue: https://askubuntu.com/questions/1029661/18-04-color-emoji-not-showing-up-at-all-in-chrome-only-partially-in-firefox + Possibly a duplicate of: https://bugs.launchpad.net/ubuntu/+source/fonts-noto-color-emoji/+bug/1859926?comments=all ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: fonts-noto-color-emoji 0~20191119-1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Apr 10 09:51:14 2020 Dependencies: InstallationDate: Installed on 2020-04-03 (6 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) PackageArchitecture: all SourcePackage: fonts-noto-color-emoji UpgradeStatus: No upgrade log present (probably fresh install) ** This bug has been marked a duplicate of bug 1859926 fonts-noto-color-emoji not making pretty emojis in google chrome -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fonts-noto-color-emoji in Ubuntu. https://bugs.launchpad.net/bugs/1872011 Title: Google chrome sometimes stops displaying color emojis Status in fonts-noto-color-emoji package in Ubuntu: New Bug description: I recently noticed that after reboots or possibly after Google Chrome get updated, I cannot anymore see color emojis (I can only see the old black and white ones instead). Reinstalling the package seem to solve the issue temporarily but after the a reboot or Chrome update the issue arises again. Similar issue on Brave (Chrome-based) browser: https://community.brave.com/t/emoji-are-monochrome-line-art-or-blank-boxes-brave-1-1-23/100111/7 Discussion on AskUbuntu on similar issue: https://askubuntu.com/questions/1029661/18-04-color-emoji-not-showing-up-at-all-in-chrome-only-partially-in-firefox Possibly a duplicate of: https://bugs.launchpad.net/ubuntu/+source/fonts-noto-color-emoji/+bug/1859926?comments=all ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: fonts-noto-color-emoji 0~20191119-1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Apr 10 09:51:14 2020 Dependencies: InstallationDate: Installed on 2020-04-03 (6 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) PackageArchitecture: all SourcePackage: fonts-noto-color-emoji
[Desktop-packages] [Bug 1872011] [NEW] Google chrome sometimes stops displaying color emojis
*** This bug is a duplicate of bug 1859926 *** https://bugs.launchpad.net/bugs/1859926 Public bug reported: I recently noticed that after reboots or possibly after Google Chrome get updated, I cannot anymore see color emojis (I can only see the old black and white ones instead). Reinstalling the package seem to solve the issue temporarily but after the a reboot or Chrome update the issue arises again. Similar issue on Brave (Chrome-based) browser: https://community.brave.com/t/emoji-are-monochrome-line-art-or-blank-boxes-brave-1-1-23/100111/7 Discussion on AskUbuntu on similar issue: https://askubuntu.com/questions/1029661/18-04-color-emoji-not-showing-up-at-all-in-chrome-only-partially-in-firefox Possibly a duplicate of: https://bugs.launchpad.net/ubuntu/+source/fonts-noto-color-emoji/+bug/1859926?comments=all ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: fonts-noto-color-emoji 0~20191119-1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Apr 10 09:51:14 2020 Dependencies: InstallationDate: Installed on 2020-04-03 (6 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) PackageArchitecture: all SourcePackage: fonts-noto-color-emoji UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: fonts-noto-color-emoji (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Description changed: I recently noticed that after reboots or possibly after Google Chrome get updated, I cannot anymore see color emojis (I can only see the old black and white ones instead). Reinstalling the package seem to solve the issue temporarily but after the a reboot or Chrome update the issue arises again. + + A discussion on what appear to be the same issue: + https://askubuntu.com/questions/1029661/18-04-color-emoji-not-showing- + up-at-all-in-chrome-only-partially-in-firefox ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: fonts-noto-color-emoji 0~20191119-1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Apr 10 09:51:14 2020 Dependencies: - + InstallationDate: Installed on 2020-04-03 (6 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) PackageArchitecture: all SourcePackage: fonts-noto-color-emoji UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: I recently noticed that after reboots or possibly after Google Chrome get updated, I cannot anymore see color emojis (I can only see the old black and white ones instead). Reinstalling the package seem to solve the issue temporarily but after the a reboot or Chrome update the issue arises again. - A discussion on what appear to be the same issue: + A discussion on what appears to be the same issue: https://askubuntu.com/questions/1029661/18-04-color-emoji-not-showing- up-at-all-in-chrome-only-partially-in-firefox ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: fonts-noto-color-emoji 0~20191119-1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Apr 10 09:51:14 2020 Dependencies: InstallationDate: Installed on 2020-04-03 (6 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) PackageArchitecture: all SourcePackage: fonts-noto-color-emoji UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fonts-noto-color-emoji in Ubuntu. https://bugs.launchpad.net/bugs/1872011 Title: Google chrome sometimes stops displaying color emojis Status in fonts-noto-color-emoji package in Ubuntu: New Bug description: I recently noticed that after reboots or possibly after Google Chrome get updated, I cannot anymore see color emojis (I can only see the old black and white ones instead). Reinstalling the package seem to solve the issue temporarily but after the a reboot or Chrome update the issue arises again. Similar issue on Brave (Chrome-based) browser: https://community.brave.com/t/emoji-are-monochrome-line-art-or-blank-boxes-brave-1-1-23/100111/7 Discussion on AskUbuntu on similar issue: https://askubuntu.com/questions/1029661/18-04-color-emoji-not-showing-up-at-all-in-chrome-only-partially-in-firefox Possibly a duplicate of: https://bugs.launchpad.net/ubuntu/+source/fonts-noto-color-emoji/+bug/1859926?comments=all ProblemType: Bug
[Desktop-packages] [Bug 1870794] [NEW] missing some emojis
Public bug reported: The current version is missing some emojis which are already available upstream. I didn't check them all but it seems they are v13 emojis. You can see the missing ones as tofu from here: https://unicode.org/emoji/charts/full-emoji-list.html ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: fonts-noto-color-emoji 0~20191119-1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Apr 4 17:25:41 2020 Dependencies: InstallationDate: Installed on 2020-04-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) PackageArchitecture: all SourcePackage: fonts-noto-color-emoji UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: fonts-noto-color-emoji (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fonts-noto-color-emoji in Ubuntu. https://bugs.launchpad.net/bugs/1870794 Title: missing some emojis Status in fonts-noto-color-emoji package in Ubuntu: New Bug description: The current version is missing some emojis which are already available upstream. I didn't check them all but it seems they are v13 emojis. You can see the missing ones as tofu from here: https://unicode.org/emoji/charts/full-emoji-list.html ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: fonts-noto-color-emoji 0~20191119-1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Apr 4 17:25:41 2020 Dependencies: InstallationDate: Installed on 2020-04-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) PackageArchitecture: all SourcePackage: fonts-noto-color-emoji UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-noto-color-emoji/+bug/1870794/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1863895] Re: gnome software taking large amount of memory
Today I woke up, with the laptop running though the night, and I discovered GNOME software is using 721.5 MB of memory. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1863895 Title: gnome software taking large amount of memory Status in gnome-software package in Ubuntu: New Bug description: I just notice that gnome-software is taking at the moment 377MB of memory, which I consider quite excessive. Let me know if I can help more. What happened? gnome-software using high memory, up to 377MB What did I expect? gnome-software using at most 280MB ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-software 3.35.2-0ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Feb 19 15:00:56 2020 InstallationDate: Installed on 2019-02-03 (380 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) InstalledPlugins: gnome-software-plugin-flatpak 3.35.2-0ubuntu2 gnome-software-plugin-snap3.35.2-0ubuntu2 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1863895/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1863895] [NEW] gnome software taking large amount of memory
Public bug reported: I just notice that gnome-software is taking at the moment 377MB of memory, which I consider quite excessive. Let me know if I can help more. What happened? gnome-software using high memory, up to 377MB What did I expect? gnome-software using at most 280MB ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-software 3.35.2-0ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Feb 19 15:00:56 2020 InstallationDate: Installed on 2019-02-03 (380 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) InstalledPlugins: gnome-software-plugin-flatpak 3.35.2-0ubuntu2 gnome-software-plugin-snap3.35.2-0ubuntu2 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1863895 Title: gnome software taking large amount of memory Status in gnome-software package in Ubuntu: New Bug description: I just notice that gnome-software is taking at the moment 377MB of memory, which I consider quite excessive. Let me know if I can help more. What happened? gnome-software using high memory, up to 377MB What did I expect? gnome-software using at most 280MB ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-software 3.35.2-0ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Feb 19 15:00:56 2020 InstallationDate: Installed on 2019-02-03 (380 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) InstalledPlugins: gnome-software-plugin-flatpak 3.35.2-0ubuntu2 gnome-software-plugin-snap3.35.2-0ubuntu2 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1863895/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1727908] Re: Software & Updates application does not permit changes on the "Other Software" tab
What this triggers in the logs: gnome-shell: > polkitAuthenticationAgent: Received 2 identities that can be used for > authentication. Only considering one. > pushModal: invocation of begin_modal failed > polkitAuthenticationAgent: Failed to show modal dialog. Dismissing > authentication request for action-id > com.ubuntu.softwareproperties.applychanges cookie > 7-b2a6e60b05bc38c7fd20137335c2abcb-34-cd8e89ea6620c9969383c39013bf86c1 polkitd: > Operator of unix-session:2 FAILED to authenticate to gain authorization for > action com.ubuntu.softwareproperties.applychanges for > system-bus-name::1.26625 [/usr/bin/python3 /usr/bin/software-properties-gtk] > (owned by unix-user:fabio) gnome-shell: > ERROR:root:Authentication canceled, changes have not been saved -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1727908 Title: Software & Updates application does not permit changes on the "Other Software" tab Status in gnome-shell package in Ubuntu: Confirmed Status in software-properties package in Ubuntu: Confirmed Status in gnome-shell source package in Bionic: Confirmed Status in software-properties source package in Bionic: Confirmed Bug description: On the "Other Software" tab, I am unable to select "Canonical Partners". Similarly, the other checkboxes on the "Other Software" can not be clicked. Clicking on a checkbox has no effect, and a dialog requesting the admin password is not presented. However, activating or deactivating checkboxes on other tabs causes an authorization dialog to be presented to the user. I experience this bug in an an Xorg session. sources.list and sources.list.d have the following permissions: -rw-r--r-- 1 root root 2897 Oct 26 22:35 sources.list drwxr-xr-x 2 root root 4096 Oct 26 21:29 sources.list.d All files in sources.list.d have the following permissions as this example: -rw-r--r-- 1 root root 189 Oct 25 21:50 google-chrome.list $ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 $ apt-cache policy software-properties-gtk software-properties-gtk: Installed: 0.96.24.17 Candidate: 0.96.24.17 Version table: *** 0.96.24.17 500 500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu artful/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: software-properties-gtk 0.96.24.17 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Oct 26 22:45:09 2017 InstallationDate: Installed on 2017-10-26 (1 days ago) InstallationMedia: Ubuntu 17.10.0 2017.10.25 amd64 "Custom Artful Aardvark" PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1727908/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1727908] Re: Software & Updates application does not permit changes on the "Other Software" tab
Video of the bug ** Attachment added: "Screencast from 02-12-19 16:00:10.webm" https://bugs.launchpad.net/ubuntu/bionic/+source/gnome-shell/+bug/1727908/+attachment/5309266/+files/Screencast%20from%2002-12-19%2016%3A00%3A10.webm -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1727908 Title: Software & Updates application does not permit changes on the "Other Software" tab Status in gnome-shell package in Ubuntu: Confirmed Status in software-properties package in Ubuntu: Confirmed Status in gnome-shell source package in Bionic: Confirmed Status in software-properties source package in Bionic: Confirmed Bug description: On the "Other Software" tab, I am unable to select "Canonical Partners". Similarly, the other checkboxes on the "Other Software" can not be clicked. Clicking on a checkbox has no effect, and a dialog requesting the admin password is not presented. However, activating or deactivating checkboxes on other tabs causes an authorization dialog to be presented to the user. I experience this bug in an an Xorg session. sources.list and sources.list.d have the following permissions: -rw-r--r-- 1 root root 2897 Oct 26 22:35 sources.list drwxr-xr-x 2 root root 4096 Oct 26 21:29 sources.list.d All files in sources.list.d have the following permissions as this example: -rw-r--r-- 1 root root 189 Oct 25 21:50 google-chrome.list $ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 $ apt-cache policy software-properties-gtk software-properties-gtk: Installed: 0.96.24.17 Candidate: 0.96.24.17 Version table: *** 0.96.24.17 500 500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu artful/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: software-properties-gtk 0.96.24.17 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Oct 26 22:45:09 2017 InstallationDate: Installed on 2017-10-26 (1 days ago) InstallationMedia: Ubuntu 17.10.0 2017.10.25 amd64 "Custom Artful Aardvark" PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1727908/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1727908] Re: Software & Updates application does not permit changes on the "Other Software" tab
Just tested on focal. I didn't have the repo, so I added it: ``` deb http://archive.canonical.com/ubuntu focal partner ``` It correctly asked me the password and after that it was added. I deselected it to verify this bug. Then I closed the software-properties-gtk window. To then verify the bug, I opened again software-properties-gtk (from Dash), moved to Other Software and clicked on the Canonical Partners repo. On click nothing appeared (we would be expecting a password prompt) but the window got unselected, like if I had moved to some other window. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1727908 Title: Software & Updates application does not permit changes on the "Other Software" tab Status in gnome-shell package in Ubuntu: Confirmed Status in software-properties package in Ubuntu: Confirmed Status in gnome-shell source package in Bionic: Confirmed Status in software-properties source package in Bionic: Confirmed Bug description: On the "Other Software" tab, I am unable to select "Canonical Partners". Similarly, the other checkboxes on the "Other Software" can not be clicked. Clicking on a checkbox has no effect, and a dialog requesting the admin password is not presented. However, activating or deactivating checkboxes on other tabs causes an authorization dialog to be presented to the user. I experience this bug in an an Xorg session. sources.list and sources.list.d have the following permissions: -rw-r--r-- 1 root root 2897 Oct 26 22:35 sources.list drwxr-xr-x 2 root root 4096 Oct 26 21:29 sources.list.d All files in sources.list.d have the following permissions as this example: -rw-r--r-- 1 root root 189 Oct 25 21:50 google-chrome.list $ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 $ apt-cache policy software-properties-gtk software-properties-gtk: Installed: 0.96.24.17 Candidate: 0.96.24.17 Version table: *** 0.96.24.17 500 500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu artful/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: software-properties-gtk 0.96.24.17 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Oct 26 22:45:09 2017 InstallationDate: Installed on 2017-10-26 (1 days ago) InstallationMedia: Ubuntu 17.10.0 2017.10.25 amd64 "Custom Artful Aardvark" PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1727908/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1851824] Re: gnome shell freezes when too many notifications appear
Thanks. I created a log with `journalctl --since "2019-11-08 13:00:00" --until "2019-11-08 13:26:49" > ~/gnome_hung_logs.txt` which I then cleaned up of unnecessary events, like nm reconnecting or similar unuseful logs. ** Attachment added: "gnome_hung_logs.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1851824/+attachment/5305140/+files/gnome_hung_logs.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1851824 Title: gnome shell freezes when too many notifications appear Status in gnome-shell package in Ubuntu: Incomplete Bug description: I'm using 20.04. When I receive some notifications immediately one after the other, the shell sometimes freezes. I usually make it start again moving to a vt and doing `killall -3 gnome-shell`. This makes it work again (except it makes some apps like PyCharm and Chrome to crash). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.34.1+git20191024-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Nov 8 13:26:49 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-02-03 (277 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2019-07-21 (109 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1851824/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1851824] Re: gnome shell freezes when too many notifications appear
I could not reproduce the issue with multiple notify send. When it happened I was receiving notifications from a Chrome extension called Pushbullet (forwards Android notifications on your desktop and other stuff). I suppose however that Chrome uses the notify-send to do so, as they look native gnome notifications. About the journal, I didn't notice anything. Can you suggest me what to look at and where? I'm never sure which logs to check exactly :/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1851824 Title: gnome shell freezes when too many notifications appear Status in gnome-shell package in Ubuntu: Incomplete Bug description: I'm using 20.04. When I receive some notifications immediately one after the other, the shell sometimes freezes. I usually make it start again moving to a vt and doing `killall -3 gnome-shell`. This makes it work again (except it makes some apps like PyCharm and Chrome to crash). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.34.1+git20191024-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Nov 8 13:26:49 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-02-03 (277 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2019-07-21 (109 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1851824/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1851824] [NEW] gnome shell freezes when too many notifications appear
Public bug reported: I'm using 20.04. When I receive some notifications immediately one after the other, the shell sometimes freezes. I usually make it start again moving to a vt and doing `killall -3 gnome-shell`. This makes it work again (except it makes some apps like PyCharm and Chrome to crash). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.34.1+git20191024-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Nov 8 13:26:49 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-02-03 (277 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2019-07-21 (109 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1851824 Title: gnome shell freezes when too many notifications appear Status in gnome-shell package in Ubuntu: New Bug description: I'm using 20.04. When I receive some notifications immediately one after the other, the shell sometimes freezes. I usually make it start again moving to a vt and doing `killall -3 gnome-shell`. This makes it work again (except it makes some apps like PyCharm and Chrome to crash). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.34.1+git20191024-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Nov 8 13:26:49 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-02-03 (277 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2019-07-21 (109 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1851824/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1851375] [NEW] gnome-shell stops allowing interactions
Public bug reported: >From time to time gnome-shell gets unresponsive to inputs. I can move the cursor, but I cannot interact with the shell in any way, neither with mouse or keyboard. When this happens I move to a vt and restart the shell with `killall -3 gnome-shell`. After this the shell does usually resume working (albeit some application crashes in the process from time to time). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.34.1+git20191024-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Nov 5 15:31:55 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-02-03 (274 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) RelatedPackageVersions: mutter-common 3.34.1+git20191022-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2019-07-21 (106 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1851375 Title: gnome-shell stops allowing interactions Status in gnome-shell package in Ubuntu: New Bug description: From time to time gnome-shell gets unresponsive to inputs. I can move the cursor, but I cannot interact with the shell in any way, neither with mouse or keyboard. When this happens I move to a vt and restart the shell with `killall -3 gnome-shell`. After this the shell does usually resume working (albeit some application crashes in the process from time to time). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.34.1+git20191024-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Nov 5 15:31:55 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-02-03 (274 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) RelatedPackageVersions: mutter-common 3.34.1+git20191022-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2019-07-21 (106 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1851375/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1849268] Re: No audio after unplugging HDMI (with workaround)
Also, in the logs, many of those: ``` snd_hda_intel :01:00.1: Disabling via vga_switcheroo ``` and ``` snd_hda_intel :01:00.1: Enabling via vga_switcheroo ``` from device: "+pci::01:00.1" -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1849268 Title: No audio after unplugging HDMI (with workaround) Status in pulseaudio package in Ubuntu: New Bug description: Background: My audio used to work correctly. I recently attached the device to my TV using HDMI. The audio kept playing from laptop's speakers. So, from settings, I changed the audio output to HDMI. It worked correctly. Issue: After removing the cable, I had no audio. I could go to the settings > audio page, and see that the output was set back to speakers. The test sounds from the settings worked, but no sound from other apps. Expected: System and apps sound to come out of laptop's speakers. Workaround: What I did to fix this, was to reattach the HDMI cable to the TV, this time the audio started automatically playing on the TV (while the first time I had to explicitly select it). I went to settings > audio and I changed the audio output (which was now set on HDMI) back to the laptop's speakers. Once detaching the HDMI, the audio continued working correctly from the speakers like it used to do. Summary: In short, the automatic audio switching for HDMI, is not working correctly, and especially is not switching properly for applications. Possibly it is just switching for some low level interface. Willing to help with triaging and test. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.2 ProcVersionSignature: Ubuntu 4.15.0-65.74-generic 4.15.18 Uname: Linux 4.15.0-65-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: giorgia1786 F pulseaudio /dev/snd/controlC2: giorgia1786 F pulseaudio /dev/snd/controlC1: giorgia1786 F pulseaudio CurrentDesktop: communitheme:ubuntu:GNOME Date: Tue Oct 22 10:41:15 2019 InstallationDate: Installed on 2018-09-17 (399 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/29/2018 dmi.bios.vendor: Alienware dmi.bios.version: A15 dmi.board.name: 068R5X dmi.board.vendor: Alienware dmi.board.version: A03 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A15 dmi.modalias: dmi:bvnAlienware:bvrA15:bd01/29/2018:svnAlienware:pnAlienware17:pvrA15:rvnAlienware:rn068R5X:rvrA03:cvnAlienware:ct8:cvrA15: dmi.product.family: 00 dmi.product.name: Alienware 17 dmi.product.version: A15 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1849268/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1849268] Re: No audio after unplugging HDMI (with workaround)
$sudo lshw -C display *-display description: VGA compatible controller product: GK106M [GeForce GTX 770M] vendor: NVIDIA Corporation physical id: 0 bus info: pci@:01:00.0 version: a1 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress vga_controller bus_master cap_list rom configuration: driver=nouveau latency=0 resources: irq:29 memory:d000-d0ff memory:a000-afff memory:b000-b1ff ioport:4000(size=128) memory:d108-d10f *-display description: VGA compatible controller product: 4th Gen Core Processor Integrated Graphics Controller vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 06 width: 64 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:30 memory:d200-d23f memory:c000-cfff ioport:5000(size=64) memory:c-d -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1849268 Title: No audio after unplugging HDMI (with workaround) Status in pulseaudio package in Ubuntu: New Bug description: Background: My audio used to work correctly. I recently attached the device to my TV using HDMI. The audio kept playing from laptop's speakers. So, from settings, I changed the audio output to HDMI. It worked correctly. Issue: After removing the cable, I had no audio. I could go to the settings > audio page, and see that the output was set back to speakers. The test sounds from the settings worked, but no sound from other apps. Expected: System and apps sound to come out of laptop's speakers. Workaround: What I did to fix this, was to reattach the HDMI cable to the TV, this time the audio started automatically playing on the TV (while the first time I had to explicitly select it). I went to settings > audio and I changed the audio output (which was now set on HDMI) back to the laptop's speakers. Once detaching the HDMI, the audio continued working correctly from the speakers like it used to do. Summary: In short, the automatic audio switching for HDMI, is not working correctly, and especially is not switching properly for applications. Possibly it is just switching for some low level interface. Willing to help with triaging and test. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.2 ProcVersionSignature: Ubuntu 4.15.0-65.74-generic 4.15.18 Uname: Linux 4.15.0-65-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: giorgia1786 F pulseaudio /dev/snd/controlC2: giorgia1786 F pulseaudio /dev/snd/controlC1: giorgia1786 F pulseaudio CurrentDesktop: communitheme:ubuntu:GNOME Date: Tue Oct 22 10:41:15 2019 InstallationDate: Installed on 2018-09-17 (399 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/29/2018 dmi.bios.vendor: Alienware dmi.bios.version: A15 dmi.board.name: 068R5X dmi.board.vendor: Alienware dmi.board.version: A03 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A15 dmi.modalias: dmi:bvnAlienware:bvrA15:bd01/29/2018:svnAlienware:pnAlienware17:pvrA15:rvnAlienware:rn068R5X:rvrA03:cvnAlienware:ct8:cvrA15: dmi.product.family: 00 dmi.product.name: Alienware 17 dmi.product.version: A15 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1849268/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1849268] Re: No audio after unplugging HDMI (with workaround)
$sudo lshw -C multimedia *-multimedia description: Audio device product: GK106 HDMI Audio Controller vendor: NVIDIA Corporation physical id: 0.1 bus info: pci@:01:00.1 version: a1 width: 32 bits clock: 33MHz capabilities: pm msi pciexpress cap_list configuration: driver=snd_hda_intel latency=0 resources: irq:17 memory:d100-d1003fff *-multimedia:0 description: Audio device product: Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller vendor: Intel Corporation physical id: 3 bus info: pci@:00:03.0 version: 06 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list configuration: driver=snd_hda_intel latency=0 resources: irq:27 memory:d291-d2913fff *-usb description: Video product: Laptop_Integrated_Webcam_FHD vendor: CN0W58PR724873AA07XPA00 physical id: 5 bus info: usb@1:1.5 version: 34.15 capabilities: usb-2.00 configuration: driver=uvcvideo maxpower=500mA speed=480Mbit/s *-multimedia:1 description: Audio device product: 8 Series/C220 Series Chipset High Definition Audio Controller vendor: Intel Corporation physical id: 1b bus info: pci@:00:1b.0 version: 05 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list configuration: driver=snd_hda_intel latency=0 resources: irq:31 memory:d2914000-d2917fff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1849268 Title: No audio after unplugging HDMI (with workaround) Status in pulseaudio package in Ubuntu: New Bug description: Background: My audio used to work correctly. I recently attached the device to my TV using HDMI. The audio kept playing from laptop's speakers. So, from settings, I changed the audio output to HDMI. It worked correctly. Issue: After removing the cable, I had no audio. I could go to the settings > audio page, and see that the output was set back to speakers. The test sounds from the settings worked, but no sound from other apps. Expected: System and apps sound to come out of laptop's speakers. Workaround: What I did to fix this, was to reattach the HDMI cable to the TV, this time the audio started automatically playing on the TV (while the first time I had to explicitly select it). I went to settings > audio and I changed the audio output (which was now set on HDMI) back to the laptop's speakers. Once detaching the HDMI, the audio continued working correctly from the speakers like it used to do. Summary: In short, the automatic audio switching for HDMI, is not working correctly, and especially is not switching properly for applications. Possibly it is just switching for some low level interface. Willing to help with triaging and test. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.2 ProcVersionSignature: Ubuntu 4.15.0-65.74-generic 4.15.18 Uname: Linux 4.15.0-65-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: giorgia1786 F pulseaudio /dev/snd/controlC2: giorgia1786 F pulseaudio /dev/snd/controlC1: giorgia1786 F pulseaudio CurrentDesktop: communitheme:ubuntu:GNOME Date: Tue Oct 22 10:41:15 2019 InstallationDate: Installed on 2018-09-17 (399 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/29/2018 dmi.bios.vendor: Alienware dmi.bios.version: A15 dmi.board.name: 068R5X dmi.board.vendor: Alienware dmi.board.version: A03 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A15 dmi.modalias: dmi:bvnAlienware:bvrA15:bd01/29/2018:svnAlienware:pnAlienware17:pvrA15:rvnAlienware:rn068R5X:rvrA03:cvnAlienware:ct8:cvrA15: dmi.product.family: 00 dmi.product.name: Alienware 17 dmi.product.version: A15 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1849268/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1849268] Re: No audio after unplugging HDMI (with workaround)
I found the following in the logs: ``` snd_hda_codec_hdmi hdaudioC2D0: out of range cmd 0:7:707:ffbf ``` from device: +hdaudio:hdaudioC2D0 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1849268 Title: No audio after unplugging HDMI (with workaround) Status in pulseaudio package in Ubuntu: New Bug description: Background: My audio used to work correctly. I recently attached the device to my TV using HDMI. The audio kept playing from laptop's speakers. So, from settings, I changed the audio output to HDMI. It worked correctly. Issue: After removing the cable, I had no audio. I could go to the settings > audio page, and see that the output was set back to speakers. The test sounds from the settings worked, but no sound from other apps. Expected: System and apps sound to come out of laptop's speakers. Workaround: What I did to fix this, was to reattach the HDMI cable to the TV, this time the audio started automatically playing on the TV (while the first time I had to explicitly select it). I went to settings > audio and I changed the audio output (which was now set on HDMI) back to the laptop's speakers. Once detaching the HDMI, the audio continued working correctly from the speakers like it used to do. Summary: In short, the automatic audio switching for HDMI, is not working correctly, and especially is not switching properly for applications. Possibly it is just switching for some low level interface. Willing to help with triaging and test. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.2 ProcVersionSignature: Ubuntu 4.15.0-65.74-generic 4.15.18 Uname: Linux 4.15.0-65-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: giorgia1786 F pulseaudio /dev/snd/controlC2: giorgia1786 F pulseaudio /dev/snd/controlC1: giorgia1786 F pulseaudio CurrentDesktop: communitheme:ubuntu:GNOME Date: Tue Oct 22 10:41:15 2019 InstallationDate: Installed on 2018-09-17 (399 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/29/2018 dmi.bios.vendor: Alienware dmi.bios.version: A15 dmi.board.name: 068R5X dmi.board.vendor: Alienware dmi.board.version: A03 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A15 dmi.modalias: dmi:bvnAlienware:bvrA15:bd01/29/2018:svnAlienware:pnAlienware17:pvrA15:rvnAlienware:rn068R5X:rvrA03:cvnAlienware:ct8:cvrA15: dmi.product.family: 00 dmi.product.name: Alienware 17 dmi.product.version: A15 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1849268/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1849268] [NEW] No audio after unplugging HDMI (with workaround)
Public bug reported: Background: My audio used to work correctly. I recently attached the device to my TV using HDMI. The audio kept playing from laptop's speakers. So, from settings, I changed the audio output to HDMI. It worked correctly. Issue: After removing the cable, I had no audio. I could go to the settings > audio page, and see that the output was set back to speakers. The test sounds from the settings worked, but no sound from other apps. Expected: System and apps sound to come out of laptop's speakers. Workaround: What I did to fix this, was to reattach the HDMI cable to the TV, this time the audio started automatically playing on the TV (while the first time I had to explicitly select it). I went to settings > audio and I changed the audio output (which was now set on HDMI) back to the laptop's speakers. Once detaching the HDMI, the audio continued working correctly from the speakers like it used to do. Summary: In short, the automatic audio switching for HDMI, is not working correctly, and especially is not switching properly for applications. Possibly it is just switching for some low level interface. Willing to help with triaging and test. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.2 ProcVersionSignature: Ubuntu 4.15.0-65.74-generic 4.15.18 Uname: Linux 4.15.0-65-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: giorgia1786 F pulseaudio /dev/snd/controlC2: giorgia1786 F pulseaudio /dev/snd/controlC1: giorgia1786 F pulseaudio CurrentDesktop: communitheme:ubuntu:GNOME Date: Tue Oct 22 10:41:15 2019 InstallationDate: Installed on 2018-09-17 (399 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/29/2018 dmi.bios.vendor: Alienware dmi.bios.version: A15 dmi.board.name: 068R5X dmi.board.vendor: Alienware dmi.board.version: A03 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A15 dmi.modalias: dmi:bvnAlienware:bvrA15:bd01/29/2018:svnAlienware:pnAlienware17:pvrA15:rvnAlienware:rn068R5X:rvrA03:cvnAlienware:ct8:cvrA15: dmi.product.family: 00 dmi.product.name: Alienware 17 dmi.product.version: A15 dmi.sys.vendor: Alienware ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1849268 Title: No audio after unplugging HDMI (with workaround) Status in pulseaudio package in Ubuntu: New Bug description: Background: My audio used to work correctly. I recently attached the device to my TV using HDMI. The audio kept playing from laptop's speakers. So, from settings, I changed the audio output to HDMI. It worked correctly. Issue: After removing the cable, I had no audio. I could go to the settings > audio page, and see that the output was set back to speakers. The test sounds from the settings worked, but no sound from other apps. Expected: System and apps sound to come out of laptop's speakers. Workaround: What I did to fix this, was to reattach the HDMI cable to the TV, this time the audio started automatically playing on the TV (while the first time I had to explicitly select it). I went to settings > audio and I changed the audio output (which was now set on HDMI) back to the laptop's speakers. Once detaching the HDMI, the audio continued working correctly from the speakers like it used to do. Summary: In short, the automatic audio switching for HDMI, is not working correctly, and especially is not switching properly for applications. Possibly it is just switching for some low level interface. Willing to help with triaging and test. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.2 ProcVersionSignature: Ubuntu 4.15.0-65.74-generic 4.15.18 Uname: Linux 4.15.0-65-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: giorgia1786 F pulseaudio /dev/snd/controlC2: giorgia1786 F pulseaudio /dev/snd/controlC1: giorgia1786 F pulseaudio CurrentDesktop: communitheme:ubuntu:GNOME Date: Tue Oct 22 10:41:15 2019 InstallationDate: Installed on 2018-09-17 (399 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/29/2018 dmi.bios.vendor: Alienware dmi.bios.version: A15 dmi.board.name: 068R5X dmi.board.vendor: Alienware
[Desktop-packages] [Bug 1849268] Re: No audio after unplugging HDMI (with workaround)
I also had: ``` snd_hda_codec_hdmi hdaudioC2D0: HDMI: invalid ELD buf size -1 ``` -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1849268 Title: No audio after unplugging HDMI (with workaround) Status in pulseaudio package in Ubuntu: New Bug description: Background: My audio used to work correctly. I recently attached the device to my TV using HDMI. The audio kept playing from laptop's speakers. So, from settings, I changed the audio output to HDMI. It worked correctly. Issue: After removing the cable, I had no audio. I could go to the settings > audio page, and see that the output was set back to speakers. The test sounds from the settings worked, but no sound from other apps. Expected: System and apps sound to come out of laptop's speakers. Workaround: What I did to fix this, was to reattach the HDMI cable to the TV, this time the audio started automatically playing on the TV (while the first time I had to explicitly select it). I went to settings > audio and I changed the audio output (which was now set on HDMI) back to the laptop's speakers. Once detaching the HDMI, the audio continued working correctly from the speakers like it used to do. Summary: In short, the automatic audio switching for HDMI, is not working correctly, and especially is not switching properly for applications. Possibly it is just switching for some low level interface. Willing to help with triaging and test. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.2 ProcVersionSignature: Ubuntu 4.15.0-65.74-generic 4.15.18 Uname: Linux 4.15.0-65-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: giorgia1786 F pulseaudio /dev/snd/controlC2: giorgia1786 F pulseaudio /dev/snd/controlC1: giorgia1786 F pulseaudio CurrentDesktop: communitheme:ubuntu:GNOME Date: Tue Oct 22 10:41:15 2019 InstallationDate: Installed on 2018-09-17 (399 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/29/2018 dmi.bios.vendor: Alienware dmi.bios.version: A15 dmi.board.name: 068R5X dmi.board.vendor: Alienware dmi.board.version: A03 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A15 dmi.modalias: dmi:bvnAlienware:bvrA15:bd01/29/2018:svnAlienware:pnAlienware17:pvrA15:rvnAlienware:rn068R5X:rvrA03:cvnAlienware:ct8:cvrA15: dmi.product.family: 00 dmi.product.name: Alienware 17 dmi.product.version: A15 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1849268/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1849268] Re: No audio after unplugging HDMI (with workaround)
$lspci -nnk | grep -A2 Audio 00:03.0 Audio device [0403]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller [8086:0c0c] (rev 06) Subsystem: Dell Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller [1028:05aa] Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel -- 00:1b.0 Audio device [0403]: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller [8086:8c20] (rev 05) Subsystem: Dell 8 Series/C220 Series Chipset High Definition Audio Controller [1028:05aa] Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel -- 01:00.1 Audio device [0403]: NVIDIA Corporation GK106 HDMI Audio Controller [10de:0e0b] (rev ff) Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1849268 Title: No audio after unplugging HDMI (with workaround) Status in pulseaudio package in Ubuntu: New Bug description: Background: My audio used to work correctly. I recently attached the device to my TV using HDMI. The audio kept playing from laptop's speakers. So, from settings, I changed the audio output to HDMI. It worked correctly. Issue: After removing the cable, I had no audio. I could go to the settings > audio page, and see that the output was set back to speakers. The test sounds from the settings worked, but no sound from other apps. Expected: System and apps sound to come out of laptop's speakers. Workaround: What I did to fix this, was to reattach the HDMI cable to the TV, this time the audio started automatically playing on the TV (while the first time I had to explicitly select it). I went to settings > audio and I changed the audio output (which was now set on HDMI) back to the laptop's speakers. Once detaching the HDMI, the audio continued working correctly from the speakers like it used to do. Summary: In short, the automatic audio switching for HDMI, is not working correctly, and especially is not switching properly for applications. Possibly it is just switching for some low level interface. Willing to help with triaging and test. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.2 ProcVersionSignature: Ubuntu 4.15.0-65.74-generic 4.15.18 Uname: Linux 4.15.0-65-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: giorgia1786 F pulseaudio /dev/snd/controlC2: giorgia1786 F pulseaudio /dev/snd/controlC1: giorgia1786 F pulseaudio CurrentDesktop: communitheme:ubuntu:GNOME Date: Tue Oct 22 10:41:15 2019 InstallationDate: Installed on 2018-09-17 (399 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/29/2018 dmi.bios.vendor: Alienware dmi.bios.version: A15 dmi.board.name: 068R5X dmi.board.vendor: Alienware dmi.board.version: A03 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A15 dmi.modalias: dmi:bvnAlienware:bvrA15:bd01/29/2018:svnAlienware:pnAlienware17:pvrA15:rvnAlienware:rn068R5X:rvrA03:cvnAlienware:ct8:cvrA15: dmi.product.family: 00 dmi.product.name: Alienware 17 dmi.product.version: A15 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1849268/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1845670] [NEW] gnome-calendar crashes on startup
Public bug reported: It crashes always after I click its icon in the dash. If I launch it from terminal it works. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-calendar 3.34.0-1 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 27 17:21:54 2019 InstallationDate: Installed on 2019-02-03 (235 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-calendar UpgradeStatus: Upgraded to eoan on 2019-07-21 (67 days ago) ** Affects: gnome-calendar (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1845670 Title: gnome-calendar crashes on startup Status in gnome-calendar package in Ubuntu: New Bug description: It crashes always after I click its icon in the dash. If I launch it from terminal it works. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-calendar 3.34.0-1 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 27 17:21:54 2019 InstallationDate: Installed on 2019-02-03 (235 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-calendar UpgradeStatus: Upgraded to eoan on 2019-07-21 (67 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1845670/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1843605] Re: Interactive menu gets frozen and cannot be removed
Seq 1 (Open Google Chrome) ** Attachment added: "Screenshot from 2019-09-11 17-52-12.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1843605/+attachment/5288118/+files/Screenshot%20from%202019-09-11%2017-52-12.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1843605 Title: Interactive menu gets frozen and cannot be removed Status in gnome-shell package in Ubuntu: New Bug description: Using the ubuntu dock, I have Google Chrome as second application. When it's open and I left-click it, the menu appears in a wrong position and gets frozen. I cannot interact with it, I cannot interact with the area under it, and I didn't find any way to make it disappear (apart restarting the shell). I can reproduce this behaviour every time, but only with Chrome. I suppose it might be related to the number of options it has in the menu. I'm attaching the screenshots to show what I mean. 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: Wed Sep 11 18:20:14 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-02-03 (219 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) RelatedPackageVersions: mutter-common 3.34.0-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-07-21 (52 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1843605/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1843605] Re: Interactive menu gets frozen and cannot be removed
Seq 0 (Plain desktop) ** Attachment added: "Screenshot from 2019-09-11 17-52-01.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1843605/+attachment/5288117/+files/Screenshot%20from%202019-09-11%2017-52-01.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1843605 Title: Interactive menu gets frozen and cannot be removed Status in gnome-shell package in Ubuntu: New Bug description: Using the ubuntu dock, I have Google Chrome as second application. When it's open and I left-click it, the menu appears in a wrong position and gets frozen. I cannot interact with it, I cannot interact with the area under it, and I didn't find any way to make it disappear (apart restarting the shell). I can reproduce this behaviour every time, but only with Chrome. I suppose it might be related to the number of options it has in the menu. I'm attaching the screenshots to show what I mean. 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: Wed Sep 11 18:20:14 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-02-03 (219 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) RelatedPackageVersions: mutter-common 3.34.0-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-07-21 (52 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1843605/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1843605] Re: Interactive menu gets frozen and cannot be removed
Seq 2 (Left-click on the Chrome icon, which makes the menu appear in a bad position) ** Attachment added: "Screenshot from 2019-09-11 17-52-15.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1843605/+attachment/5288119/+files/Screenshot%20from%202019-09-11%2017-52-15.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1843605 Title: Interactive menu gets frozen and cannot be removed Status in gnome-shell package in Ubuntu: New Bug description: Using the ubuntu dock, I have Google Chrome as second application. When it's open and I left-click it, the menu appears in a wrong position and gets frozen. I cannot interact with it, I cannot interact with the area under it, and I didn't find any way to make it disappear (apart restarting the shell). I can reproduce this behaviour every time, but only with Chrome. I suppose it might be related to the number of options it has in the menu. I'm attaching the screenshots to show what I mean. 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: Wed Sep 11 18:20:14 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-02-03 (219 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) RelatedPackageVersions: mutter-common 3.34.0-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-07-21 (52 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1843605/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1843605] Re: Interactive menu gets frozen and cannot be removed
Seq 3 (Showing how the menu got stuck and I can left-click other menus for icons not hovered by the stuck menu) ** Attachment added: "Screenshot from 2019-09-11 17-52-19.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1843605/+attachment/5288120/+files/Screenshot%20from%202019-09-11%2017-52-19.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1843605 Title: Interactive menu gets frozen and cannot be removed Status in gnome-shell package in Ubuntu: New Bug description: Using the ubuntu dock, I have Google Chrome as second application. When it's open and I left-click it, the menu appears in a wrong position and gets frozen. I cannot interact with it, I cannot interact with the area under it, and I didn't find any way to make it disappear (apart restarting the shell). I can reproduce this behaviour every time, but only with Chrome. I suppose it might be related to the number of options it has in the menu. I'm attaching the screenshots to show what I mean. 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: Wed Sep 11 18:20:14 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-02-03 (219 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) RelatedPackageVersions: mutter-common 3.34.0-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-07-21 (52 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1843605/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1843605] Re: Interactive menu gets frozen and cannot be removed
Extensions are just default ones: Desktop Folders, AppIndicators and UbuntuDock -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1843605 Title: Interactive menu gets frozen and cannot be removed Status in gnome-shell package in Ubuntu: New Bug description: Using the ubuntu dock, I have Google Chrome as second application. When it's open and I left-click it, the menu appears in a wrong position and gets frozen. I cannot interact with it, I cannot interact with the area under it, and I didn't find any way to make it disappear (apart restarting the shell). I can reproduce this behaviour every time, but only with Chrome. I suppose it might be related to the number of options it has in the menu. I'm attaching the screenshots to show what I mean. 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: Wed Sep 11 18:20:14 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-02-03 (219 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) RelatedPackageVersions: mutter-common 3.34.0-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-07-21 (52 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1843605/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1843605] [NEW] Interactive menu gets frozen and cannot be removed
Public bug reported: Using the ubuntu dock, I have Google Chrome as second application. When it's open and I left-click it, the menu appears in a wrong position and gets frozen. I cannot interact with it, I cannot interact with the area under it, and I didn't find any way to make it disappear (apart restarting the shell). I can reproduce this behaviour every time, but only with Chrome. I suppose it might be related to the number of options it has in the menu. I'm attaching the screenshots to show what I mean. 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: Wed Sep 11 18:20:14 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-02-03 (219 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) RelatedPackageVersions: mutter-common 3.34.0-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-07-21 (52 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1843605 Title: Interactive menu gets frozen and cannot be removed Status in gnome-shell package in Ubuntu: New Bug description: Using the ubuntu dock, I have Google Chrome as second application. When it's open and I left-click it, the menu appears in a wrong position and gets frozen. I cannot interact with it, I cannot interact with the area under it, and I didn't find any way to make it disappear (apart restarting the shell). I can reproduce this behaviour every time, but only with Chrome. I suppose it might be related to the number of options it has in the menu. I'm attaching the screenshots to show what I mean. 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: Wed Sep 11 18:20:14 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-02-03 (219 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) RelatedPackageVersions: mutter-common 3.34.0-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-07-21 (52 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1843605/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1842890] Re: gnome-shell high cpu usage and unresponsiveness
Thanks, perfect! :) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1842890 Title: gnome-shell high cpu usage and unresponsiveness Status in gnome-shell package in Ubuntu: Incomplete Bug description: From time to time the shell becomes slow and poorly responsive, checking the CPU usage I discovered that in such moments it had high values, like 25-35%. In only one occasion it went up to 100% CPU and I was forced to reboot. I don't know if it matters, but I'm using an external screen connected to my laptop. Let me know if I can help better to debug the issue. 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 11:35:03 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-02-03 (213 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) RelatedPackageVersions: mutter-common 3.33.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-07-21 (45 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1842890/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1842890] Re: gnome-shell high cpu usage and unresponsiveness
I removed the non-Ubuntu extensions (including user-theme, which is provided by the gnome-shell-extensions package). Should the problem happen again, would you like me to apport collect or to just write it? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1842890 Title: gnome-shell high cpu usage and unresponsiveness Status in gnome-shell package in Ubuntu: Incomplete Bug description: From time to time the shell becomes slow and poorly responsive, checking the CPU usage I discovered that in such moments it had high values, like 25-35%. In only one occasion it went up to 100% CPU and I was forced to reboot. I don't know if it matters, but I'm using an external screen connected to my laptop. Let me know if I can help better to debug the issue. 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 11:35:03 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-02-03 (213 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) RelatedPackageVersions: mutter-common 3.33.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-07-21 (45 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1842890/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1842890] [NEW] gnome-shell high cpu usage and unresponsiveness
Public bug reported: >From time to time the shell becomes slow and poorly responsive, checking the CPU usage I discovered that in such moments it had high values, like 25-35%. In only one occasion it went up to 100% CPU and I was forced to reboot. I don't know if it matters, but I'm using an external screen connected to my laptop. Let me know if I can help better to debug the issue. 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 11:35:03 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-02-03 (213 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) RelatedPackageVersions: mutter-common 3.33.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-07-21 (45 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1842890 Title: gnome-shell high cpu usage and unresponsiveness Status in gnome-shell package in Ubuntu: New Bug description: From time to time the shell becomes slow and poorly responsive, checking the CPU usage I discovered that in such moments it had high values, like 25-35%. In only one occasion it went up to 100% CPU and I was forced to reboot. I don't know if it matters, but I'm using an external screen connected to my laptop. Let me know if I can help better to debug the issue. 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 11:35:03 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-02-03 (213 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) RelatedPackageVersions: mutter-common 3.33.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-07-21 (45 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1842890/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1839127] Re: headerbar buttons can get hidden if left column is too narrow
** Attachment added: "Screenshot-20190806135701-897x641.png" https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1839127/+attachment/5281174/+files/Screenshot-20190806135701-897x641.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1839127 Title: headerbar buttons can get hidden if left column is too narrow Status in gnome-disk-utility package in Ubuntu: New Bug description: Check the left column of gnome-disk-utility, you can reduce it in ways that hide the buttons contained within. I think other apps have some dynamically computed minimum width to avoid such behaviour. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-disk-utility 3.32.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 Uname: Linux 5.2.0-8-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 6 13:47:55 2019 InstallationDate: Installed on 2019-02-03 (183 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-disk-utility UpgradeStatus: Upgraded to eoan on 2019-07-21 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1839127/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1839127] [NEW] headerbar buttons can get hidden if left column is too narrow
Public bug reported: Check the left column of gnome-disk-utility, you can reduce it in ways that hide the buttons contained within. I think other apps have some dynamically computed minimum width to avoid such behaviour. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-disk-utility 3.32.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 Uname: Linux 5.2.0-8-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 6 13:47:55 2019 InstallationDate: Installed on 2019-02-03 (183 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-disk-utility UpgradeStatus: Upgraded to eoan on 2019-07-21 (15 days ago) ** Affects: gnome-disk-utility (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ** Attachment added: "Screenshot-20190806135639-909x641.png" https://bugs.launchpad.net/bugs/1839127/+attachment/5281170/+files/Screenshot-20190806135639-909x641.png ** Summary changed: - headerbar buttons can hide if too narrow column + headerbar buttons can get hidden if left column is too narrow -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1839127 Title: headerbar buttons can get hidden if left column is too narrow Status in gnome-disk-utility package in Ubuntu: New Bug description: Check the left column of gnome-disk-utility, you can reduce it in ways that hide the buttons contained within. I think other apps have some dynamically computed minimum width to avoid such behaviour. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-disk-utility 3.32.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 Uname: Linux 5.2.0-8-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 6 13:47:55 2019 InstallationDate: Installed on 2019-02-03 (183 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-disk-utility UpgradeStatus: Upgraded to eoan on 2019-07-21 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1839127/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1839127] Re: headerbar buttons can get hidden if left column is too narrow
** Attachment added: "Screenshot-20190806135742-897x641.png" https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1839127/+attachment/5281175/+files/Screenshot-20190806135742-897x641.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1839127 Title: headerbar buttons can get hidden if left column is too narrow Status in gnome-disk-utility package in Ubuntu: New Bug description: Check the left column of gnome-disk-utility, you can reduce it in ways that hide the buttons contained within. I think other apps have some dynamically computed minimum width to avoid such behaviour. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-disk-utility 3.32.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 Uname: Linux 5.2.0-8-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 6 13:47:55 2019 InstallationDate: Installed on 2019-02-03 (183 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-disk-utility UpgradeStatus: Upgraded to eoan on 2019-07-21 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1839127/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1839127] Re: headerbar buttons can get hidden if left column is too narrow
This is how I think it should be wide as minimum. Note however that I have buttons on the left, hence my suggestion of a dynamic minimum width. People who have them on the right shouldn't have unnecessary padding. ** Attachment added: "Screenshot-20190806135750-897x641.png" https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1839127/+attachment/5281188/+files/Screenshot-20190806135750-897x641.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1839127 Title: headerbar buttons can get hidden if left column is too narrow Status in gnome-disk-utility package in Ubuntu: New Bug description: Check the left column of gnome-disk-utility, you can reduce it in ways that hide the buttons contained within. I think other apps have some dynamically computed minimum width to avoid such behaviour. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-disk-utility 3.32.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 Uname: Linux 5.2.0-8-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 6 13:47:55 2019 InstallationDate: Installed on 2019-02-03 (183 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-disk-utility UpgradeStatus: Upgraded to eoan on 2019-07-21 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1839127/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1818274] Re: Cannot change screenshot directory
** Bug watch added: GNOME Bug Tracker #699642 https://bugzilla.gnome.org/show_bug.cgi?id=699642 ** Also affects: gnome-settings-daemon via https://bugzilla.gnome.org/show_bug.cgi?id=699642 Importance: Unknown Status: Unknown ** Description changed: Expected: Be able to change the directory where the screenshots are saved, either from Settings (GUI) or from gsettings (cli). What happens: Screenshots are unconditionally saved to the Pictures directory (XDG_PICTURES_DIR). Temporary Workaround: Use a specific extension: Screenshot Locations (https://extensions.gnome.org/extension/1179/screenshot-locations/) Previous discussion: The bug was previously reported 5 years ago on bugzilla 699642 (https://bugzilla.gnome.org/show_bug.cgi?id=699642) and closed as WONTFIX. I'm reporting here again, as I hope the time is ripe for a reconsideration, given how many users are affected and willing to see this solved. - - Tracked on GitLab: https://gitlab.gnome.org/GNOME/gnome-settings- - daemon/issues/153 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-settings-daemon 3.28.1-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: communitheme:ubuntu:GNOME Date: Fri Mar 1 19:50:31 2019 InstallationDate: Installed on 2019-02-03 (25 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1818274 Title: Cannot change screenshot directory Status in GNOME Settings Daemon: Unknown Status in gnome-settings-daemon package in Ubuntu: Triaged Bug description: Expected: Be able to change the directory where the screenshots are saved, either from Settings (GUI) or from gsettings (cli). What happens: Screenshots are unconditionally saved to the Pictures directory (XDG_PICTURES_DIR). Temporary Workaround: Use a specific extension: Screenshot Locations (https://extensions.gnome.org/extension/1179/screenshot-locations/) Previous discussion: The bug was previously reported 5 years ago on bugzilla 699642 (https://bugzilla.gnome.org/show_bug.cgi?id=699642) and closed as WONTFIX. I'm reporting here again, as I hope the time is ripe for a reconsideration, given how many users are affected and willing to see this solved. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-settings-daemon 3.28.1-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: communitheme:ubuntu:GNOME Date: Fri Mar 1 19:50:31 2019 InstallationDate: Installed on 2019-02-03 (25 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1818274/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1818274] Re: Cannot change screenshot directory
Related but not duplicate: https://bugs.launchpad.net/ubuntu/+source /gnome-screenshot/+bug/1742443 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1818274 Title: Cannot change screenshot directory Status in gnome-settings-daemon package in Ubuntu: New Bug description: Expected: Be able to change the directory where the screenshots are saved, either from Settings (GUI) or from gsettings (cli). What happens: Screenshots are unconditionally saved to the Pictures directory (XDG_PICTURES_DIR). Temporary Workaround: Use a specific extension: Screenshot Locations (https://extensions.gnome.org/extension/1179/screenshot-locations/) Previous discussion: The bug was previously reported 5 years ago on bugzilla 699642 (https://bugzilla.gnome.org/show_bug.cgi?id=699642) and closed as WONTFIX. I'm reporting here again, as I hope the time is ripe for a reconsideration, given how many users are affected and willing to see this solved. Tracked on GitLab: https://gitlab.gnome.org/GNOME/gnome-settings- daemon/issues/153 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-settings-daemon 3.28.1-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: communitheme:ubuntu:GNOME Date: Fri Mar 1 19:50:31 2019 InstallationDate: Installed on 2019-02-03 (25 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1818274/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1818274] [NEW] Cannot change screenshot directory
Public bug reported: Expected: Be able to change the directory where the screenshots are saved, either from Settings (GUI) or from gsettings (cli). What happens: Screenshots are unconditionally saved to the Pictures directory (XDG_PICTURES_DIR). Temporary Workaround: Use a specific extension: Screenshot Locations (https://extensions.gnome.org/extension/1179/screenshot-locations/) Previous discussion: The bug was previously reported 5 years ago on bugzilla 699642 (https://bugzilla.gnome.org/show_bug.cgi?id=699642) and closed as WONTFIX. I'm reporting here again, as I hope the time is ripe for a reconsideration, given how many users are affected and willing to see this solved. Tracked on GitLab: https://gitlab.gnome.org/GNOME/gnome-settings- daemon/issues/153 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-settings-daemon 3.28.1-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: communitheme:ubuntu:GNOME Date: Fri Mar 1 19:50:31 2019 InstallationDate: Installed on 2019-02-03 (25 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1818274 Title: Cannot change screenshot directory Status in gnome-settings-daemon package in Ubuntu: New Bug description: Expected: Be able to change the directory where the screenshots are saved, either from Settings (GUI) or from gsettings (cli). What happens: Screenshots are unconditionally saved to the Pictures directory (XDG_PICTURES_DIR). Temporary Workaround: Use a specific extension: Screenshot Locations (https://extensions.gnome.org/extension/1179/screenshot-locations/) Previous discussion: The bug was previously reported 5 years ago on bugzilla 699642 (https://bugzilla.gnome.org/show_bug.cgi?id=699642) and closed as WONTFIX. I'm reporting here again, as I hope the time is ripe for a reconsideration, given how many users are affected and willing to see this solved. Tracked on GitLab: https://gitlab.gnome.org/GNOME/gnome-settings- daemon/issues/153 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-settings-daemon 3.28.1-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: communitheme:ubuntu:GNOME Date: Fri Mar 1 19:50:31 2019 InstallationDate: Installed on 2019-02-03 (25 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1818274/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1740106] Re: Gnome terminal not starting, timeout reached (bionic)
I confirm that removing chrome-remote-desktop and rebooting fixed the issue for me too. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1740106 Title: Gnome terminal not starting, timeout reached (bionic) Status in gnome-terminal package in Ubuntu: Confirmed Bug description: After a having my memory filled I had to reboot because the system got unresponsive. After that I can no longer open gnome terminal. I tried running it from xterm and the following message appears: Error constructing proxy for org.gnome.Terminal:/org/gnome/Terminal/Factory0: Error calling StartServiceByName for org.gnome.Terminal: Timeout was reached ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-terminal 3.24.2-0ubuntu4 ProcVersionSignature: Ubuntu 4.14.0-11.13-generic 4.14.3 Uname: Linux 4.14.0-11-generic x86_64 ApportVersion: 2.20.8-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Dec 26 10:38:26 2017 InstallationDate: Installed on 2017-08-21 (126 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1740106/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1662688] Re: Have drag and drop support for the dock
I think a temporary fix could be for it to work like Dash to Panel, which if hovered while dragging, activates the shell overview and hence allows to drop on the chose window. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1662688 Title: Have drag and drop support for the dock Status in GNOME Shell: Confirmed Status in Ubuntu GNOME: New Status in gnome-shell package in Ubuntu: Triaged Bug description: It would be useful if the dock in the AO supported drag and drop, that is so that one may drag a file to one of its docked applications and it may open it. Although this wouldn't necessarily be so useful for standard installs, users of extensions such as Dash to Dock would find this highly useful. So it would be nice if this feature were at least supported so that they could implement it as such extensions are becoming more and more popular day by day. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1662688/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1807519] [NEW] xrandr fails setting panning on valid size
Public bug reported: I'm trying to downscale GNOME interface, and in order to do this, on X, I'm using `xrandr --scale 1.25x1.25`, which produces a larger view, which I'd like to fit to my screen size. So i'm trying to use the --panning option as follows: `xrandr --output eDP-1-1 --scale 1.25x1.25 --panning 1360x768` What happens is that the scale is applied but the panning is not, and throws the following error: X Error of failed request: BadMatch (invalid parameter attributes) Major opcode of failed request: 140 (RANDR) Minor opcode of failed request: 29 (RRSetPanning) Serial number of failed request: 32 Current serial number in output stream: 32 My xrandr output (`xrandr --prop`): Screen 0: minimum 8 x 8, current 1366 x 768, maximum 16384 x 16384 eDP-1-1 connected primary 1366x768+0+0 (normal left inverted right x axis y axis) 345mm x 194mm _MUTTER_PRESENTATION_OUTPUT: 0 EDID: 000030e45d04 00180103802313780a05f59458569228 1e50540001010101010101010101 010101010101d01d56f4500016303020 350059c21019 00fe004c 4720446973706c61790a202000fe 004c503135365748422d544c423100b7 PRIME Synchronization: 1 supported: 0, 1 scaling mode: Full aspect supported: Full, Center, Full aspect Broadcast RGB: Automatic supported: Automatic, Full, Limited 16:235 audio: auto supported: force-dvi, off, auto, on non-desktop: 0 range: (0, 1) link-status: Good supported: Good, Bad 1366x768 60.00*+ 1360x768 59.8059.96 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 VGA-1-1 disconnected (normal left inverted right x axis y axis) PRIME Synchronization: 1 supported: 0, 1 non-desktop: 0 range: (0, 1) link-status: Good supported: Good, Bad HDMI-1-1 disconnected (normal left inverted right x axis y axis) PRIME Synchronization: 1 supported: 0, 1 aspect ratio: Automatic supported: Automatic, 4:3, 16:9 Broadcast RGB: Automatic supported: Automatic, Full, Limited 16:235 audio: auto supported: force-dvi, off, auto, on non-desktop: 0 range: (0, 1) link-status: Good supported: Good, Bad ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: x11-xserver-utils 7.7+7build1 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 396.54 Tue Aug 14 19:02:34 PDT 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04) ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Sat Dec 8 19:38:30 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.15.0-39-generic, x86_64: installed bbswitch, 0.8, 4.15.0-42-generic, x86_64: installed nvidia, 396.54, 4.15.0-39-generic, x86_64: installed nvidia, 396.54, 4.15.0-42-generic, x86_64: installed GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated Graphics Controller [1043:178d] Subsystem: ASUSTeK Computer Inc.
[Desktop-packages] [Bug 1795021] Re: gsd-xsettings high memory usage
top -bn1 top - 18:53:10 up 19:16, 1 user, load average: 0,45, 0,99, 1,17 Tasks: 386 total, 1 running, 313 sleeping, 0 stopped, 0 zombie %Cpu(s): 3,9 us, 1,1 sy, 0,0 ni, 93,7 id, 1,2 wa, 0,0 hi, 0,1 si, 0,0 st KiB Mem : 8048180 total, 240784 free, 5832756 used, 1974640 buff/cache KiB Swap: 8191996 total, 8191996 free,0 used. 1807524 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 2874 fabio 20 0 4529612 481344 76580 S 16,7 6,0 69:27.09 gnome-shell 20862 fabio 20 0 1210128 442908 85532 S 5,6 5,5 1:39.43 chrome 1 root 20 0 226544 8328 4800 S 0,0 0,1 0:15.01 systemd 2 root 20 0 0 0 0 S 0,0 0,0 0:00.01 kthreadd 4 root 0 -20 0 0 0 I 0,0 0,0 0:00.00 kworker/0:+ 6 root 0 -20 0 0 0 I 0,0 0,0 0:00.00 mm_percpu_+ 7 root 20 0 0 0 0 S 0,0 0,0 0:00.26 ksoftirqd/0 8 root 20 0 0 0 0 I 0,0 0,0 0:28.09 rcu_sched 9 root 20 0 0 0 0 I 0,0 0,0 0:00.00 rcu_bh 10 root rt 0 0 0 0 S 0,0 0,0 0:00.03 migration/0 11 root rt 0 0 0 0 S 0,0 0,0 0:00.04 watchdog/0 12 root 20 0 0 0 0 S 0,0 0,0 0:00.00 cpuhp/0 13 root 20 0 0 0 0 S 0,0 0,0 0:00.00 cpuhp/1 14 root rt 0 0 0 0 S 0,0 0,0 0:00.05 watchdog/1 15 root rt 0 0 0 0 S 0,0 0,0 0:00.02 migration/1 16 root 20 0 0 0 0 S 0,0 0,0 0:00.11 ksoftirqd/1 18 root 0 -20 0 0 0 I 0,0 0,0 0:00.00 kworker/1:+ 19 root 20 0 0 0 0 S 0,0 0,0 0:00.00 cpuhp/2 20 root rt 0 0 0 0 S 0,0 0,0 0:00.05 watchdog/2 21 root rt 0 0 0 0 S 0,0 0,0 0:00.03 migration/2 22 root 20 0 0 0 0 S 0,0 0,0 0:00.07 ksoftirqd/2 24 root 0 -20 0 0 0 I 0,0 0,0 0:00.00 kworker/2:+ 25 root 20 0 0 0 0 S 0,0 0,0 0:00.00 cpuhp/3 26 root rt 0 0 0 0 S 0,0 0,0 0:00.05 watchdog/3 27 root rt 0 0 0 0 S 0,0 0,0 0:00.03 migration/3 28 root 20 0 0 0 0 S 0,0 0,0 0:00.19 ksoftirqd/3 30 root 0 -20 0 0 0 I 0,0 0,0 0:00.00 kworker/3:+ 31 root 20 0 0 0 0 S 0,0 0,0 0:00.00 cpuhp/4 32 root rt 0 0 0 0 S 0,0 0,0 0:00.05 watchdog/4 33 root rt 0 0 0 0 S 0,0 0,0 0:00.02 migration/4 34 root 20 0 0 0 0 S 0,0 0,0 0:00.09 ksoftirqd/4 36 root 0 -20 0 0 0 I 0,0 0,0 0:00.00 kworker/4:+ 37 root 20 0 0 0 0 S 0,0 0,0 0:00.00 cpuhp/5 38 root rt 0 0 0 0 S 0,0 0,0 0:00.05 watchdog/5 39 root rt 0 0 0 0 S 0,0 0,0 0:00.03 migration/5 40 root 20 0 0 0 0 S 0,0 0,0 0:00.08 ksoftirqd/5 42 root 0 -20 0 0 0 I 0,0 0,0 0:00.00 kworker/5:+ 43 root 20 0 0 0 0 S 0,0 0,0 0:00.00 cpuhp/6 44 root rt 0 0 0 0 S 0,0 0,0 0:00.05 watchdog/6 45 root rt 0 0 0 0 S 0,0 0,0 0:00.03 migration/6 46 root 20 0 0 0 0 S 0,0 0,0 0:00.07 ksoftirqd/6 48 root 0 -20 0 0 0 I 0,0 0,0 0:00.00 kworker/6:+ 49 root 20 0 0 0 0 S 0,0 0,0 0:00.00 cpuhp/7 50 root rt 0 0 0 0 S 0,0 0,0 0:00.05 watchdog/7 51 root rt 0 0 0 0 S 0,0 0,0 0:00.03 migration/7 52 root 20 0 0 0 0 S 0,0 0,0 0:00.19 ksoftirqd/7 54 root 0 -20 0 0 0 I 0,0 0,0 0:00.00 kworker/7:+ 55 root 20 0 0 0 0 S 0,0 0,0 0:00.00 kdevtmpfs 56 root 0 -20 0 0 0 I 0,0 0,0 0:00.00 netns 57 root 20 0 0 0 0 S 0,0 0,0 0:00.00 rcu_tasks_+ 58 root 20 0 0 0 0 S 0,0 0,0 0:00.00 kauditd 61 root 20 0 0 0 0 S 0,0 0,0 0:00.04 khungtaskd 62 root 20 0 0 0 0 S 0,0 0,0 0:00.00 oom_reaper 63 root 0 -20 0 0 0 I 0,0 0,0 0:00.00 writeback 64 root 20 0 0 0 0 S 0,0 0,0 0:00.00 kcompactd0 65 root 25 5 0 0 0 S 0,0 0,0 0:00.00 ksmd 66 root 39 19 0 0 0 S 0,0 0,0 0:00.00 khugepaged 67 root 0 -20 0 0 0 I 0,0 0,0 0:00.00
[Desktop-packages] [Bug 1795021] [NEW] gsd-xsettings high memory usage
Public bug reported: gsd-xsettings is using ~700MB of memory. I think there could be some memory leak because I don't remember it ever happening before. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-settings-daemon 3.28.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: communitheme:ubuntu:GNOME Date: Fri Sep 28 18:42:46 2018 InstallationDate: Installed on 2017-08-21 (403 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820) SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages ** Attachment added: "Gnome system monitor screenshot" https://bugs.launchpad.net/bugs/1795021/+attachment/5194125/+files/Screenshot%20from%202018-09-28%2018-47-33.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1795021 Title: gsd-xsettings high memory usage Status in gnome-settings-daemon package in Ubuntu: New Bug description: gsd-xsettings is using ~700MB of memory. I think there could be some memory leak because I don't remember it ever happening before. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-settings-daemon 3.28.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: communitheme:ubuntu:GNOME Date: Fri Sep 28 18:42:46 2018 InstallationDate: Installed on 2017-08-21 (403 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820) SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1795021/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1788807] [NEW] Bluetooth device not detected after resume from suspend
Public bug reported: When I suspend my laptop, it often happens that the bluetooth stops working. From gnome settings it is shown like if I had no bluetooth device at all. $ lspci -nnk | grep -iA3 net; lsusb; rfkill list; uname -r; dmesg | egrep -i 'blue|firm' 03:00.0 Network controller [0280]: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter [168c:0036] (rev 01) Subsystem: AzureWave QCA9565 / AR9565 Wireless Network Adapter [1a3b:2130] Kernel driver in use: ath9k Kernel modules: ath9k 04:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTL8411B PCI Express Card Reader [10ec:5287] (rev 01) -- 04:00.1 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 12) Subsystem: ASUSTeK Computer Inc. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [1043:200f] Kernel driver in use: r8169 Kernel modules: r8169 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:57b4 Realtek Semiconductor Corp. Bus 001 Device 006: ID 13d3:3408 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no 4.15.0-32-generic [0.024000] Spectre V2 : Enabling Restricted Speculation for firmware calls [0.048030] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored [2.758768] [Firmware Bug]: ACPI(PEGP) defines _DOD but not _DOS [ 35.407491] Bluetooth: Core ver 2.22 [ 35.407504] Bluetooth: HCI device and connection manager initialized [ 35.407506] Bluetooth: HCI socket layer initialized [ 35.407507] Bluetooth: L2CAP socket layer initialized [ 35.407510] Bluetooth: SCO socket layer initialized [ 53.501780] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 53.501780] Bluetooth: BNEP filters: protocol multicast [ 53.501783] Bluetooth: BNEP socket layer initialized [ 87.220137] Bluetooth: RFCOMM TTY layer initialized [ 87.220143] Bluetooth: RFCOMM socket layer initialized [ 87.220149] Bluetooth: RFCOMM ver 1.11 [ 1675.503865] usb 1-5: device firmware changed [ 1681.095543] Bluetooth: Can't get version to change to load ram patch err [ 1681.095546] Bluetooth: Loading patch file failed [ 4105.994687] audit: type=1107 audit(1534926184.213:339): pid=1258 uid=105 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/" interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" mask="send" name="org.bluez" pid=10248 label="snap.signal-desktop.signal-desktop" peer_pid=1314 peer_label="unconfined" Trying to use bluetooth from bluetoothctl $ bluetoothctl Agent registered [bluetooth]# scan on No default controller available Trying to restart the bluetooth service doesn't produce any effect: $ sudo service bluetooth restart Getting bluetooth service status: $ sudo service bluetooth status ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset Active: active (running) since Fri 2018-08-24 11:23:17 EEST; 1min 35s ago Docs: man:bluetoothd(8) Main PID: 24999 (bluetoothd) Status: "Running" Tasks: 1 (limit: 4915) CGroup: /system.slice/bluetooth.service └─24999 /usr/lib/bluetooth/bluetoothd elo 24 11:23:17 fabio-X550JK systemd[1]: Stopping Bluetooth service... elo 24 11:23:17 fabio-X550JK systemd[1]: Stopped Bluetooth service. elo 24 11:23:17 fabio-X550JK systemd[1]: Starting Bluetooth service... elo 24 11:23:17 fabio-X550JK bluetoothd[24999]: Bluetooth daemon 5.48 elo 24 11:23:17 fabio-X550JK systemd[1]: Started Bluetooth service. elo 24 11:23:17 fabio-X550JK bluetoothd[24999]: Starting SDP server elo 24 11:23:17 fabio-X550JK bluetoothd[24999]: Bluetooth management interface 1 lines 1-17/17 (END) Reloading the driver: $ sudo modprobe -r btusb; sudo modprobe btusb; $ sudo service bluetooth restart None of these attempts could solve the issue. What happens? Bluetooth is working, I suspend my laptop, I resume my laptop -> Bluetooth controller is no longer recognised and bluetooth service cannot be used anymore. What would you expect? Bluetooth controller to be recognised and working also after resume. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-bluetooth 3.28.0-2 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: communitheme:ubuntu:GNOME Date: Fri Aug 24 11:12:06 2018 InstallationDate: Installed on 2017-08-21 (367 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820) SourcePackage: gnome-bluetooth UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-bluetooth (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages -- You
[Desktop-packages] [Bug 1570721] Re: synaptic could not acquire dpkg lock
I didn't encounter this problem anymore, so it can probably be closed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1570721 Title: synaptic could not acquire dpkg lock Status in gnome-software package in Ubuntu: Incomplete Status in synaptic package in Ubuntu: Incomplete Bug description: After running gnome software center to search a package, I closed it and tried to open synaptic. After entering the password in the prompt, I was informed that synaptic could not acquire the lock on dpkg. Possible cause: I think this could be related to gnome software not releasing the lock, as there was no dpkg operation running at the moment. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: synaptic 0.83 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Apr 15 08:55:26 2016 InstallationDate: Installed on 2015-03-21 (390 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150321) SourcePackage: synaptic UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1570721/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1756901] Re: GNOME Calendar crashes when I try to add my Google Calendar account
Hi, I have gnome-calendar 3.26.3 and I still experience this bug. Also, whenever I try to open it again it crashes after few seconds. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1756901 Title: GNOME Calendar crashes when I try to add my Google Calendar account Status in gnome-calendar package in Ubuntu: Confirmed Bug description: I clicked the following: Manage your calendars -> Calendar settings, which led me to the Settings program, the Online Accounts section, selected "Google account", entered my data. My data was successfully taken. GNOME Calendar did not load my calendar and crashed. Upon restarting GNOME Calendar/restarting Ubuntu, it did not load my calendar either. Clicking "Synchronise" did not fix the situation either. Why do I think this is a security vulnerability? I am just a Computer Science student, but I imagine something might possibly come in the way so that personal data could be taken. It happens if I run the vanilla gnome-session as well. -Ubuntu Bionic Beaver (development branch), 18.04, on a fresh install. -GNOME Calendar version: 3.28.0-1 (Version table: 3.28.0-1 500) -What I expected to happen: load my Google Calendar data. -What happened instead: crashed, didn't load my Google Calendar data, even if my Google account data is loaded my GNOME. I hope Apport uploaded the debug information properly. If not, I can try to recreate the bug and upload the debug data, if necessary. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-calendar 3.28.0-1 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 19 16:40:14 2018 ExecutablePath: /usr/bin/gnome-calendar InstallationDate: Installed on 2018-03-19 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180319) ProcCmdline: /usr/bin/gnome-calendar --gapplication-service SegvAnalysis: Segfault happened at: 0x7f3513ec4d12 : mov(%rdi),%rbp PC (0x7f3513ec4d12) ok source "(%rdi)" (0x2c6e616d656c6f63) not located in a known VMA region (needed readable region)! destination "%rbp" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-calendar StacktraceTop: g_type_check_instance_cast () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-calendar crashed with SIGSEGV in g_type_check_instance_cast() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1756901/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1756901] Re: GNOME Calendar crashes when I try to add my Google Calendar account
Sorry for the confusion, I was using the snap version. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1756901 Title: GNOME Calendar crashes when I try to add my Google Calendar account Status in gnome-calendar package in Ubuntu: Confirmed Bug description: I clicked the following: Manage your calendars -> Calendar settings, which led me to the Settings program, the Online Accounts section, selected "Google account", entered my data. My data was successfully taken. GNOME Calendar did not load my calendar and crashed. Upon restarting GNOME Calendar/restarting Ubuntu, it did not load my calendar either. Clicking "Synchronise" did not fix the situation either. Why do I think this is a security vulnerability? I am just a Computer Science student, but I imagine something might possibly come in the way so that personal data could be taken. It happens if I run the vanilla gnome-session as well. -Ubuntu Bionic Beaver (development branch), 18.04, on a fresh install. -GNOME Calendar version: 3.28.0-1 (Version table: 3.28.0-1 500) -What I expected to happen: load my Google Calendar data. -What happened instead: crashed, didn't load my Google Calendar data, even if my Google account data is loaded my GNOME. I hope Apport uploaded the debug information properly. If not, I can try to recreate the bug and upload the debug data, if necessary. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-calendar 3.28.0-1 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 19 16:40:14 2018 ExecutablePath: /usr/bin/gnome-calendar InstallationDate: Installed on 2018-03-19 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180319) ProcCmdline: /usr/bin/gnome-calendar --gapplication-service SegvAnalysis: Segfault happened at: 0x7f3513ec4d12 : mov(%rdi),%rbp PC (0x7f3513ec4d12) ok source "(%rdi)" (0x2c6e616d656c6f63) not located in a known VMA region (needed readable region)! destination "%rbp" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-calendar StacktraceTop: g_type_check_instance_cast () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-calendar crashed with SIGSEGV in g_type_check_instance_cast() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1756901/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1689356] Re: UI scale being reset to 1 everytime when display sleeps for a while
Reference on how to write/read these values: https://askubuntu.com/a/510476 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1689356 Title: UI scale being reset to 1 everytime when display sleeps for a while Status in compiz package in Ubuntu: New Status in unity package in Ubuntu: New Status in unity-settings-daemon package in Ubuntu: Confirmed Bug description: After upgrading to Ubuntu 17.04, the HiDPI setting(Scale for menu and title bars) is being reset to 1 everytime when display sleeps for a while, making everything looks small. If the display sleeps and I resume it instantly, it's fine, but if the display slept for long, the HiDPI setting gets reset to 1. My guess is that if a display is plugged in(detected), the old DPI setting is not restored. This issue is not present on previous Ubuntu versions and the same issue persists even after a fresh install. *-* This bug is now present also in 16.04 since a recent update, experiencing this in Xenial since 23 Feb 2018 at least. We could trace the cause of the bug in the recent backports/bugfix updates to Xenial. *-* ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xorg 1:7.7+16ubuntu3 Uname: Linux 4.10.14-zen+ x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 375.66 Mon May 1 15:29:16 PDT 2017 GCC version: gcc version 6.3.0 20170406 (Ubuntu 6.3.0-12ubuntu2) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. .tmp.unity_support_test.0: ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity:Unity7 Date: Tue May 9 02:08:25 2017 DistUpgraded: Fresh install DistroCodename: zesty DistroVariant: ubuntu DkmsStatus: nvidia, 375.66, 4.10.14-zen+, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1080] [10de:1b80] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP104 [GeForce GTX 1080] [1043:85aa] Advanced Micro Devices, Inc. [AMD/ATI] Bonaire XTX [Radeon R7 260X/360] [1002:6658] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Bonaire XTX [Radeon R7 260X/360] [1458:227b] InstallationDate: Installed on 2017-05-06 (1 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: ASUS All Series ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.14-zen+ root=UUID=e1130f0b-d82f-4976-989f-c8b18f0965eb ro intel_iommu=on vfio_iommu_type1.allow_unsafe_interrupts=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/18/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3402 dmi.board.asset.tag: Default string dmi.board.name: X99-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3402:bd08/18/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnX99-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.3-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.14-0ubuntu1 xserver.bootTime: Tue May
[Desktop-packages] [Bug 1689356] Re: UI scale being reset to 1 everytime when display sleeps for a while
Temporary workaround for me is to use
dconf read /com/ubuntu/user-interface/scale-factor
to read the value when the setting is still correct, then copy the
output and assign it back with
dconf write /com/ubuntu/user-interface/scale-factor "{'DP-6': 16}"
Note that this dconf value gets resetted every time this bug happens, so you
have set it again. Anyway I find it faster to just have it as a command.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1689356
Title:
UI scale being reset to 1 everytime when display sleeps for a while
Status in compiz package in Ubuntu:
New
Status in unity package in Ubuntu:
New
Status in unity-settings-daemon package in Ubuntu:
Confirmed
Bug description:
After upgrading to Ubuntu 17.04,
the HiDPI setting(Scale for menu and title bars)
is being reset to 1 everytime when display sleeps for a while,
making everything looks small.
If the display sleeps and I resume it instantly, it's fine,
but if the display slept for long, the HiDPI setting gets reset to 1.
My guess is that if a display is plugged in(detected), the old DPI
setting is not restored.
This issue is not present on previous Ubuntu versions
and the same issue persists even after a fresh install.
*-*
This bug is now present also in 16.04 since a recent update, experiencing
this in Xenial since 23 Feb 2018 at least. We could trace the cause of the bug
in the recent backports/bugfix updates to Xenial.
*-*
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: xorg 1:7.7+16ubuntu3
Uname: Linux 4.10.14-zen+ x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory:
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 375.66 Mon May 1 15:29:16
PDT 2017
GCC version: gcc version 6.3.0 20170406 (Ubuntu 6.3.0-12ubuntu2)
.proc.driver.nvidia.warnings.fbdev:
Your system is not currently configured to drive a VGA console
on the primary VGA device. The NVIDIA Linux graphics driver
requires the use of a text-mode VGA console. Use of other console
drivers including, but not limited to, vesafb, may result in
corruption and stability problems, and is not supported.
.tmp.unity_support_test.0:
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity:Unity7
Date: Tue May 9 02:08:25 2017
DistUpgraded: Fresh install
DistroCodename: zesty
DistroVariant: ubuntu
DkmsStatus: nvidia, 375.66, 4.10.14-zen+, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
NVIDIA Corporation GP104 [GeForce GTX 1080] [10de:1b80] (rev a1) (prog-if 00
[VGA controller])
Subsystem: ASUSTeK Computer Inc. GP104 [GeForce GTX 1080] [1043:85aa]
Advanced Micro Devices, Inc. [AMD/ATI] Bonaire XTX [Radeon R7 260X/360]
[1002:6658] (prog-if 00 [VGA controller])
Subsystem: Gigabyte Technology Co., Ltd Bonaire XTX [Radeon R7 260X/360]
[1458:227b]
InstallationDate: Installed on 2017-05-06 (1 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: ASUS All Series
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.14-zen+
root=UUID=e1130f0b-d82f-4976-989f-c8b18f0965eb ro intel_iommu=on
vfio_iommu_type1.allow_unsafe_interrupts=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/18/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3402
dmi.board.asset.tag: Default string
dmi.board.name: X99-A
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr3402:bd08/18/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnX99-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.name: All Series
dmi.product.version: System Version
dmi.sys.vendor: ASUS
version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.76-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.3-1ubuntu1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1
[Desktop-packages] [Bug 1689356] Re: UI scale being reset to 1 everytime when display sleeps for a while
** Also affects: unity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1689356 Title: UI scale being reset to 1 everytime when display sleeps for a while Status in compiz package in Ubuntu: New Status in unity package in Ubuntu: New Status in unity-settings-daemon package in Ubuntu: Confirmed Bug description: After upgrading to Ubuntu 17.04, the HiDPI setting(Scale for menu and title bars) is being reset to 1 everytime when display sleeps for a while, making everything looks small. If the display sleeps and I resume it instantly, it's fine, but if the display slept for long, the HiDPI setting gets reset to 1. My guess is that if a display is plugged in(detected), the old DPI setting is not restored. This issue is not present on previous Ubuntu versions and the same issue persists even after a fresh install. *-* This bug is now present also in 16.04 since a recent update, experiencing this in Xenial since 23 Feb 2018 at least. We could trace the cause of the bug in the recent backports/bugfix updates to Xenial. *-* ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xorg 1:7.7+16ubuntu3 Uname: Linux 4.10.14-zen+ x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 375.66 Mon May 1 15:29:16 PDT 2017 GCC version: gcc version 6.3.0 20170406 (Ubuntu 6.3.0-12ubuntu2) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. .tmp.unity_support_test.0: ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity:Unity7 Date: Tue May 9 02:08:25 2017 DistUpgraded: Fresh install DistroCodename: zesty DistroVariant: ubuntu DkmsStatus: nvidia, 375.66, 4.10.14-zen+, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1080] [10de:1b80] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP104 [GeForce GTX 1080] [1043:85aa] Advanced Micro Devices, Inc. [AMD/ATI] Bonaire XTX [Radeon R7 260X/360] [1002:6658] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Bonaire XTX [Radeon R7 260X/360] [1458:227b] InstallationDate: Installed on 2017-05-06 (1 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: ASUS All Series ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.14-zen+ root=UUID=e1130f0b-d82f-4976-989f-c8b18f0965eb ro intel_iommu=on vfio_iommu_type1.allow_unsafe_interrupts=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/18/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3402 dmi.board.asset.tag: Default string dmi.board.name: X99-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3402:bd08/18/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnX99-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.3-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.14-0ubuntu1 xserver.bootTime: Tue May
[Desktop-packages] [Bug 1689356] Re: UI scale being reset to 1 everytime when display sleeps for a while
** Description changed: After upgrading to Ubuntu 17.04, the HiDPI setting(Scale for menu and title bars) is being reset to 1 everytime when display sleeps for a while, making everything looks small. If the display sleeps and I resume it instantly, it's fine, but if the display slept for long, the HiDPI setting gets reset to 1. My guess is that if a display is plugged in(detected), the old DPI setting is not restored. This issue is not present on previous Ubuntu versions and the same issue persists even after a fresh install. + *-* + This bug is now present also in 16.04 since a recent update, experiencing this in Xenial since 23 Feb 2018 at least. We could trace the cause of the bug in the recent backports/bugfix updates to Xenial. + *-* + ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xorg 1:7.7+16ubuntu3 Uname: Linux 4.10.14-zen+ x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: - NVRM version: NVIDIA UNIX x86_64 Kernel Module 375.66 Mon May 1 15:29:16 PDT 2017 - GCC version: gcc version 6.3.0 20170406 (Ubuntu 6.3.0-12ubuntu2) + NVRM version: NVIDIA UNIX x86_64 Kernel Module 375.66 Mon May 1 15:29:16 PDT 2017 + GCC version: gcc version 6.3.0 20170406 (Ubuntu 6.3.0-12ubuntu2) .proc.driver.nvidia.warnings.fbdev: - Your system is not currently configured to drive a VGA console - on the primary VGA device. The NVIDIA Linux graphics driver - requires the use of a text-mode VGA console. Use of other console - drivers including, but not limited to, vesafb, may result in - corruption and stability problems, and is not supported. + Your system is not currently configured to drive a VGA console + on the primary VGA device. The NVIDIA Linux graphics driver + requires the use of a text-mode VGA console. Use of other console + drivers including, but not limited to, vesafb, may result in + corruption and stability problems, and is not supported. .tmp.unity_support_test.0: - + ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity:Unity7 Date: Tue May 9 02:08:25 2017 DistUpgraded: Fresh install DistroCodename: zesty DistroVariant: ubuntu DkmsStatus: nvidia, 375.66, 4.10.14-zen+, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: - NVIDIA Corporation GP104 [GeForce GTX 1080] [10de:1b80] (rev a1) (prog-if 00 [VGA controller]) -Subsystem: ASUSTeK Computer Inc. GP104 [GeForce GTX 1080] [1043:85aa] - Advanced Micro Devices, Inc. [AMD/ATI] Bonaire XTX [Radeon R7 260X/360] [1002:6658] (prog-if 00 [VGA controller]) -Subsystem: Gigabyte Technology Co., Ltd Bonaire XTX [Radeon R7 260X/360] [1458:227b] + NVIDIA Corporation GP104 [GeForce GTX 1080] [10de:1b80] (rev a1) (prog-if 00 [VGA controller]) + Subsystem: ASUSTeK Computer Inc. GP104 [GeForce GTX 1080] [1043:85aa] + Advanced Micro Devices, Inc. [AMD/ATI] Bonaire XTX [Radeon R7 260X/360] [1002:6658] (prog-if 00 [VGA controller]) + Subsystem: Gigabyte Technology Co., Ltd Bonaire XTX [Radeon R7 260X/360] [1458:227b] InstallationDate: Installed on 2017-05-06 (1 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: ASUS All Series ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.14-zen+ root=UUID=e1130f0b-d82f-4976-989f-c8b18f0965eb ro intel_iommu=on vfio_iommu_type1.allow_unsafe_interrupts=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/18/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3402 dmi.board.asset.tag: Default string dmi.board.name: X99-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3402:bd08/18/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnX99-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.3-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
[Desktop-packages] [Bug 1689356] Re: UI scale being reset to 1 everytime when display sleeps for a while
Happening to me as well since few days. I tough it was a configuration issue, but probably this is a regression caused by some backport. ** Tags added: regression-update ** Tags added: verification-done-xenial xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1689356 Title: UI scale being reset to 1 everytime when display sleeps for a while Status in unity-settings-daemon package in Ubuntu: Confirmed Bug description: After upgrading to Ubuntu 17.04, the HiDPI setting(Scale for menu and title bars) is being reset to 1 everytime when display sleeps for a while, making everything looks small. If the display sleeps and I resume it instantly, it's fine, but if the display slept for long, the HiDPI setting gets reset to 1. My guess is that if a display is plugged in(detected), the old DPI setting is not restored. This issue is not present on previous Ubuntu versions and the same issue persists even after a fresh install. *-* This bug is now present also in 16.04 since a recent update, experiencing this in Xenial since 23 Feb 2018 at least. We could trace the cause of the bug in the recent backports/bugfix updates to Xenial. *-* ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xorg 1:7.7+16ubuntu3 Uname: Linux 4.10.14-zen+ x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 375.66 Mon May 1 15:29:16 PDT 2017 GCC version: gcc version 6.3.0 20170406 (Ubuntu 6.3.0-12ubuntu2) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. .tmp.unity_support_test.0: ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity:Unity7 Date: Tue May 9 02:08:25 2017 DistUpgraded: Fresh install DistroCodename: zesty DistroVariant: ubuntu DkmsStatus: nvidia, 375.66, 4.10.14-zen+, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1080] [10de:1b80] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP104 [GeForce GTX 1080] [1043:85aa] Advanced Micro Devices, Inc. [AMD/ATI] Bonaire XTX [Radeon R7 260X/360] [1002:6658] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Bonaire XTX [Radeon R7 260X/360] [1458:227b] InstallationDate: Installed on 2017-05-06 (1 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: ASUS All Series ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.14-zen+ root=UUID=e1130f0b-d82f-4976-989f-c8b18f0965eb ro intel_iommu=on vfio_iommu_type1.allow_unsafe_interrupts=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/18/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3402 dmi.board.asset.tag: Default string dmi.board.name: X99-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3402:bd08/18/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnX99-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.3-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau:
[Desktop-packages] [Bug 1740106] [NEW] Gnome terminal not starting, timeout reached (bionic)
Public bug reported: After a having my memory filled I had to reboot because the system got unresponsive. After that I can no longer open gnome terminal. I tried running it from xterm and the following message appears: Error constructing proxy for org.gnome.Terminal:/org/gnome/Terminal/Factory0: Error calling StartServiceByName for org.gnome.Terminal: Timeout was reached ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-terminal 3.24.2-0ubuntu4 ProcVersionSignature: Ubuntu 4.14.0-11.13-generic 4.14.3 Uname: Linux 4.14.0-11-generic x86_64 ApportVersion: 2.20.8-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Dec 26 10:38:26 2017 InstallationDate: Installed on 2017-08-21 (126 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Summary changed: - Error constructing proxy for org.gnome.Terminal + Gnome terminal not starting, timeout reached (bionic) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1740106 Title: Gnome terminal not starting, timeout reached (bionic) Status in gnome-terminal package in Ubuntu: New Bug description: After a having my memory filled I had to reboot because the system got unresponsive. After that I can no longer open gnome terminal. I tried running it from xterm and the following message appears: Error constructing proxy for org.gnome.Terminal:/org/gnome/Terminal/Factory0: Error calling StartServiceByName for org.gnome.Terminal: Timeout was reached ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-terminal 3.24.2-0ubuntu4 ProcVersionSignature: Ubuntu 4.14.0-11.13-generic 4.14.3 Uname: Linux 4.14.0-11-generic x86_64 ApportVersion: 2.20.8-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Dec 26 10:38:26 2017 InstallationDate: Installed on 2017-08-21 (126 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1740106/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1732450] Re: Lock screen doesn't respect gnome shell theme choice
This bug has now been reported upstream: https://bugzilla.gnome.org/show_bug.cgi?id=791299 ** Bug watch added: GNOME Bug Tracker #791299 https://bugzilla.gnome.org/show_bug.cgi?id=791299 ** Also affects: gnome-shell via https://bugzilla.gnome.org/show_bug.cgi?id=791299 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1732450 Title: Lock screen doesn't respect gnome shell theme choice Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: New Bug description: The lockscreen theme doesn't follow the selected gnome shell theme, as it used to do, but instead it always uses gnome-shell.css if logged in as Gnome session or ubuntu.css if logged as Ubuntu session. The currently selected gdm theme is ubuntu.css, but after login it's not respected either. ``` There are 3 choices for the alternative gdm3.css (providing /usr/share/gnome-shell/theme/gdm3.css). SelectionPath Priority Status 0/usr/share/gnome-shell/theme/pop.css 20auto mode 1/usr/share/gnome-shell/theme/gnome-shell.css 5 manual mode 2/usr/share/gnome-shell/theme/pop.css 20 manual mode * 3/usr/share/gnome-shell/theme/ubuntu.css10 manual mode ``` The selected shell theme is Arc-Darker, from the Ubuntu repositories. This happens both in the Wayland and Xorg sessions. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.26.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 ApportVersion: 2.20.7-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Nov 15 15:31:14 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-08-21 (85 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1732450/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1731310] Re: nautilus doesn't align icons properly when name is long
I don't see this happening anymore ** Changed in: nautilus (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1731310 Title: nautilus doesn't align icons properly when name is long Status in nautilus package in Ubuntu: Fix Released Bug description: Nautilus icons with long text are not aligned properly to the grid ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Nov 9 19:28:36 2017 InstallationDate: Installed on 2017-08-21 (80 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1731310/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1710382] Re: Wireless network frequently drops in 17.10
Can you check bug 1736690 to see if it's the same bug as this? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1710382 Title: Wireless network frequently drops in 17.10 Status in network-manager package in Ubuntu: Confirmed Bug description: On a fairly clean 17.10 install, on a Thinkpad T450, the wireless connection keeps dropping. Other devices nearby do not suffer the same way. I can turn the wifi off and on again to get reconnected. It happens multiple times over a short period of an hour or so. So quite irritating. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: network-manager 1.8.2-1ubuntu2 ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12 Uname: Linux 4.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Aug 12 15:52:20 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-08-02 (9 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170712) IpRoute: default via 192.168.1.1 dev wlp3s0 proto static metric 600 10.124.121.0/24 dev lxdbr0 proto kernel scope link src 10.124.121.1 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.95 metric 600 NetworkManager.conf: [main] plugins=ifupdown,keyfile [ifupdown] managed=false NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH lxdbr0 bridgeconnected/org/freedesktop/NetworkManager/Devices/27 lxdbr0 9e57f30a-21b5-4f87-aa76-06a328c24462 /org/freedesktop/NetworkManager/ActiveConnection/10 wlp3s0 wifi connected/org/freedesktop/NetworkManager/Devices/3 popey b83cf629-38b9-47dc-8916-3aaa2868e90a /org/freedesktop/NetworkManager/ActiveConnection/6 enp0s25 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.8.2connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1710382/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1736690] [NEW] [Bionic] WiFi connection keeps dropping after some time
Public bug reported: >From time to time my wireless network connection drops. It works again for some time and then it suddenly drops again. When this happens, I switch the wifi setting off and on again (from GNOME settings). As wifi is on again, I get connected again and everything works again for some time (could be half an hour as few hours). This bug is a possible duplicate of 1710382, but I'm reporting it from bionic. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.8.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.14.0-11.13-generic 4.14.3 Uname: Linux 4.14.0-11-generic x86_64 ApportVersion: 2.20.8-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Dec 6 11:26:06 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-08-21 (106 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820) IpRoute: default via 192.168.0.1 dev wlp3s0 proto static metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.0.0/24 dev wlp3s0 proto kernel scope link src 192.168.0.202 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICETYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp3s0wifi connected/org/freedesktop/NetworkManager/Devices/3 ~ ~ S h i n w a r y o k u ~ ~ 46fc1e57-8d59-4681-b79a-13f8504317ce /org/freedesktop/NetworkManager/ActiveConnection/2 enp4s0f1 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- loloopback unmanaged/org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.8.4connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1736690 Title: [Bionic] WiFi connection keeps dropping after some time Status in network-manager package in Ubuntu: New Bug description: From time to time my wireless network connection drops. It works again for some time and then it suddenly drops again. When this happens, I switch the wifi setting off and on again (from GNOME settings). As wifi is on again, I get connected again and everything works again for some time (could be half an hour as few hours). This bug is a possible duplicate of 1710382, but I'm reporting it from bionic. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.8.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.14.0-11.13-generic 4.14.3 Uname: Linux 4.14.0-11-generic x86_64 ApportVersion: 2.20.8-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Dec 6 11:26:06 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-08-21 (106 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820) IpRoute: default via 192.168.0.1 dev wlp3s0 proto static metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.0.0/24 dev wlp3s0 proto kernel scope link src 192.168.0.202 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICETYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp3s0wifi connected/org/freedesktop/NetworkManager/Devices/3 ~ ~ S h i n w a r y o k u ~ ~ 46fc1e57-8d59-4681-b79a-13f8504317ce /org/freedesktop/NetworkManager/ActiveConnection/2 enp4s0f1 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- loloopback unmanaged/org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI
[Desktop-packages] [Bug 1732450] [NEW] Lock screen doesn't respect gnome shell theme choice
Public bug reported: The lockscreen theme doesn't follow the selected gnome shell theme, as it used to do, but instead it always uses gnome-shell.css if logged in as Gnome session or ubuntu.css if logged as Ubuntu session. The currently selected gdm theme is ubuntu.css, but after login it's not respected either. ``` There are 3 choices for the alternative gdm3.css (providing /usr/share/gnome-shell/theme/gdm3.css). SelectionPath Priority Status 0/usr/share/gnome-shell/theme/pop.css 20auto mode 1/usr/share/gnome-shell/theme/gnome-shell.css 5 manual mode 2/usr/share/gnome-shell/theme/pop.css 20manual mode * 3/usr/share/gnome-shell/theme/ubuntu.css10manual mode ``` The selected shell theme is Arc-Darker, from the Ubuntu repositories. This happens both in the Wayland and Xorg sessions. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.26.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 ApportVersion: 2.20.7-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Nov 15 15:31:14 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-08-21 (85 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Description changed: - When I log in into a gnome session, the lockscreen theme doesn't follow - the selected gnome shell theme, as it used to do, but instead it always - uses the Adwaita theme (gnome-shell.css). + The lockscreen theme doesn't follow the selected gnome shell theme, as + it used to do, but instead it always uses gnome-shell.css if logged in + as Gnome session or ubuntu.css if logged as Ubuntu session. - This is not even the gdm theme, otherwise it would be using ubuntu.css, - but it's not. + The currently selected gdm theme is ubuntu.css, but after login it's not + respected either. - There are 3 choices for the alternative gdm3.css (providing /usr/share - /gnome-shell/theme/gdm3.css). + ``` + There are 3 choices for the alternative gdm3.css (providing /usr/share/gnome-shell/theme/gdm3.css). - SelectionPath Priority Status + SelectionPath Priority Status - 0/usr/share/gnome-shell/theme/pop.css 20auto mode - 1/usr/share/gnome-shell/theme/gnome-shell.css 5 manual mode - 2/usr/share/gnome-shell/theme/pop.css 20 manual mode + 0/usr/share/gnome-shell/theme/pop.css 20auto mode + 1/usr/share/gnome-shell/theme/gnome-shell.css 5 manual mode + 2/usr/share/gnome-shell/theme/pop.css 20 manual mode * 3/usr/share/gnome-shell/theme/ubuntu.css10 manual mode + ``` The selected shell theme is Arc-Darker, from the Ubuntu repositories. This happens both in the Wayland and Xorg sessions. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.26.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 ApportVersion: 2.20.7-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Nov 15 15:31:14 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-08-21 (85 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1732450 Title: Lock screen doesn't respect gnome shell theme choice Status in gnome-shell package in Ubuntu: New Bug description: The lockscreen theme doesn't follow the selected gnome shell theme, as it used to do, but instead it always uses gnome-shell.css if logged in as Gnome session or ubuntu.css if logged as Ubuntu session. The currently selected gdm theme is ubuntu.css, but after login it's not respected either. ``` There are 3 choices for the alternative gdm3.css (providing /usr/share/gnome-shell/theme/gdm3.css). SelectionPath Priority Status 0/usr/share/gnome-shell/theme/pop.css 20auto mode 1
[Desktop-packages] [Bug 1731310] [NEW] nautilus doesn't align icons properly when name is long
Public bug reported: Nautilus icons with long text are not aligned properly to the grid ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Nov 9 19:28:36 2017 InstallationDate: Installed on 2017-08-21 (80 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic regression-proposed ** Attachment added: "Screenshot from 2017-11-09 19-28-19.png" https://bugs.launchpad.net/bugs/1731310/+attachment/5006621/+files/Screenshot%20from%202017-11-09%2019-28-19.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1731310 Title: nautilus doesn't align icons properly when name is long Status in nautilus package in Ubuntu: New Bug description: Nautilus icons with long text are not aligned properly to the grid ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Nov 9 19:28:36 2017 InstallationDate: Installed on 2017-08-21 (80 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1731310/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1731030] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1731030/+attachment/5006516/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1731030 Title: PS3 Controller causes screen to rotate Status in gnome-session package in Ubuntu: New Status in xserver-xorg-input-libinput package in Ubuntu: New Bug description: When I attach and turn on my PS3 controller to my laptop, the screen get's rotated of 180 degrees. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-session 3.26.1-0ubuntu7 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 8 21:31:47 2017 InstallationDate: Installed on 2017-08-21 (79 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820) SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.7-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2017-08-21 (79 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820) Package: xserver-xorg-input-libinput PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Tags: bionic Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1731030/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1731030] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1731030/+attachment/5006515/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1731030 Title: PS3 Controller causes screen to rotate Status in gnome-session package in Ubuntu: New Status in xserver-xorg-input-libinput package in Ubuntu: New Bug description: When I attach and turn on my PS3 controller to my laptop, the screen get's rotated of 180 degrees. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-session 3.26.1-0ubuntu7 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 8 21:31:47 2017 InstallationDate: Installed on 2017-08-21 (79 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820) SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.7-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2017-08-21 (79 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820) Package: xserver-xorg-input-libinput PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Tags: bionic Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1731030/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1731030] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1731030/+attachment/5006514/+files/JournalErrors.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1731030 Title: PS3 Controller causes screen to rotate Status in gnome-session package in Ubuntu: New Status in xserver-xorg-input-libinput package in Ubuntu: New Bug description: When I attach and turn on my PS3 controller to my laptop, the screen get's rotated of 180 degrees. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-session 3.26.1-0ubuntu7 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 8 21:31:47 2017 InstallationDate: Installed on 2017-08-21 (79 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820) SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.7-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2017-08-21 (79 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820) Package: xserver-xorg-input-libinput PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Tags: bionic Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1731030/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1731030] Re: PS3 Controller causes screen to rotate
apport information ** Tags added: apport-collected ** Description changed: When I attach and turn on my PS3 controller to my laptop, the screen get's rotated of 180 degrees. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-session 3.26.1-0ubuntu7 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 8 21:31:47 2017 InstallationDate: Installed on 2017-08-21 (79 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820) SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) + --- + ApportVersion: 2.20.7-0ubuntu4 + Architecture: amd64 + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2017-08-21 (79 days ago) + InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820) + Package: xserver-xorg-input-libinput + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 + Tags: bionic + Uname: Linux 4.13.0-16-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1731030/+attachment/5006513/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1731030 Title: PS3 Controller causes screen to rotate Status in gnome-session package in Ubuntu: New Status in xserver-xorg-input-libinput package in Ubuntu: New Bug description: When I attach and turn on my PS3 controller to my laptop, the screen get's rotated of 180 degrees. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-session 3.26.1-0ubuntu7 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 8 21:31:47 2017 InstallationDate: Installed on 2017-08-21 (79 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820) SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.7-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2017-08-21 (79 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820) Package: xserver-xorg-input-libinput PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Tags: bionic Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1731030/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1731030] Re: PS3 Controller causes screen to rotate
** Also affects: libinput (Ubuntu) Importance: Undecided Status: New ** No longer affects: libinput (Ubuntu) ** Also affects: xserver-xorg-input-libinput (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1731030 Title: PS3 Controller causes screen to rotate Status in gnome-session package in Ubuntu: New Status in xserver-xorg-input-libinput package in Ubuntu: New Bug description: When I attach and turn on my PS3 controller to my laptop, the screen get's rotated of 180 degrees. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-session 3.26.1-0ubuntu7 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 8 21:31:47 2017 InstallationDate: Installed on 2017-08-21 (79 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820) SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.7-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2017-08-21 (79 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820) Package: xserver-xorg-input-libinput PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Tags: bionic Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1731030/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1731030] Re: PS3 Controller causes screen to rotate
This happens both with Xorg and Wayland sessions. The controller is an original Dualshock 3 Contoller. If I just plug the controller in it doesn't cause any screen rotation, but pressing the "home button" triggers the issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1731030 Title: PS3 Controller causes screen to rotate Status in gnome-session package in Ubuntu: New Bug description: When I attach and turn on my PS3 controller to my laptop, the screen get's rotated of 180 degrees. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-session 3.26.1-0ubuntu7 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 8 21:31:47 2017 InstallationDate: Installed on 2017-08-21 (79 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820) SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1731030/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1731030] [NEW] PS3 Controller causes screen to rotate
Public bug reported: When I attach and turn on my PS3 controller to my laptop, the screen get's rotated of 180 degrees. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-session 3.26.1-0ubuntu7 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 8 21:31:47 2017 InstallationDate: Installed on 2017-08-21 (79 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820) SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-session (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "VID_20171108_212004.mp4" https://bugs.launchpad.net/bugs/1731030/+attachment/5005983/+files/VID_20171108_212004.mp4 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1731030 Title: PS3 Controller causes screen to rotate Status in gnome-session package in Ubuntu: New Bug description: When I attach and turn on my PS3 controller to my laptop, the screen get's rotated of 180 degrees. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-session 3.26.1-0ubuntu7 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 8 21:31:47 2017 InstallationDate: Installed on 2017-08-21 (79 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820) SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1731030/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1716579] [NEW] gnome-software uses a very high cpu amount
Public bug reported: The room was silent, when the fan of my laptop suddenly started making noise. I checked it and it was because of the intense amount of CPU in use because of gnome software. Gnome Software CPU use was over 60%. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-software 3.25.91-1ubuntu5 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 12 08:29:01 2017 InstallationDate: Installed on 2017-08-21 (21 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.25.91-1ubuntu5 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful ** Attachment added: "Screenshot from 2017-09-12 08-28-20.png" https://bugs.launchpad.net/bugs/1716579/+attachment/4948471/+files/Screenshot%20from%202017-09-12%2008-28-20.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1716579 Title: gnome-software uses a very high cpu amount Status in gnome-software package in Ubuntu: New Bug description: The room was silent, when the fan of my laptop suddenly started making noise. I checked it and it was because of the intense amount of CPU in use because of gnome software. Gnome Software CPU use was over 60%. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-software 3.25.91-1ubuntu5 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 12 08:29:01 2017 InstallationDate: Installed on 2017-08-21 (21 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.25.91-1ubuntu5 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1716579/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1716201] [NEW] gnome software continuously takes more memory
Public bug reported: After opening gnome software, it starts taking more and more memory in big chunks, around 80MB per second. While I'm writing this report it has already taken 3.1GB of memory. As time passes it also asks more CPU, taking sometimes up to 33% on my machine. Reproduce: - kill any instance of gnome software - open gnome software - watch it eat all your memory This doesn't happen every time. When it happened to me I had just killed gnome software because it was taking a lot of CPU. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-software 3.25.91-1ubuntu5 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Sep 10 09:45:29 2017 InstallationDate: Installed on 2017-08-21 (19 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.25.91-1ubuntu5 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1716201 Title: gnome software continuously takes more memory Status in gnome-software package in Ubuntu: New Bug description: After opening gnome software, it starts taking more and more memory in big chunks, around 80MB per second. While I'm writing this report it has already taken 3.1GB of memory. As time passes it also asks more CPU, taking sometimes up to 33% on my machine. Reproduce: - kill any instance of gnome software - open gnome software - watch it eat all your memory This doesn't happen every time. When it happened to me I had just killed gnome software because it was taking a lot of CPU. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-software 3.25.91-1ubuntu5 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Sep 10 09:45:29 2017 InstallationDate: Installed on 2017-08-21 (19 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.25.91-1ubuntu5 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1716201/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1696621] Re: Desktop icons slip under the top bar after logging in
If I open nautilus the icons suddenly move in an appropriate position. Look duplicate bug #1705285 for screenshots of before and after opening nautilus. ** Tags added: julyshakedown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1696621 Title: Desktop icons slip under the top bar after logging in Status in GNOME Shell: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in nautilus package in Ubuntu: Confirmed Bug description: Desktop icons slip under the top bar after logging in again. If I place icons on the desktop in Gnome Shell they look fine, until I log out and log in again. On the second login they have moved half under the top bar. The same problem is visible in the Ubuntu live session starting with 20170607. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1696621/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1705280] [NEW] Gnome software fails to install snap apps with classic confinement
*** This bug is a duplicate of bug 1705023 *** https://bugs.launchpad.net/bugs/1705023 Public bug reported: I'm trying to install the anbox-installer snap from gnome-software and it fails without any advice. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-software 3.24.3-0ubuntu6 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Jul 19 16:22:02 2017 InstallationDate: Installed on 2015-03-21 (851 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150321) InstalledPlugins: gnome-software-plugin-flatpak 3.24.3-0ubuntu6 gnome-software-plugin-limba N/A gnome-software-plugin-snap3.24.3-0ubuntu6 SourcePackage: gnome-software UpgradeStatus: Upgraded to artful on 2017-07-18 (1 days ago) ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful julyshakedown third-party-packages ** Tags added: julyshakedown ** This bug has been marked a duplicate of bug 1705023 Do not promote or show classic snaps as installable or display the warning before installation -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1705280 Title: Gnome software fails to install snap apps with classic confinement Status in gnome-software package in Ubuntu: New Bug description: I'm trying to install the anbox-installer snap from gnome-software and it fails without any advice. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-software 3.24.3-0ubuntu6 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Jul 19 16:22:02 2017 InstallationDate: Installed on 2015-03-21 (851 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150321) InstalledPlugins: gnome-software-plugin-flatpak 3.24.3-0ubuntu6 gnome-software-plugin-limba N/A gnome-software-plugin-snap3.24.3-0ubuntu6 SourcePackage: gnome-software UpgradeStatus: Upgraded to artful on 2017-07-18 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1705280/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1705122] Re: Installed snaps do not appear among other apps in menus when using Wayland
This issue happens only under Wayland sessions. ** Summary changed: - installed snaps do not appear among other apps in menus + Installed snaps do not appear among other apps in menus when using Wayland ** Also affects: wayland (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1705122 Title: Installed snaps do not appear among other apps in menus when using Wayland Status in snapd package in Ubuntu: New Status in wayland package in Ubuntu: New Bug description: I installed the snap telegram-sergiusens but it doesn't appear among the other applications in the menu and I can't search for it from the Activities menu (GNOME Shell). I'm trying this from a Wayland session, I don't know if this can be related in any way. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: snapd 2.26.10+17.10 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Jul 18 22:39:57 2017 InstallationDate: Installed on 2015-03-21 (850 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150321) SourcePackage: snapd UpgradeStatus: Upgraded to artful on 2017-07-18 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1705122/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1705124] Re: snap apps have blurry icons
This happens only under Wayland sessions. On X the icons appears correctly. ** Also affects: wayland (Ubuntu) Importance: Undecided Status: New ** Summary changed: - snap apps have blurry icons + Snap apps have blurry icons in Wayland session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1705124 Title: Snap apps have blurry icons in Wayland session Status in snapd package in Ubuntu: New Status in wayland package in Ubuntu: New Bug description: I installed telegram-sergiusens but as per bug #1705122 I could not launch it from the menu. So I started it from GNOME Software using the Launch button. The icon appears terribly blurred. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: snapd 2.26.10+17.10 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Jul 18 22:45:42 2017 InstallationDate: Installed on 2015-03-21 (850 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150321) SourcePackage: snapd UpgradeStatus: Upgraded to artful on 2017-07-18 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1705124/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1697481] [NEW] totem-video-thumbnailer crashed with signal 5 in g_malloc()
Public bug reported: Every time I open a folder with MTS video files the video thumbnailer crashes. It would be ok, if it just failed gracefully. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: libgstreamer1.0-0 1.8.3-1~ubuntu0.1 ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-54-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME Date: Mon Jun 12 16:58:17 2017 ExecutablePath: /usr/bin/totem-video-thumbnailer InstallationDate: Installed on 2016-09-09 (275 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. ProcCmdline: /usr/bin/totem-video-thumbnailer -s 256 file:///media/username/0123-4567/PRIVATE/AVCHD/BDMV/STREAM/00139.MTS /tmp/.gnome_desktop_thumbnail.59DG1Y Signal: 5 SourcePackage: gstreamer1.0 StacktraceTop: g_malloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_slice_alloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0 gst_buffer_new_allocate () from /usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgstvideo-1.0.so.0 Title: totem-video-thumbnailer crashed with signal 5 in g_malloc() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: lxd sudo ** Affects: gstreamer1.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash need-amd64-retrace third-party-packages xenial ** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1697481 Title: totem-video-thumbnailer crashed with signal 5 in g_malloc() Status in gstreamer1.0 package in Ubuntu: New Bug description: Every time I open a folder with MTS video files the video thumbnailer crashes. It would be ok, if it just failed gracefully. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: libgstreamer1.0-0 1.8.3-1~ubuntu0.1 ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-54-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME Date: Mon Jun 12 16:58:17 2017 ExecutablePath: /usr/bin/totem-video-thumbnailer InstallationDate: Installed on 2016-09-09 (275 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. ProcCmdline: /usr/bin/totem-video-thumbnailer -s 256 file:///media/username/0123-4567/PRIVATE/AVCHD/BDMV/STREAM/00139.MTS /tmp/.gnome_desktop_thumbnail.59DG1Y Signal: 5 SourcePackage: gstreamer1.0 StacktraceTop: g_malloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_slice_alloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0 gst_buffer_new_allocate () from /usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgstvideo-1.0.so.0 Title: totem-video-thumbnailer crashed with signal 5 in g_malloc() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: lxd sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1697481/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1696019] Re: cursor not following the theme while hovering the desktop and the windows decorations
After making the screencast something fixed this behaviour, at least for this session.. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1696019 Title: cursor not following the theme while hovering the desktop and the windows decorations Status in gnome-shell package in Ubuntu: New Status in lightdm package in Ubuntu: New Status in nautilus package in Ubuntu: New Bug description: If I use lightdm to load GNOME Shell, I encounter a very weird bug: if I move the cursor to hover the desktop, the cursor theme becomes DMZ White, but if I move the cursor over the GNOME panel or over any open window, it returns back to the custom theme set by me. I can experience this bug only when using lightdm, if I use gdm3 I always have the same cursor. Note that I'm not on Wayland and that I have nautilus folders on my desktop. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lightdm 1.18.3-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.8.0-53.56~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-53-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Jun 6 02:14:12 2017 InstallationDate: Installed on 2016-09-09 (269 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1696019/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1696019] Re: cursor not following the theme while hovering the desktop and the windows decorations
I made a screencast of this behaviour. I rescaled it to keep it in a limited size ** Attachment added: "untitled.mpg" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1696019/+attachment/4889756/+files/untitled.mpg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1696019 Title: cursor not following the theme while hovering the desktop and the windows decorations Status in gnome-shell package in Ubuntu: New Status in lightdm package in Ubuntu: New Status in nautilus package in Ubuntu: New Bug description: If I use lightdm to load GNOME Shell, I encounter a very weird bug: if I move the cursor to hover the desktop, the cursor theme becomes DMZ White, but if I move the cursor over the GNOME panel or over any open window, it returns back to the custom theme set by me. I can experience this bug only when using lightdm, if I use gdm3 I always have the same cursor. Note that I'm not on Wayland and that I have nautilus folders on my desktop. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lightdm 1.18.3-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.8.0-53.56~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-53-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Jun 6 02:14:12 2017 InstallationDate: Installed on 2016-09-09 (269 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1696019/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1696019] Re: cursor not following the theme while hovering the desktop and the windows decorations
** Summary changed: - cursor not following the theme while hovering the desktop + cursor not following the theme while hovering the desktop and the windows decorations ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Also affects: nautilus (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1696019 Title: cursor not following the theme while hovering the desktop and the windows decorations Status in gnome-shell package in Ubuntu: New Status in lightdm package in Ubuntu: New Status in nautilus package in Ubuntu: New Bug description: If I use lightdm to load GNOME Shell, I encounter a very weird bug: if I move the cursor to hover the desktop, the cursor theme becomes DMZ White, but if I move the cursor over the GNOME panel or over any open window, it returns back to the custom theme set by me. I can experience this bug only when using lightdm, if I use gdm3 I always have the same cursor. Note that I'm not on Wayland and that I have nautilus folders on my desktop. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lightdm 1.18.3-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.8.0-53.56~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-53-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Jun 6 02:14:12 2017 InstallationDate: Installed on 2016-09-09 (269 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1696019/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
