[Bug 1978133] Re: System freeze followed by kernel panic or blank screen
I can reproduce this on Fedora 40, which likely indicates that it's an upstream bug. Workaround: disable c-states in BIOS. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1978133 Title: System freeze followed by kernel panic or blank screen To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1978133/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975890] Re: mp4 video gets stuck in a frame, like it's paused
No, I can reproduce it with many different video files. Nothing shows up on the cmdline. Firefox plays the videos just fine, by the way. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975890 Title: mp4 video gets stuck in a frame, like it's paused To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1975890/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975890] Re: mp4 video gets stuck in a frame, like it's paused
1. I ran "totem filename.mp4" and reproduced the problem, but nothing is logged to the console. 2. The package gstreamer1.0-vaapi is not installed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975890 Title: mp4 video gets stuck in a frame, like it's paused To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1975890/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975890] [NEW] mp4 video gets stuck in a frame, like it's paused
Public bug reported: The video stops playing at a certain random frame, like it's been paused. You can drag the range control and move forwards and backwards and the frame will change as expected, but toggling play/pause does nothing. I can only reproduce this on Ubuntu 22.04. On Debian 11 it works as expected. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: totem 42.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Uname: Linux 5.15.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu May 26 23:13:19 2022 InstallationDate: Installed on 2022-05-23 (3 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] Arquivo ou diretório inexistente: '/var/log/Xorg.0.log' ** Affects: totem (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975890 Title: mp4 video gets stuck in a frame, like it's paused To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1975890/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975516] Re: System freeze
It happened again, with the laptop idle same as before. This time the screen went dark (backlight off) and the fans were spinning fast. I could feel the laptop was a bit hot. I had Transmission, LibreOffice Writer and GNOME Files running at the time. ** Attachment added: "journalctl log of the second freeze" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975516/+attachment/5592731/+files/journalctl_2.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975516 Title: System freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975516/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975516] Re: System freeze
** Description changed: I had LibreOffice Writer open at the time, but it was idle. The system - was completely unresponsive and a power reset was the only way to shut - it down. The "REISUB" command didn't work. + became completely unresponsive and a power reset was the only way to + shut it down. The "REISUB" command didn't work. I had Ubuntu 21.10 and Debian 11 before, and this was not reproducible with them. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-33-generic 5.15.0-33.34 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Uname: Linux 5.15.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: dsilva 1511 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: dsilva 1511 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 23 13:48:05 2022 InstallationDate: Installed on 2022-05-23 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Lsusb: - Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub - Bus 001 Device 003: ID 0c45:671e Microdia Integrated_Webcam_HD - Bus 001 Device 002: ID 045e:07fd Microsoft Corp. Nano Transceiver 1.1 - Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 003: ID 0c45:671e Microdia Integrated_Webcam_HD + Bus 001 Device 002: ID 045e:07fd Microsoft Corp. Nano Transceiver 1.1 + Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 3583 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-33-generic root=UUID=15cac922-78d2-4c88-aa40-a49c2bfda033 ro quiet splash vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-5.15.0-33-generic N/A - linux-backports-modules-5.15.0-33-generic N/A - linux-firmware 20220329.git681281e4-0ubuntu3 + linux-restricted-modules-5.15.0-33-generic N/A + linux-backports-modules-5.15.0-33-generic N/A + linux-firmware 20220329.git681281e4-0ubuntu3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/21/2021 dmi.bios.release: 1.13 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.0 dmi.board.name: 0DC2CG dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.0:bd04/21/2021:br1.13:svnDellInc.:pnInspiron3583:pvr:rvnDellInc.:rn0DC2CG:rvrA00:cvnDellInc.:ct10:cvr:sku08CA: dmi.product.family: Inspiron dmi.product.name: Inspiron 3583 dmi.product.sku: 08CA dmi.sys.vendor: Dell Inc. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975516 Title: System freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975516/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975516] Re: System freeze
** Attachment added: "dmesg log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975516/+attachment/5592340/+files/dmesg.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975516 Title: System freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975516/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975516] [NEW] System freeze
Public bug reported: I had LibreOffice Writer open at the time, but it was idle. The system was completely unresponsive and a power reset was the only way to shut it down. The "REISUB" command didn't work. I had Ubuntu 21.10 and Debian 11 before, and this was not reproducible with them. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-33-generic 5.15.0-33.34 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Uname: Linux 5.15.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dsilva 1511 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 23 13:48:05 2022 InstallationDate: Installed on 2022-05-23 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:671e Microdia Integrated_Webcam_HD Bus 001 Device 002: ID 045e:07fd Microsoft Corp. Nano Transceiver 1.1 Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 3583 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-33-generic root=UUID=15cac922-78d2-4c88-aa40-a49c2bfda033 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-33-generic N/A linux-backports-modules-5.15.0-33-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/21/2021 dmi.bios.release: 1.13 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.0 dmi.board.name: 0DC2CG dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.0:bd04/21/2021:br1.13:svnDellInc.:pnInspiron3583:pvr:rvnDellInc.:rn0DC2CG:rvrA00:cvnDellInc.:ct10:cvr:sku08CA: dmi.product.family: Inspiron dmi.product.name: Inspiron 3583 dmi.product.sku: 08CA dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session ** Attachment added: "journalctl log" https://bugs.launchpad.net/bugs/1975516/+attachment/5592320/+files/journalctl.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975516 Title: System freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975516/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951006] Re: Cannot maximize window
File upload on Launchpad is broken, so here's an alternative link: https://1drv.ms/u/s!ApqEOOKoIKfogRiabNNcsT-7whBd?e=zWE6Zc -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951006 Title: Cannot maximize window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/handbrake/+bug/1951006/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951006] Re: Cannot maximize window
** Attachment added: "Screen recording" https://bugs.launchpad.net/ubuntu/+source/handbrake/+bug/1951006/+attachment/5541054/+files/Grava%C3%A7%C3%A3o%20de%20tela%20de%2015-11-2021%2015%3A33%3A04.webm -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951006 Title: Cannot maximize window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/handbrake/+bug/1951006/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951006] [NEW] Cannot maximize window
Public bug reported: The screen recording I'm attaching will expose 2 possibly related problems. 1. Maximize window button doesn't do anything. 2. The window height cannot be fully adjusted. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: handbrake 1.4.1+ds1-1 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Nov 15 15:29:45 2021 InstallationDate: Installed on 2021-11-15 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: handbrake UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: handbrake (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish wayland-session ** Attachment added: "Screen recording" https://bugs.launchpad.net/bugs/1951006/+attachment/5541050/+files/Grava%C3%A7%C3%A3o%20de%20tela%20de%2015-11-2021%2015%3A33%3A04.webm ** Description changed: - The screen recording I'm attaching will expose possibly related + The screen recording I'm attaching will expose 2 possibly related problems. 1. Maximize window button doesn't do anything. 2. The window height cannot be fully adjusted. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: handbrake 1.4.1+ds1-1 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Nov 15 15:29:45 2021 InstallationDate: Installed on 2021-11-15 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: handbrake UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951006 Title: Cannot maximize window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/handbrake/+bug/1951006/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951004] [NEW] pass -c won't work on Wayland without installing wl-clipboard
Public bug reported: To reproduce: 1. Install pass (apt install pass) 2. Add an entry to your password store, then try to copy it to the clipboard (pass -c entry_name) What happens: Command "wl-copy" not found. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: pass 1.7.4-1 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Nov 15 15:20:36 2021 InstallationDate: Installed on 2021-11-15 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) PackageArchitecture: all SourcePackage: password-store UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: password-store (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951004 Title: pass -c won't work on Wayland without installing wl-clipboard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/password-store/+bug/1951004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947527] Re: Unresponsive window when opening brush or color picker popup
I can reproduce this on Debian 11 with the GNOME desktop. Upstream issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947527 Title: Unresponsive window when opening brush or color picker popup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mypaint/+bug/1947527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947527] [NEW] Unresponsive window when opening brush or color picker popup
Public bug reported: ### Description of the problem The whole window becomes unresponsive when you open the brush or color picker popup window. The workaround to recover from this condition is pressing ESC once. The screen recording added below will also show you another problem. Most of the time I can't pick another brush. Sometimes it works, but I can't consistently reproduce it. This may or may not be related to the frozen window situation. ### Basic system details Operating system: Ubuntu 21.10 impish (amd64) Desktop environment: GNOME (wayland) MyPaint version: Package mypaint from universe repository $ mypaint --version INFO: mypaint: Installation layout: conventional POSIX-like structure with prefix '/usr' MyPaint version 2.0.1+gitexport.478280f ### Steps to reproduce Start mypaint. Click the large brush selector at the bottom right, or the color selector at the bottom left. The popup brush selector window appears, but the whole window is now unresponsive. ### Backtraces or error messages Console output: $ mypaint -t > trace-mypaint.txt INFO: mypaint: Installation layout: conventional POSIX-like structure with prefix '/usr' INFO: gui.main: No locale setting found, using system locale INFO: lib.i18n: POSIX: LANG='pt_BR.UTF-8' INFO: lib.i18n: POSIX: LANGUAGE='pt_BR:pt:en' INFO: lib.i18n: Value of LANGUAGE after cleanup: 'pt_BR:pt:en:C' INFO: gui.compatibility: Setting mode to 2.x (standard) INFO: gui.compatibility: Setting default layer type to Pigment INFO: gui.device: New device 'Wayland Pointer' (GDK_SOURCE_MOUSE, axes:2, class=GdkWaylandDevice, vendor=None, product=None) INFO: gui.document: Initialized background from '/usr/share/mypaint/backgrounds/mrmamurk/mamurk_e_1.png' WARNING: gui.keyboard: Ignoring keybinding for '/BrushModifierActions/BlendModeMenu' INFO: gui.brushmanager: Switching default pigment setting to On INFO: lib.document: load_ora: '/home/dsilva/.local/share/mypaint/scratchpads/autosave.ora' INFO: lib.document: 0.137s load_ora total INFO: gui.filehandling: Loaded scratchpad from '/home/dsilva/.local/share/mypaint/scratchpads/autosave.ora' INFO: gui.compatibility: Setting default layer type to Pigment (mypaint:33094): Gdk-WARNING **: 13:49:40.388: Window 0x3cbd030 is already mapped at the time of grabbing. gdk_seat_grab() should be used to simultanously grab input and show this popup. You may find oddities ahead. WARNING: gui.windowing: grab: outside-popup grab already active: regrabbing (mypaint:33094): Gdk-WARNING **: 13:49:45.766: Window 0x3cbd030 is already mapped at the time of grabbing. gdk_seat_grab() should be used to simultanously grab input and show this popup. You may find oddities ahead. (mypaint:33094): Gdk-WARNING **: 13:49:49.402: Window 0x3cbd030 is already mapped at the time of grabbing. gdk_seat_grab() should be used to simultanously grab input and show this popup. You may find oddities ahead. (mypaint:33094): Gdk-WARNING **: 13:49:51.673: Window 0x3cbd030 is already mapped at the time of grabbing. gdk_seat_grab() should be used to simultanously grab input and show this popup. You may find oddities ahead. WARNING: gui.windowing: grab: outside-popup grab already active: regrabbing (mypaint:33094): Gdk-WARNING **: 13:49:52.668: Window 0x3cbd030 is already mapped at the time of grabbing. gdk_seat_grab() should be used to simultanously grab input and show this popup. You may find oddities ahead. WARNING: gui.windowing: grab: outside-popup grab already active: regrabbing (mypaint:33094): Gdk-WARNING **: 13:49:55.338: Window 0x3cbd030 is already mapped at the time of grabbing. gdk_seat_grab() should be used to simultanously grab input and show this popup. You may find oddities ahead. WARNING: gui.windowing: grab: outside-popup grab already active: regrabbing (mypaint:33094): Gdk-WARNING **: 13:49:59.113: Window 0x3cbd030 is already mapped at the time of grabbing. gdk_seat_grab() should be used to simultanously grab input and show this popup. You may find oddities ahead. WARNING: gui.windowing: grab: outside-popup grab already active: regrabbing (mypaint:33094): Gdk-WARNING **: 13:50:06.928: Window 0x3cbd030 is already mapped at the time of grabbing. gdk_seat_grab() should be used to simultanously grab input and show this popup. You may find oddities ahead. (mypaint:33094): Gdk-WARNING **: 13:50:14.014: Window 0x3faf5c0 is already mapped at the time of grabbing. gdk_seat_grab() should be used to simultanously grab input and show this popup. You may find oddities ahead. WARNING: gui.windowing: grab: outside-popup grab already active: regrabbing (mypaint:33094): Gdk-WARNING **: 13:50:25.138: Window 0x3faf5c0 is already mapped at the time of grabbing. gdk_seat_grab() should be used to simultanously grab input and show this popup. You may find oddities ahead. WARNING: gui.windowing: grab: outside-popup grab already active: regrabbing (mypaint:33094): Gdk-WARNING **: 13:50:49.872: Window 0x3faf5c0 is al
[Bug 1947294] Re: MyPaint crashes/freezes after interacting with its interface
This is not reproducible on Ubuntu impish (21.10). ** Description changed: - This is reproducible on both hirsute and impish. Ubuntu Wayland session. + This is reproducible on both hirsute ~and impish~. Ubuntu Wayland + session. 1. Open MyPaint 2. Try to select a different brush or color The application becomes unresponsive. The menubar and the buttons below it do not seem to cause any problem. Only the fancy widgets at the bottom of the window lead to a crash. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: mypaint 2.0.1-2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Oct 14 22:00:52 2021 InstallationDate: Installed on 2021-10-10 (4 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: mypaint UpgradeStatus: Upgraded to impish on 2021-10-15 (0 days ago) ** Description changed: - This is reproducible on both hirsute ~and impish~. Ubuntu Wayland - session. + This is reproducible on hirsute. Ubuntu Wayland session. 1. Open MyPaint 2. Try to select a different brush or color The application becomes unresponsive. The menubar and the buttons below it do not seem to cause any problem. Only the fancy widgets at the bottom of the window lead to a crash. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: mypaint 2.0.1-2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Oct 14 22:00:52 2021 InstallationDate: Installed on 2021-10-10 (4 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: mypaint UpgradeStatus: Upgraded to impish on 2021-10-15 (0 days ago) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947294 Title: MyPaint crashes/freezes after interacting with its interface To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mypaint/+bug/1947294/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947294] Re: MyPaint crashes/freezes after interacting with its interface
I'm attaching the trace and the command line output: INFO: mypaint: Installation layout: conventional POSIX-like structure with prefix '/usr' INFO: gui.main: No locale setting found, using system locale INFO: lib.i18n: POSIX: LANG='pt_BR.UTF-8' INFO: lib.i18n: POSIX: LANGUAGE='pt_BR:pt:en' INFO: lib.i18n: Value of LANGUAGE after cleanup: 'pt_BR:pt:en:C' INFO: gui.compatibility: Setting mode to 2.x (standard) INFO: gui.compatibility: Setting default layer type to Pigment INFO: gui.device: New device 'Wayland Pointer' (GDK_SOURCE_MOUSE, axes:2, class=GdkWaylandDevice, vendor=None, product=None) INFO: gui.document: Initialized background from '/usr/share/mypaint/backgrounds/mrmamurk/mamurk_e_1.png' WARNING: gui.keyboard: Ignoring keybinding for '/BrushModifierActions/BlendModeMenu' INFO: gui.brushmanager: Switching default pigment setting to On INFO: lib.document: load_ora: '/home/dsilva/.local/share/mypaint/scratchpads/autosave.ora' INFO: lib.document: 0.145s load_ora total INFO: gui.filehandling: Loaded scratchpad from '/home/dsilva/.local/share/mypaint/scratchpads/autosave.ora' INFO: gui.compatibility: Setting default layer type to Pigment (mypaint:16241): Gdk-WARNING **: 22:09:13.575: Window 0x31a01a0 is already mapped at the time of grabbing. gdk_seat_grab() should be used to simultanously grab input and show this popup. You may find oddities ahead. ** Attachment added: "MyPaint trace log" https://bugs.launchpad.net/ubuntu/+source/mypaint/+bug/1947294/+attachment/5533007/+files/mypaint-trace.log ** Description changed: This is reproducible on both hirsute and impish. Ubuntu Wayland session. 1. Open MyPaint - 2. Try to select a different brush, for example + 2. Try to select a different brush or color The application becomes unresponsive. + + The menubar and the buttons below it do not seem to cause any problem. + Only the fancy widgets at the bottom of the window lead to a crash. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: mypaint 2.0.1-2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Oct 14 22:00:52 2021 InstallationDate: Installed on 2021-10-10 (4 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: mypaint UpgradeStatus: Upgraded to impish on 2021-10-15 (0 days ago) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947294 Title: MyPaint crashes/freezes after interacting with its interface To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mypaint/+bug/1947294/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947294] [NEW] MyPaint crashes/freezes after interacting with its interface
Public bug reported: This is reproducible on both hirsute and impish. Ubuntu Wayland session. 1. Open MyPaint 2. Try to select a different brush or color The application becomes unresponsive. The menubar and the buttons below it do not seem to cause any problem. Only the fancy widgets at the bottom of the window lead to a crash. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: mypaint 2.0.1-2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Oct 14 22:00:52 2021 InstallationDate: Installed on 2021-10-10 (4 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: mypaint UpgradeStatus: Upgraded to impish on 2021-10-15 (0 days ago) ** Affects: mypaint (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947294 Title: MyPaint crashes/freezes after interacting with its interface To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mypaint/+bug/1947294/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946411] Re: Glitchy/freezing desktop caused by opening app launcher group
*** This bug is a duplicate of bug 1872268 *** https://bugs.launchpad.net/bugs/1872268 Thanks, it's a duplicate then. I'm attaching the video again, let's see if it works now. ** Attachment removed: "Reproducing the bug in video" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1946411/+attachment/5531404/+files/Grava%C3%A7%C3%A3o%20de%20tela%20de%2007-10-2021%2023%3A08%3A21.webm ** Attachment added: "Reproducing the bug in video" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1946411/+attachment/5531405/+files/gnome-shell-bug.webm -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946411 Title: Glitchy/freezing desktop caused by opening app launcher group To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1946411/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946411] Re: Glitchy/freezing desktop caused by opening app launcher group
** Attachment added: "Reproducing the bug in video" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1946411/+attachment/5531404/+files/Grava%C3%A7%C3%A3o%20de%20tela%20de%2007-10-2021%2023%3A08%3A21.webm -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946411 Title: Glitchy/freezing desktop caused by opening app launcher group To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1946411/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946411] [NEW] Glitchy/freezing desktop caused by opening app launcher group
Public bug reported: # Steps to reproduce: 1. Press "Super + A" to see all apps. 2. Find an app launcher group (many launchers grouped in one item) and open it 3. Close the group # What happens: The pagination indicators become duplicated, followed by glitchy animations. This can be temporarily fixed by pressing ALT + F2 and running "r" to restart the desktop. If you don't do that soon, the desktop will become frozen, unresponsive. # Workaround (for the frozen desktop): Switch to another TTY and restart the 'gdm' service. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.9-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Oct 7 22:53:34 2021 DisplayManager: gdm3 InstallationDate: Installed on 2021-10-07 (0 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946411 Title: Glitchy/freezing desktop caused by opening app launcher group To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1946411/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940699] [NEW] Orca makes browsers crash
Public bug reported: Enabling the screen reader in GNOME and using it with any browser leads to occasional glitches and crashes. Firefox, for example, crashed and asked me to file a crash report to Mozilla. GNOME Web just restarted itself out of nowhere, same as Chromium. The arrow up/down navigation sometimes works correctly in Firefox, but on other browsers it looks totally broken (nothing happens when pressed). I believe this is not reproducible on focal, only on hirsute. I'm using the default Wayland session. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: orca 3.38.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Aug 20 14:06:24 2021 InstallationDate: Installed on 2021-08-15 (4 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all SourcePackage: orca UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: orca (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940699 Title: Orca makes browsers crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/orca/+bug/1940699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917674] Re: [amdgpu] kernel crash when resuming from automatic suspension to RAM (started in 5.7.0, not in 5.6.19)
I'm now using Ubuntu 21.04 hirsute, and this bug can no longer be reproduced :) Kernel 5.11.0-25-generic. I've done 3 tests. No crashes so far. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917674 Title: [amdgpu] kernel crash when resuming from automatic suspension to RAM (started in 5.7.0, not in 5.6.19) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930167] Re: New Firefox 88 freezes on Wayland then system crash
So, I've questions about this bug if it comes from firefox, or mutter, or wayland because every time I try use Firefox 88 the Wayland session freezes and nothing else works besides Magic Key to restart my machine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930167 Title: New Firefox 88 freezes on Wayland then system crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1930167/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930167] Re: New Firefox 88 freezes on Wayland then system crash
Hi there! This report page doesn't have any from reported version but it does have the report from the previous version, version 87: https://crash-stats.mozilla.org/report/index/09389e82-1bfb-43fe- bd10-2b8940210408 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930167 Title: New Firefox 88 freezes on Wayland then system crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1930167/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930167] [NEW] New Firefox 88 freezes on Wayland then system crash
Public bug reported: After updating firefox deb to version 88, every time I play YouTube videos, some times in several tabs, then Wayland crashes and the system freezes. For try workaround this crash, I've to use the magic key SysRq (Alt + SysReq) with "REISUB" characters to safely reboot my Ubuntu though. Every time I open Firefox 88 deb via console, the message below appears even though these modules are installed: Gtk-Message: 14:01:56.615: Failed to load module "appmenu-gtk-module" Gtk-Message: 14:01:56.662: Failed to load module "canberra-gtk-module" Gtk-Message: 14:01:56.664: Failed to load module "canberra-gtk-module" /usr/share/libdrm/amdgpu.ids: No such file or directory I'm currently using Firefox 78 ESR snap because the main installation is unusable, unfortunately ... Thank you! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 88.0.1+build1-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: douglas 15771 F pulseaudio /dev/snd/controlC2: douglas 15771 F pulseaudio /dev/snd/controlC0: douglas 15771 F pulseaudio BuildID: 20210504152106 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Sun May 30 13:54:03 2021 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:352 DefaultProfilePrefSources: prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2020-11-12 (198 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IpRoute: default via 192.168.1.1 dev eno1 proto dhcp metric 100 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.1.0/24 dev eno1 proto kernel scope link src 192.168.1.2 metric 100 MostRecentCrashID: bp-09389e82-1bfb-43fe-bd10-2b8940210408 Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:352 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=84.0.2/20210105180113 (Out of date) Profile0 - LastVersion=88.0.1/20210504152106 RunningIncompatibleAddons: False SourcePackage: firefox SubmittedCrashIDs: bp-09389e82-1bfb-43fe-bd10-2b8940210408 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F50d dmi.board.asset.tag: Default string dmi.board.name: AB350M-Gaming 3-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF50d:bd07/02/2020:br5.14:svnGigabyteTechnologyCo.,Ltd.:pnAB350M-Gaming3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350M-Gaming3-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: B350 MB dmi.product.name: AB350M-Gaming 3 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930167 Title: New Firefox 88 freezes on Wayland then system crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1930167/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922241] Re: [Wayland] Dash to dock don't show all applications
Probably related to bug 1872796 too -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922241 Title: [Wayland] Dash to dock don't show all applications To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1922241/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922241] [NEW] [Wayland] Dash to dock don't show all applications
Public bug reported: This extension has been updated these days and the "All" button (next to "Frequent" button) has crash and no longer shows all applications. Disabling Ubuntu-Dock via Extensions Panel this function works perfectly again. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-ubuntu-dock 68ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 1 09:56:04 2021 InstallationDate: Installed on 2020-11-12 (139 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922241 Title: [Wayland] Dash to dock don't show all applications To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1922241/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917674] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1917674/+attachment/5479070/+files/acpidump.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Changed in: linux-hwe-5.8 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917674 Title: [amdgpu] kernel crash when resuming from automatic suspension to RAM (started in 5.7.0, not in 5.6.19) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917674] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1917674/+attachment/5479069/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917674 Title: [amdgpu] kernel crash when resuming from automatic suspension to RAM (started in 5.7.0, not in 5.6.19) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917674] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1917674/+attachment/5479068/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917674 Title: [amdgpu] kernel crash when resuming from automatic suspension to RAM (started in 5.7.0, not in 5.6.19) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917674] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1917674/+attachment/5479066/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917674 Title: [amdgpu] kernel crash when resuming from automatic suspension to RAM (started in 5.7.0, not in 5.6.19) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917674] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1917674/+attachment/5479065/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917674 Title: [amdgpu] kernel crash when resuming from automatic suspension to RAM (started in 5.7.0, not in 5.6.19) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917674] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1917674/+attachment/5479064/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917674 Title: [amdgpu] kernel crash when resuming from automatic suspension to RAM (started in 5.7.0, not in 5.6.19) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917674] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1917674/+attachment/5479063/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917674 Title: [amdgpu] kernel crash when resuming from automatic suspension to RAM (started in 5.7.0, not in 5.6.19) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917674] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1917674/+attachment/5479062/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917674 Title: [amdgpu] kernel crash when resuming from automatic suspension to RAM (started in 5.7.0, not in 5.6.19) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917674] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1917674/+attachment/5479061/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917674 Title: [amdgpu] kernel crash when resuming from automatic suspension to RAM (started in 5.7.0, not in 5.6.19) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917674] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1917674/+attachment/5479060/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917674 Title: [amdgpu] kernel crash when resuming from automatic suspension to RAM (started in 5.7.0, not in 5.6.19) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917674] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1917674/+attachment/5479059/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917674 Title: [amdgpu] kernel crash when resuming from automatic suspension to RAM (started in 5.7.0, not in 5.6.19) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917674] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1917674/+attachment/5479058/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917674 Title: [amdgpu] kernel crash when resuming from automatic suspension to RAM (started in 5.7.0, not in 5.6.19) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917674] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1917674/+attachment/5479057/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917674 Title: [amdgpu] kernel crash when resuming from automatic suspension to RAM (started in 5.7.0, not in 5.6.19) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917674] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1917674/+attachment/5479056/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917674 Title: [amdgpu] kernel crash when resuming from automatic suspension to RAM (started in 5.7.0, not in 5.6.19) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917674] Re: [amdgpu] kernel crash when resuming from automatic suspension to RAM (started in 5.7.0, not in 5.6.19)
apport information ** Tags added: apport-collected ** Description changed: Automatic suspension causes the system to freeze on resume. This doesn't happen if I suspend it manually by opening the system menu and pressing the suspend button. Suspension works flawlessly when it is triggered manually. When the system resumes from automatic suspension, the lock screen is visible but does not respond. It's frozen. A notification says something like "system will suspend shortly due to inactivity". It never goes away. The keyboard responds during this (at least for a while). The CAPS LOCK LED turns on and off as I press it (with no delay). Sometimes I can even switch to another TTY and kill the X server, which is why I'm reporting it against gnome-shell. When switching TTY is impossible, I use the "REISUB" combination to shut down. Either way, I always lose the running session. This is reproducible about 60% of the time. Eventually I ended up disabling it and relying only on manual suspension. # Additional information: 1) Ubuntu 20.04.2 LTS / Release: 20.04 2) gnome-shell 3.36.4-1ubuntu1~20.04.2 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Mar 3 16:56:01 2021 DisplayManager: gdm3 InstallationDate: Installed on 2021-01-31 (31 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.16 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: dsilva 1884 F pulseaudio + /dev/snd/controlC1: dsilva 1884 F pulseaudio + CasperMD5CheckResult: skip + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2021-01-31 (49 days ago) + InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) + Lsusb: + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub + Bus 001 Device 004: ID 0951:16de Kingston Technology HyperX Pulsefire Core + Bus 001 Device 003: ID 0951:16d2 Kingston Technology HyperX Alloy FPS Pro Mechanical Gaming Keyboard + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + MachineType: Gigabyte Technology Co., Ltd. B460MDS3H + Package: linux-hwe-5.8 + ProcEnviron: + LANGUAGE=pt_BR:pt:en + TERM=xterm-256color + PATH=(custom, no user) + LANG=pt_BR.UTF-8 + SHELL=/bin/bash + ProcFB: 0 amdgpudrmfb + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-45-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18 + PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. + RelatedPackageVersions: + linux-restricted-modules-5.8.0-45-generic N/A + linux-backports-modules-5.8.0-45-generic N/A + linux-firmware1.187.10 + RfKill: + + Tags: focal + Uname: Linux 5.8.0-45-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: N/A + _MarkForUpload: True + dmi.bios.date: 05/27/2020 + dmi.bios.release: 5.17 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: F3 + dmi.board.asset.tag: Default string + dmi.board.name: B460M DS3H + dmi.board.vendor: Gigabyte Technology Co., Ltd. + dmi.board.version: x.x + dmi.chassis.asset.tag: Default string + dmi.chassis.type: 3 + dmi.chassis.vendor: Default string + dmi.chassis.version: Default string + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF3:bd05/27/2020:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnB460MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB460MDS3H:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: + dmi.product.family: B460 MB + dmi.product.name: B460MDS3H + dmi.product.sku: Default string + dmi.product.version: Default string + dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1917674/+attachment/5479055/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917674 Title: [amdgpu] kernel crash when resuming from automatic suspension to RAM (started in 5.7.0, not in 5.6.19) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-
[Bug 1917674] Re: [amdgpu] kernel crash when resuming from automatic suspension to RAM
Kernel 5.6.19: OK If I'm not mistaken, this was the last version before 5.7, so the bug must have been introduced in 5.7.0. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917674 Title: [amdgpu] kernel crash when resuming from automatic suspension to RAM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917674] Re: [amdgpu] kernel crash when resuming from automatic suspension to RAM
I've finished the tests, here are the results: 5.0.0: OK 5.4.0: OK 5.6.0: OK 5.7.0: BUG 5.8.0: BUG -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917674 Title: [amdgpu] kernel crash when resuming from automatic suspension to RAM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917674] Re: [amdgpu] kernel crash when resuming from automatic suspension to RAM
Nevermind, I was running 5.8, not 5.0.0. I forgot to select 5.0.0 in the boot menu. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917674 Title: [amdgpu] kernel crash when resuming from automatic suspension to RAM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917674] Re: [amdgpu] kernel crash when resuming from automatic suspension to RAM
I was able to reproduce this with kernel 5.0.0 too. Isn't it possible that this is not caused by the kernel? I don't think I had this issue back then - it's something more recent. ** Attachment added: "Logs from a previous session that crashed with kernel 5.0.0" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917674/+attachment/5476815/+files/prevboot.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917674 Title: [amdgpu] kernel crash when resuming from automatic suspension to RAM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917674] Re: Freeze when resuming from automatic suspension to RAM
I'm attaching the requested logs. Near the end of this file you'll see the last action I performed, which was the CTRL+ALT+PRINT+REISUB combination to reboot. You'll also see that there is a long crash log related to AMDGPU. Oh, and this time when it crashed I attempted to switch TTY, and then the screen changed to a display of trillions of tiny colorful artifacts, like a TV with bad reception. ** Attachment added: "Logs from a previous session that crashed" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1917674/+attachment/5475553/+files/prevboot.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917674 Title: Freeze when resuming from automatic suspension to RAM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1917674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917674] Re: Freeze when resuming from automatic suspension to RAM
I can't see any files in /var/crash/, even after applying the workaround and reproducing the freeze again. This time the freeze was more severe. There was no response from the keyboard and a hard reset was the only way to recover. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917674 Title: Freeze when resuming from automatic suspension to RAM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1917674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917674] [NEW] Freeze when resuming from automatic suspension to RAM
Public bug reported: Automatic suspension causes the system to freeze on resume. This doesn't happen if I suspend it manually by opening the system menu and pressing the suspend button. Suspension works flawlessly when it is triggered manually. When the system resumes from automatic suspension, the lock screen is visible but does not respond. It's frozen. A notification says something like "system will suspend shortly due to inactivity". It never goes away. The keyboard responds during this (at least for a while). The CAPS LOCK LED turns on and off as I press it (with no delay). Sometimes I can even switch to another TTY and kill the X server, which is why I'm reporting it against gnome-shell. When switching TTY is impossible, I use the "REISUB" combination to shut down. Either way, I always lose the running session. This is reproducible about 60% of the time. Eventually I ended up disabling it and relying only on manual suspension. # Additional information: 1) Ubuntu 20.04.2 LTS / Release: 20.04 2) gnome-shell 3.36.4-1ubuntu1~20.04.2 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Mar 3 16:56:01 2021 DisplayManager: gdm3 InstallationDate: Installed on 2021-01-31 (31 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Description changed: Automatic suspension causes the system to freeze on resume. This doesn't happen if I suspend it manually by opening the system menu and pressing the suspend button. Suspension works flawlessly when it is triggered manually. When the system resumes from automatic suspension, the lock screen is - visible but does not respond. It's frozen. A notification says "system - will suspend shortly due to inactivity". It never goes away. + visible but does not respond. It's frozen. A notification says something + like "system will suspend shortly due to inactivity". It never goes + away. The keyboard responds during this (at least for a while). The CAPS LOCK LED turns on and off as I press it (with no delay). Sometimes I can even switch to another TTY and kill the X server, which is why I'm reporting it against gnome-shell. When switching TTY is impossible, I use the "REISUB" combination to shut down. Either way, I always lose the running session. This is reproducible about 60% of the time. Eventually I ended up disabling it and relying only on manual suspension. # Additional information: 1) Ubuntu 20.04.2 LTS / Release: 20.04 2) gnome-shell 3.36.4-1ubuntu1~20.04.2 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Mar 3 16:56:01 2021 DisplayManager: gdm3 InstallationDate: Installed on 2021-01-31 (31 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917674 Title: Freeze when resuming from automatic suspension to RAM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1917674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876532] Re: Badly positioned icons in the app grid
Correction: It's not about where the cursor is placed when the animation ends, it's about whether the cursor is moving or not. Keep the cursor still, as I said previously, and the bug doesn't happen. Keep the cursor moving while the sliding animation is running, and the problem is nearly always reproducible. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876532 Title: Badly positioned icons in the app grid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1876532/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876532] Re: Badly positioned icons in the app grid
An observation about how to reproduce this bug: As soon as you click the "Show Applications" button on the dock, move your mouse to the target position of any of the icons before the sliding animation is over. This will usually trigger the glitch. Keeping the cursor still after you click that button is one way to avoid reproducing it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876532 Title: Badly positioned icons in the app grid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1876532/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876532] Re: Badly positioned icons in the app grid
Update: this is also reproducible on Wayland. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876532 Title: Badly positioned icons in the app grid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1876532/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876532] Re: Badly positioned icons in the app grid
Here's the gif showing a strange animation happening right after the app grid is opened, which causes a displacement of the icons. ** Attachment added: "Animation showing how to reproduce the problem" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1876532/+attachment/5365469/+files/Peek%2002-05-2020%2020-23.gif -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876532 Title: Badly positioned icons in the app grid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1876532/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876532] Re: Badly positioned icons in the app grid
** Attachment added: "Screenshot of the first part of the grid" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1876532/+attachment/5365468/+files/Captura%20de%20tela%20de%202020-05-02%2019-47-31.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876532 Title: Badly positioned icons in the app grid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1876532/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876532] [NEW] Badly positioned icons in the app grid
Public bug reported: This bug is best explained with images. I've attached two screenshots showing what the app grid looks like right after it's opened. A gif has also been recorded to show a glitch in the animation as the icons slide in. This is not reproducible in Fedora 32 with GNOME 3.36 on the same machine. I will be testing the Wayland session shortly and report back. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu1 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: ubuntu:GNOME Date: Sat May 2 19:51:09 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-05-02 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "Screenshot of the second part of the grid" https://bugs.launchpad.net/bugs/1876532/+attachment/5365462/+files/Captura%20de%20tela%20de%202020-05-02%2020-06-23.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876532 Title: Badly positioned icons in the app grid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1876532/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875249] Re: [Inspiron 11-3162, Realtek ALC3234, Black Headphone Out, Front] No sound output from earphones
I forgot to tell you that I never see any dialog when I plug the earphone. It's a feature of some desktop environments, right? I have never seen it in Xfce. The capture source changes to "headphone" every time I plug the earphone, and when that happens, there is no sound output. Changing it to any other source makes the sound work. I don't remember how it worked in previous versions of Ubuntu. It just worked. I never had to worry about switching the capture source in order to have sound. If you think that's important to know, I can try a live ISO of 18.04 and report back what I find. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875249 Title: [Inspiron 11-3162, Realtek ALC3234, Black Headphone Out, Front] No sound output from earphones To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1875249/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875249] Re: [Inspiron 11-3162, Realtek ALC3234, Black Headphone Out, Front] No sound output from earphones
Oh, I can finally hear sound through the earphones by changing the capture source. Too bad the change doesn't persist after I remove and reinsert the connector. Every time that happens, I must change it to Headset Mic, otherwise there will be no sound output. It also works when I do it through the Pulseaudio GUI mixer that comes with Xubuntu. Now I just wish the default selection could be one that works out of the box, as it was in previous Ubuntu versions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875249 Title: [Inspiron 11-3162, Realtek ALC3234, Black Headphone Out, Front] No sound output from earphones To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1875249/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875249] Re: [Inspiron 11-3162, Realtek ALC3234, Black Headphone Out, Front] No sound output from earphones
** Attachment added: "screenshot alsamixer capture" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1875249/+attachment/5361512/+files/Captura%20de%20tela_2020-04-27_06-51-37.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875249 Title: [Inspiron 11-3162, Realtek ALC3234, Black Headphone Out, Front] No sound output from earphones To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1875249/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875249] Re: [Inspiron 11-3162, Realtek ALC3234, Black Headphone Out, Front] No sound output from earphones
I have attached a screenshot of that screen, because I couldn't find any Capture Source or Input Source there. Maybe it has a different name or is missing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875249 Title: [Inspiron 11-3162, Realtek ALC3234, Black Headphone Out, Front] No sound output from earphones To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1875249/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875249] Re: [Inspiron 11-3162, Realtek ALC3234, Black Headphone Out, Front] No sound output from earphones
Running amixer sset 'Capture Source' 'Internal Mic' returns error: amixer: Unable to find simple control 'Capture Source',0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875249 Title: [Inspiron 11-3162, Realtek ALC3234, Black Headphone Out, Front] No sound output from earphones To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1875249/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875249] [NEW] [Inspiron 11-3162, Realtek ALC3234, Black Headphone Out, Front] No sound output from earphones
Public bug reported: Starting from Ubuntu 20.04 (tested Xubuntu and Ubuntu MATE), there is no sound output when you plug an earphone/headset. The built-in speakers, on the other hand, are working properly. This is a laptop, Dell Inspiron 11 3162. I checked volume levels with alsamixer, I played with the device selection in the Pulseaudio mixer application, but nothing worked. I also tested Firefox (playing a YouTube video) and system sounds. None of them worked. The audio test made by apport-bug played no sound through the earphone. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dsilva 3990 F pulseaudio dsilva 4791 F alsamixer CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sun Apr 26 18:12:06 2020 InstallationDate: Installed on 2020-04-24 (2 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Áudio interno - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dsilva 3990 F pulseaudio dsilva 4791 F alsamixer Symptom_Jack: Black Headphone Out, Front Symptom_Type: No sound at all Title: [Inspiron 11-3162, Realtek ALC3234, Black Headphone Out, Front] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.0 dmi.board.name: 0NM68T dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr2.4.0:bd01/31/2018:svnDellInc.:pnInspiron11-3162:pvr2.4.0:rvnDellInc.:rn0NM68T:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.family: To be filled by O.E.M. dmi.product.name: Inspiron 11-3162 dmi.product.sku: 0725 dmi.product.version: 2.4.0 dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Summary changed: - No sound output from earphones + [Inspiron 11-3162, Realtek ALC3234, Black Headphone Out, Front] No sound output from earphones -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875249 Title: [Inspiron 11-3162, Realtek ALC3234, Black Headphone Out, Front] No sound output from earphones To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1875249/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1795135] Re: XFCE window buttons are not clickable at the top of the screen
This bug was fixed in Xubuntu 19.04, if I remember correctly. But on later releases it became reproducible again. I'm currently running Xubuntu 20.04, and most of the widgets on the top panel are affected, with the exception of Whisker menu icon (sometimes), the task switcher and the Notes widget icon. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1795135 Title: XFCE window buttons are not clickable at the top of the screen To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1795135/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1757375] Re: Desktop unable to Suspend when Inactive
I think I can't reproduce this anymore on Xubuntu 20.04. I left the laptop idle and after 30 minutes it was suspended as expected, without making any fixes (clean install). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1757375 Title: Desktop unable to Suspend when Inactive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-desktop-privileges/+bug/1757375/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860793] Re: [amdgpu] Severe freezes that begin with minor stutters
You mean I should try an older version? Then I think I should try v5.0.x first. As you can see, it takes time to reproduce it again. I don't know how to intentionally reproduce it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860793 Title: [amdgpu] Severe freezes that begin with minor stutters To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860793/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860793] Re: [amdgpu] Severe freezes that begin with minor stutters
The logs I attached previously only refer to the session AFTER the system restarted. So I've collected the logs from the previous boot this time, which will contain the relevant information. I'm attaching the output of: `journalctl -b-1` ** Attachment added: "output of journalctl -b-1" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1860793/+attachment/5327108/+files/journalctl.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860793 Title: [amdgpu] Severe freezes that begin with minor stutters To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1860793/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860793] Re: [amdgpu] Severe freezes that begin with minor stutters
Apparently, the logs I collected are from after the reboot, so they're probably not relevant. How do I collect logs from before the reboot? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860793 Title: [amdgpu] Severe freezes that begin with minor stutters To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1860793/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860793] Re: [amdgpu] Severe freezes that begin with minor stutters
I was able to reproduce it again. The system quickly became unresponsive, so I had to reboot with the REISUB combination. After the system started again I collected the logs. I wasn't using Nautilus of the image viewer this time. ** Attachment added: "journalctl -b0 after the freeze" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1860793/+attachment/5327105/+files/journal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860793 Title: [amdgpu] Severe freezes that begin with minor stutters To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1860793/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862214] [NEW] Overview windows overflow vertically
Public bug reported: When you have 3 or more windows open, the overview will overflow vertically. A piece of the bottom row is cut off from the screen. See the screenshot, please. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 6 13:49:13 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-12-27 (41 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1~19.10.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ** Attachment added: "Screenshot of the glitch" https://bugs.launchpad.net/bugs/1862214/+attachment/5325990/+files/Captura%20de%20tela%20de%202020-02-06%2013-48-12.png ** Description changed: - When you have 4 or more windows open, the overview will overflow + When you have 3 or more windows open, the overview will overflow vertically. A piece of the bottom row is cut off from the screen. See the screenshot, please. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 6 13:49:13 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-12-27 (41 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1~19.10.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1862214 Title: Overview windows overflow vertically To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1862214/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860793] Re: Severe freezes that begin with minor stutters
I have been trying to reproduce it in the last days, but I couldn't. I managed to get nearly 100% use of swap space again, while simultaneously using Nautilus and Eye of GNOME (which is what I was doing at the exact moment the freezes began), but it didn't happen again. Nothing changed about my workload. I have the same applications open, consuming the same usual amount of resources. This seems to be a tricky one to reproduce, but I'll keep trying. By the way, I'm attaching the lspci command output. ** Attachment added: "lspci -k output" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1860793/+attachment/5325733/+files/lspcik.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860793 Title: Severe freezes that begin with minor stutters To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1860793/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849135] Re: Clicking Activities in the corner doesn't work
Here's the new issue: https://gitlab.gnome.org/GNOME/gnome-shell/issues/2164 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #2164 https://gitlab.gnome.org/GNOME/gnome-shell/issues/2164 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849135 Title: Clicking Activities in the corner doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1849135/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849135] Re: Clicking Activities in the corner doesn't work
I'll create the new issue there. I have only one monitor. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849135 Title: Clicking Activities in the corner doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1849135/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856032] Re: DVD icon did not disappear from dash.
I can reproduce this problem with a USB stick as well. I suggest changing the title to "Removable media icon stays on the dock after eject". To reproduce, I've inserted my USB stick used to install Ubuntu, automounting it; Two items appeared, one that says "Ubuntu 19.10..." and another saying "casper...", then I ejected it with the command `sudo eject /dev/sdx`. The icon saying "Ubuntu 19.10..." is still there. The other is gone. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856032 Title: DVD icon did not disappear from dash. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1856032/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860793] [NEW] Severe freezes that begin with minor stutters
Public bug reported: It starts with very subtle stuttering that you notice when moving windows around, then keeps getting worse and worse until it starts freezing the UI for many seconds. I could only reproduce it twice in a couple of days. The applications open at the time are usually Atom, Firefox, Hexchat, GNOME Files and occasionally Eye of GNOME. I checked resource consumption at the time of the stutters. Memory consumption was about 50% of 8GB, while the swap partition was nearly full (after a long gaming session). Storage device is a SATA SSD. During the stutters and freezes, CPU usage is normal. Through the process list of System Monitor I cannot see any application overusing resources. Temperatures are also normal. One potentially problematic hardware device is the GPU: AMD RX 560 4GB (open source AMDGPU). Its temperature and fan speed were also normal at the time. I know my system is capable of handling this workload. Also, this is only reproducible on Ubuntu 19.10 Eoan with GNOME. The LTS version of Ubuntu (18.04.3) is unaffected. I have used it for months before switching to the latest non-LTS version. What I've tried to stop the freezes: - Closed all running applications and waited. It didn't improve the situation, so I restarted my user session. The freezes continued, so I performed a system reboot, which finally helped normalize things. I did not try to reproduce this on the Wayland session. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jan 24 11:13:56 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-12-27 (28 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1~19.10.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ** Description changed: It starts with very subtle stuttering that you notice when moving windows around, then keeps getting worse and worse until it starts freezing the UI for many seconds. I could only reproduce it twice in a couple of days. The applications open at the time are usually Atom, Firefox, Hexchat, GNOME Files and occasionally Eye of GNOME. I checked resource consumption at the time of the stutters. Memory consumption was about 50% of 8GB, while the swap partition was nearly full (after a long gaming session). Storage device is a SATA SSD. During the stutters and freezes, CPU usage is normal. Through the process list of System Monitor I cannot see any application overusing resources. Temperatures are also normal. One potentially problematic hardware device is the GPU: AMD RX 560 4GB (open source AMDGPU). Its temperature and fan speed were also normal at the time. I know my system is capable of handling this workload. Also, this is only reproducible on Ubuntu 19.10 Eoan with GNOME. The LTS version of Ubuntu (18.04.3) is unaffected. I have used it for months before switching to the latest non-LTS version. What I've tried to stop the freezes: - Closed all running applications and waited. It didn't improve the situation, so I restarted my user session. The freezes continued, so I performed a system reboot, which finally helped normalize things. + I did not try to reproduce this on the Wayland session. + ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jan 24 11:13:56 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-12-27 (28 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1~19.10.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860793 Title: Severe freezes that begin with minor stutters To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1860793/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849135] Re: Clicking Activities in the corner doesn't work
Let me add that I also tested a GNOME session (package 'gnome-session') and there was no difference from the results of testing the Ubuntu Xorg session. The proposed package does NOT fix the issue for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849135 Title: Clicking Activities in the corner doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1849135/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849135] Re: Clicking Activities in the corner doesn't work
I have tested 'mutter' version 3.34.3-1ubuntu1~19.10.1 from eoan- proposed on an Xorg session, and it doesn't fix the issue. Testing was made after package installation, followed by a system reboot. mutter/eoan-proposed,now 3.34.3-1ubuntu1~19.10.1 amd64 [installed] I don't know what other information to get from this. ** Tags removed: verification-needed-eoan ** Tags added: verification-failed-eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849135 Title: Clicking Activities in the corner doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1849135/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851661] [NEW] AppArmor denied operation open to snap pick-colour-picker
Public bug reported: I've written an issue here: https://github.com/stuartlangridge/ColourPicker/issues/63 Pick (a color picker distributed as a snap) will not launch. The creator of the application believes this to be a problem with my system, not with their app. Apparently, AppArmor is preventing it from starting. I'm not familiar with this MAC implementation, but the logs suggest that this is the problem. See the attachment. ``` nov 07 11:18:29 alq22 audit[27542]: AVC apparmor="DENIED" operation="open" profile="snap.pick-colour-picker.pick-colour-picker" name="/proc/27542/mounts" pid=27542 comm="python3" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 nov 07 11:18:29 alq22 kernel: audit: type=1400 audit(1573136309.796:304): apparmor="DENIED" operation="open" profile="snap.pick-colour-picker.pick-colour-picker" name="/proc/27542/mounts" pid=27542 comm="python3" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 ``` This is a fresh installation of Ubuntu 18.04.3. I take great care not to mess with system components such as snapd. Other snaps are working properly. ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Journalctl output - see last lines" https://bugs.launchpad.net/bugs/1851661/+attachment/5303495/+files/journalctl.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851661 Title: AppArmor denied operation open to snap pick-colour-picker To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1851661/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849217] Re: Steam game freezes on startup (only on Xorg session)
Let me update the description of the problem: I launch Counter Strike: Global Offensive and the screen freezes on the main menu. I can hear sounds from the game, I can hear feedback sounds from hover events, and I can press buttons on the frozen interface (it works) but I never see the frame change. In other words, the rendering gets stuck. It doesn't update. This wasn't reproducible on the first run. After I installed Ubuntu 19.10, I was able to happily play the game. The next day, I try to play again, and this starts to happen. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849217 Title: Steam game freezes on startup (only on Xorg session) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/steam/+bug/1849217/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849324] [NEW] Xorg logs spammed with failed page flip messages
Public bug reported: Please read this bug report: https://bugzilla.redhat.com/show_bug.cgi?id=1645553 I'm running Ubuntu MATE 19.10 Eoan, currently with xorg-server-source 2:1.20.5+git20191008-0ubuntu1 (xorg 1:7.7+19ubuntu12), and these messages are still being spammed into my Xorg logs. ``` [ 6794.424] (WW) AMDGPU(0): Page flip failed: Resource temporarily unavailable [ 6794.424] (EE) AMDGPU(0): present flip failed [ 6794.457] Failed to get FB for flip ``` A potential fix has already been merged here: https://gitlab.freedesktop.org/xorg/xserver/commit/26fe29f4fa53cbb7d51892e2cf397c084093812f?merge_request_iid=193 Fedora users already have it. I haven't tested Fedora to see if that fixes my problem. If that fix is already in Ubuntu, I believe we're talking about a new bug. ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Attachment added: "The Xorg log file, currently 15 MB large" https://bugs.launchpad.net/bugs/1849324/+attachment/5299212/+files/Xorg.0.log ** Description changed: - This bug has already been discussed here: + Please read this bug report: https://bugzilla.redhat.com/show_bug.cgi?id=1645553 I'm running Ubuntu MATE 19.10 Eoan, currently with xorg-server-source 2:1.20.5+git20191008-0ubuntu1 (xorg 1:7.7+19ubuntu12), and these messages are still being spammed into my Xorg logs. ``` [ 6794.424] (WW) AMDGPU(0): Page flip failed: Resource temporarily unavailable [ 6794.424] (EE) AMDGPU(0): present flip failed [ 6794.457] Failed to get FB for flip ``` A fix has already been merged here: https://gitlab.freedesktop.org/xorg/xserver/commit/26fe29f4fa53cbb7d51892e2cf397c084093812f?merge_request_iid=193 Fedora users already have it. I haven't tested Fedora to see if that fixes my problem. If that fix is already in Ubuntu, I believe we're talking about a new bug. ** Description changed: Please read this bug report: https://bugzilla.redhat.com/show_bug.cgi?id=1645553 I'm running Ubuntu MATE 19.10 Eoan, currently with xorg-server-source 2:1.20.5+git20191008-0ubuntu1 (xorg 1:7.7+19ubuntu12), and these messages are still being spammed into my Xorg logs. ``` [ 6794.424] (WW) AMDGPU(0): Page flip failed: Resource temporarily unavailable [ 6794.424] (EE) AMDGPU(0): present flip failed [ 6794.457] Failed to get FB for flip ``` - A fix has already been merged here: + A potential fix has already been merged here: https://gitlab.freedesktop.org/xorg/xserver/commit/26fe29f4fa53cbb7d51892e2cf397c084093812f?merge_request_iid=193 Fedora users already have it. I haven't tested Fedora to see if that fixes my problem. If that fix is already in Ubuntu, I believe we're talking about a new bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849324 Title: Xorg logs spammed with failed page flip messages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1849324/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849135] Re: Activities button does not respond to clicks on a specific pixel
It was already reported. Here: https://gitlab.gnome.org/GNOME/gnome-shell/issues/1649 And here: https://gitlab.gnome.org/GNOME/gnome-shell/issues/1601 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #1649 https://gitlab.gnome.org/GNOME/gnome-shell/issues/1649 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #1601 https://gitlab.gnome.org/GNOME/gnome-shell/issues/1601 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849135 Title: Activities button does not respond to clicks on a specific pixel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1849135/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849217] Re: Steam game freezes on startup (only on Xorg session)
** Attachment added: "Journalctl output of cs:go-related entries" https://bugs.launchpad.net/ubuntu/+source/steam/+bug/1849217/+attachment/5299054/+files/journalctl-csgo.txt ** Description changed: I believe I've found a regression in Ubuntu 19.10 Eoan concerning a Steam game. Start an Ubuntu session on Xorg and try to play Counter Strike: Global Offensive. The screen stutters, skips frames, becomes glitchy and ultimately unresponsive. It doesn't respond to ALT+F4, doesn't let me open the Activities overlay and ALT+TAB also does nothing. However, the mouse pointer still works and I can still hear some delayed sound effects from hover events in the game. My system logs are being spammed with errors related to the game. Take a look at the attachments. On a Wayland session, the game runs normally. I haven't tested other games yet. I believe a recent kernel update did this. It was version 5.3.0-19-generic. Before that update I could play CS:GO on Xorg. This problem is also reproducible on the latest Fedora Workstation, which uses a slightly newer kernel. Specs: Graphics: AMD RX 560 (AMDGPU, open source) CPU: Intel Core i3-8100 - Ubuntu 19.10 Eoan (fresh install) + Ubuntu 19.10 Eoan (GNOME, fresh install) I tried to use `apport-bug steam` but it failed saying the package isn't installed, which doesn't make sense. See attachments. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849217 Title: Steam game freezes on startup (only on Xorg session) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/steam/+bug/1849217/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849217] [NEW] Steam game freezes on startup (only on Xorg session)
Public bug reported: I believe I've found a regression in Ubuntu 19.10 Eoan concerning a Steam game. Start an Ubuntu session on Xorg and try to play Counter Strike: Global Offensive. The screen stutters, skips frames, becomes glitchy and ultimately unresponsive. It doesn't respond to ALT+F4, doesn't let me open the Activities overlay and ALT+TAB also does nothing. However, the mouse pointer still works and I can still hear some delayed sound effects from hover events in the game. My system logs are being spammed with errors related to the game. Take a look at the attachments. On a Wayland session, the game runs normally. I haven't tested other games yet. I believe a recent kernel update did this. It was version 5.3.0-19-generic. Before that update I could play CS:GO on Xorg. This problem is also reproducible on the latest Fedora Workstation, which uses a slightly newer kernel. Specs: Graphics: AMD RX 560 (AMDGPU, open source) CPU: Intel Core i3-8100 Ubuntu 19.10 Eoan (GNOME, fresh install) I tried to use `apport-bug steam` but it failed saying the package isn't installed, which doesn't make sense. See attachments. ** Affects: steam (Ubuntu) Importance: Undecided Status: New ** Tags: eoan ** Attachment added: "Journalctl" https://bugs.launchpad.net/bugs/1849217/+attachment/5299053/+files/journalctl.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849217 Title: Steam game freezes on startup (only on Xorg session) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/steam/+bug/1849217/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849157] [NEW] Default sound output device is never the expected one
Public bug reported: According to this page: https://wiki.ubuntu.com/Sound#Primary_sound_output, "if you manually choose an output device in the “Sound” settings panel or a similar utility, that choice should be followed". Well, despite me having explicitly selected the headset as the output device, on every reboot it falls back to the HDMI device. The headset is always plugged in. I believe this is a regression. On Ubuntu 19.04 and previous versions, it respected my preferences about the sound device. It is reproducible on both Xorg and Wayland sessions. Specs: OS: Ubuntu 19.10 Eoan (GNOME, Ubuntu sessions) Motherboard: Gigabyte B360M GAMING HD CPU: Intel Core i3-8100 Graphics: AMD RX 560 (AMDGPU, open source) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-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-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 21 12:49:52 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-10-21 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849157 Title: Default sound output device is never the expected one To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1849157/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849135] Re: Activities button does not respond to clicks on a specific pixel
No extensions were installed. Also, I'm using the native AMDGPU drivers, not the proprietary ones. I've tested the vanilla GNOME session as you suggested, and the bug is there too. Due to the hover highlighting of the panel items, I had a visual cue to test with. The highlighting does not happen at the unclickable spot. Move one pixel away from it, and the panel item lits up again. That was on Xorg, of course. On Wayland, the problem is gone, at least initially. As I said on the initial report, after using the Wayland session for a while, I started having the problem again. No idea what caused it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849135 Title: Activities button does not respond to clicks on a specific pixel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1849135/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849135] Re: Activities button does not respond to clicks on a specific pixel
** Description changed: Starting from Ubuntu 19.10, the top-left corner of the screen is unclickable. It's where the Activities button is. It is unresponsive to clicks to open the overlay, BUT it responds to clicks to close it. The unclickable spot is exactly one pixel large. - Important: This is only reproducible on Xorg, not on Wayland. + Edit: At first it seemed to be reproducible only on Xorg sessions, but + after using it for a while on Wayland, I am having the issue again. Specs: - Graphics: AMD RX 560 - CPU: Intel Core i3-8100 - Ubuntu 19.10 Eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849135 Title: Activities button does not respond to clicks on a specific pixel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1849135/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849135] Re: Activities button does not respond to clicks on a specific pixel
** Description changed: Starting from Ubuntu 19.10, the top-left corner of the screen is unclickable. It's where the Activities button is. It is unresponsive to clicks to open the overlay, BUT it responds to clicks to close it. The unclickable spot is exactly one pixel large. + Important: This is only reproducible on Xorg, not on Wayland. + Specs: - Graphics: AMD RX 560 - CPU: Intel Core i3-8100 - Ubuntu 19.10 Eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849135 Title: Activities button does not respond to clicks on a specific pixel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1849135/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849135] [NEW] Activities button does not respond to clicks on a specific pixel
Public bug reported: Starting from Ubuntu 19.10, the top-left corner of the screen is unclickable. It's where the Activities button is. It is unresponsive to clicks to open the overlay, BUT it responds to clicks to close it. The unclickable spot is exactly one pixel large. Specs: - Graphics: AMD RX 560 - CPU: Intel Core i3-8100 - Ubuntu 19.10 Eoan ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Screenshot of the Activities button with the mouse placed on the unclickable spot" https://bugs.launchpad.net/bugs/1849135/+attachment/5298946/+files/Captura%20de%20tela%20de%202019-10-21%2011-22-54.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849135 Title: Activities button does not respond to clicks on a specific pixel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1849135/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849135] Re: Activities button does not respond to clicks on a specific pixel
** Attachment added: "Journalctl logs" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1849135/+attachment/5298947/+files/journalctl.txt ** Description changed: Starting from Ubuntu 19.10, the top-left corner of the screen is unclickable. It's where the Activities button is. It is unresponsive to clicks to open the overlay, BUT it responds to clicks to close it. The unclickable spot is exactly one pixel large. Specs: - Graphics: AMD RX 560 - CPU: Intel Core i3-8100 - - Ubuntu 19.10 Eoan (fresh install, all updates) + - Ubuntu 19.10 Eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849135 Title: Activities button does not respond to clicks on a specific pixel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1849135/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848616] [NEW] LightDM crashes and logs me out when resuming from suspend
Public bug reported: I close the laptop lid and let it suspend. On resume, the whole desktop is frozen for a while. Nothing works during this time, no CAPS LOCK indicator LED, neither TTY switching. Then the screen goes dark and I see the LightDM login screen. I was logged out. This is a regression, since it wasn't reproducible on Ubuntu 19.04. How reproducible? 100% of the time. I am not totally sure it was LightDM's fault. It is my best guess based on the behavior I witnessed. See logs. Potentially relevant specs: - Intel HD Graphics 400 (Braswell) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: lightdm 1.30.0-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Oct 17 21:52:19 2019 InstallationDate: Installed on 2019-10-17 (0 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ** Attachment added: "Journalctl output from right after the problem" https://bugs.launchpad.net/bugs/1848616/+attachment/5298012/+files/journalctl.txt ** Description changed: I close the laptop lid and let it suspend. On resume, the whole desktop is frozen for a while. Nothing works during this time, no CAPS LOCK indicator LED, neither TTY switching. Then the screen goes dark and I see the LightDM login screen. I was logged out. This is a regression, since it wasn't reproducible on Ubuntu 19.04. + + How reproducible? + 100% of the time. I am not totally sure it was LightDM's fault. It is my best guess based on the behavior I witnessed. See logs. Potentially relevant specs: - Intel HD Graphics 400 (Braswell) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: lightdm 1.30.0-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Oct 17 21:52:19 2019 InstallationDate: Installed on 2019-10-17 (0 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848616 Title: LightDM crashes and logs me out when resuming from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1848616/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1844841] [NEW] Changes within a directory only appear if manually refreshing with F5
Public bug reported: When a file changes, or when a new file or folder is created in a directory, and Thunar is showing that directory, changes will not be visible until you press F5. This is not the case for the desktop (where my wallpaper is). Changes there are shown in real time, as expected. Thunar version 1.8.4-1ubuntu1 Xubuntu 19.04 ** Affects: thunar (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1844841 Title: Changes within a directory only appear if manually refreshing with F5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/1844841/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1757375] Re: Desktop unable to Suspend when Inactive
** Description changed: - On 16.04 (XFCE session and others) and possibly later the power-manager - is unable to suspend the system when the user is inactive. A PK user- - agent dialog is presented for the user to authenticate first - and as - this action occurs specifically when the user is idle and away the PC - can end up having an unplanned loss of power when the battery is - exhausted. + On Ubuntu 16.04 and later versions (Xfce/Xubuntu) the power-manager is + unable to suspend the system when the user is inactive. A PK user-agent + dialog is presented for the user to authenticate first - and as this + action occurs specifically when the user is idle and away the PC can end + up having an unplanned loss of power when the battery is exhausted. /var/log/auth.log shows: polkitd(authority=local): Operator of unix-session:c2 FAILED to authenticate to gain authorization for action org.freedesktop.login1.suspend for system-bus-name::1.47 [xfce4-power- manager --restart --sm-client-id 2992705d4-6fa2-4fba-966c-f7631ecd0b46] (owned by unix-user:tj) The problem seems to be "com.ubuntu.desktop.pkla" is missing an entry to allow Suspend. Currently it only has an entry for hibernate. Adding the following stanza solves the issue: [Enable suspend by default in logind] Identity=unix-user:* Action=org.freedesktop.login1.suspend;org.freedesktop.login1.inhibit-handle-suspend-key;org.freedesktop.login1;org.freedesktop.login1.suspend-multiple-sessions;org.freedesktop.login1.suspend-ignore-inhibit ResultActive=yes ResultInactive=yes -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1757375 Title: Desktop unable to Suspend when Inactive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-desktop-privileges/+bug/1757375/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1757375] Re: Desktop unable to Suspend when Inactive
I can also reproduce this on both of my computers running Xubuntu 19.04, a desktop and a laptop. Just to be extra clear on what the issue is: If the computer is left idle for 10 minutes, the screen locks. When 15 minutes have passed, it should suspend, but it never does. I unlock the screen to investigate why, and find that there is a prompt window asking my password in order to allow the system to suspend. What usually happens as a consequence: I fall asleep with the laptop still running, and on the next day the thing is powered off with only 1% of battery power. It stayed ON all night. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1757375 Title: Desktop unable to Suspend when Inactive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-desktop-privileges/+bug/1757375/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1757375] Re: Desktop unable to Suspend when Inactive
Thanks for the response. Sorry for the delay, I didn't get a notification about this. If by admin you mean one that has sudo privileges or a member of group `adm`, then yes. It's the default user created by the installer. I could reproduce this on Arch Linux and other distros IIRC. The workaround works on them too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1757375 Title: Desktop unable to Suspend when Inactive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-desktop-privileges/+bug/1757375/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839900] [NEW] Power button action not working
Public bug reported: I've configured it so that the system would suspend after pressing the power button. This does not happen. How is it reproducible? It started after updating from Ubuntu 18.04.2 to 18.04.3. New packages, new kernel, new bug. On Ubuntu 19.04, this has been reproducible since its release. This is also reproducible on other distributions with the GNOME desktop. This is exclusive to the GNOME desktop. No other desktop I've tried has issues with the power button action. Ubuntu 18.04.3 Kernel 5.0.0-23-generic GNOME 3.28.2 See attached logs. Near the end of it I attempted to make the system suspend by repeatedly pressing the power button, as configured in GNOME Settings > Power > When the power button is pressed. ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Attachment added: "journalctl output" https://bugs.launchpad.net/bugs/1839900/+attachment/5282269/+files/journalctl.txt ** Package changed: systemd (Ubuntu) => gnome-settings-daemon (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839900 Title: Power button action not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1839900/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838720] Re: Power button action not working
** Attachment added: "journalctl output" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1838720/+attachment/5280445/+files/journalctl.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838720 Title: Power button action not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1838720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838720] [NEW] Power button action not working
Public bug reported: In the Power tab, the option "When the power button is pressed" is set to "Suspend". However, this action is not executed on power button press. It does nothing. This is always reproducible on Ubuntu 19.04, while on Ubuntu 18.04.2 it works as expected. gnome-control-center 3.32.2 Kernel 5.0.0-23-generic Ubuntu 19.04 Disco See attached logs. ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Attachment added: "gnome-control-center -v output" https://bugs.launchpad.net/bugs/1838720/+attachment/5280444/+files/gnome-control-center-log.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838720 Title: Power button action not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1838720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838720] Re: Power button action not working
** Attachment added: "dmesg output" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1838720/+attachment/5280446/+files/dmesg.txt ** Description changed: In the Power tab, the option "When the power button is pressed" is set to "Suspend". However, this action is not executed on power button press. It does nothing. This is always reproducible on Ubuntu 19.04, while on Ubuntu 18.04.2 it works as expected. + gnome-control-center 3.32.2 + Kernel 5.0.0-23-generic + Ubuntu 19.04 Disco + See attached logs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838720 Title: Power button action not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1838720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820173] Re: Screen brightness buttons change gain instead of brightness
I have a similar netbook called Dell Inspiron 11 3162 in which this is reproducible. Changing brightness with the FN (function) key combinations change the gamma of the screen instead of the actual brightness. It's a fake brightness change, like the one Redshift can do if you're familiar with it. If I go to the settings and open Brightness, I can move the slider there and change the brightness as expected. It's just the key combination that doesn't work as we expect. I have tested Lubuntu 19.04 and Fedora 30 LXQt in their default settings. In both this is reproducible. I don't have these systems installed right now. I might try Lubuntu 19.04 in the coming days and attach the requested log files here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820173 Title: Screen brightness buttons change gain instead of brightness To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lubuntu-meta/+bug/1820173/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1757375] Re: Desktop unable to Suspend when Inactive
The solution is right here, so simple to apply. Why is this ignored? No one else suspends their machines? Merge the necessary polkit rule, please. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1757375 Title: Desktop unable to Suspend when Inactive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-desktop-privileges/+bug/1757375/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834807] Re: Two alert sounds playing at the same time
All right, that fixes it. Now I have the expected behavior. Only one sound plays: the one selected through GNOME Settings. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834807 Title: Two alert sounds playing at the same time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1834807/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834807] Re: Two alert sounds playing at the same time
Sorry, I'm not sure what to remove. My file is slightly different from the one in that commit. Is it OK to comment out everything at /usr/bin /start-pulseaudio-x11? There are other if blocks that don't seem to be related. I will try to comment out only the if block that references `bell.ogg` and come back with the result. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834807 Title: Two alert sounds playing at the same time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1834807/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
