[Desktop-packages] [Bug 2040311] [NEW] manpage for gdm3.8 contains content of gdm-screenshot.1
Public bug reported: man 8 gdm3 shows content for gdm-screenshot OS: ubuntu 22.04 package: gdm3/jammy-updates,now 42.0-1ubuntu7.22.04.3 amd64 [installed,automatic] ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/2040311 Title: manpage for gdm3.8 contains content of gdm-screenshot.1 Status in gdm3 package in Ubuntu: New Bug description: man 8 gdm3 shows content for gdm-screenshot OS: ubuntu 22.04 package: gdm3/jammy-updates,now 42.0-1ubuntu7.22.04.3 amd64 [installed,automatic] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2040311/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1981109] Re: server image pulls in ModemManager via fwupd, consumes 25MiB RAM in every container
Package fwupd-signed is still installed, is it needed? Checked in https://cloud- images.ubuntu.com/releases/22.04/release/ubuntu-22.04-server-cloudimg- amd64.img and https://cloud-images.ubuntu.com/mantic/current/mantic- server-cloudimg-amd64.img. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1981109 Title: server image pulls in ModemManager via fwupd, consumes 25MiB RAM in every container Status in fwupd package in Ubuntu: Invalid Status in livecd-rootfs package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Triaged Status in ubuntu-meta package in Ubuntu: New Status in fwupd source package in Jammy: Invalid Status in livecd-rootfs source package in Jammy: Fix Released Status in modemmanager source package in Jammy: New Status in ubuntu-meta source package in Jammy: New Bug description: [Impact] Cloud images should not have fwupd, modemmanager, and udisks2 installed as those are not needed and only taking up memory. [Test Case] Build cloud images with livecd-rootfs and confirm that fwupd, modemmanager, and udisks2 are not present and not running. [Regression Potential] Only thing that might happen is for any of the 3 listed packages getting removed from images where they might be used. So possibly double-checking if this will affect preinstalled server images and if they care about this or not. [Original Description] Looking at memory utilization in a pristine Ubuntu lxd container (top -o RES), I see that ModemManager is running, which I was surprised to see is present at all in the stock image. Tracking this I find that fwupd depends on libmm-glib0, which in turn Recommends: modemmanager. Libraries in general should not recommend daemons, so it's possible this should be fixed by libmm-glib0 dropping this Recommends. It certainly doesn't seem to be a deliberate decision by the Server Team to have modemmanager installed and running by default on all systems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1981109/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2020709] [NEW] Screens won't turn on after manually suspending
Public bug reported: SUMMARY When returning from "suspend" (sleep mode), the monitors do not turn on, or rarely return with low resolution (640x480). Wayland does not allow resolution change (attachment). I have two HP V206hz monitors that have a maximum resolution of 1600x900x60hz and are connected to a Radeon RX 6600 via cable (displayport > DVI). STEPS TO REPRODUCE 1. Manually suspend the computer. 2. Wait for the suspend process to finish (front panel LED flashes). 3. Press any key to wake up the computer. OBSERVED RESULT A1 - The screens do not turn on (monitor LED is blinking) after manual suspension. A2 - Sometimes the screens turn on, but with low resolution (640x480). A3 - Sometimes one of the screens returns with a resolution of 640x480 after returning from automatic suspension (when the automatic shutdown of the splint is not active). A4 - If the screen turns off automatically (before the automatic suspension) the monitor video returns with adequate resolution (1600x900) EXPECTED OUTCOME The screens turn on after the computer wakes up from sleep mode. SOFTWARE/OS VERSIONS Linux/KDE Plasma: OS: Kubuntu 22.04.2 LTS x86_64 Kernel: 5.19.0-42-generic KDE Plasma Version: 5.24.7 KDE Framework Version: 5.92.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION To view any content, you must force restart with the power button or remove and reinsert the display cable. I installed the amd package for the gpu but the problem remained. https://www.amd.com/en/support/graphics/amd-radeon-6000-series/amd-radeon-6600-series/amd-radeon-rx-6600 Attachment https://pastebin.com/Xbq3JaWT https://bugs.kde.org/show_bug.cgi?id=470180#attach_159212 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-42.43~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: KDE Date: Wed May 24 17:12:50 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 23 [Radeon RX 6600/6600 XT/6600M] [1002:73ff] (rev c7) (prog-if 00 [VGA controller]) Subsystem: Tul Corporation / PowerColor Navi 23 [Radeon RX 6600/6600 XT/6600M] [148c:2413] InstallationDate: Installed on 2023-05-20 (3 days ago) InstallationMedia: Kubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: To Be Filled By O.E.M. B550M-ITX/ac ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.19.0-42-generic root=UUID=14e3583d-5b94-40f1-b1ff-0d1d175e7bc8 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/27/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: P2.20 dmi.board.name: B550M-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP2.20:bd12/27/2022:br5.17:svnToBeFilledByO.E.M.:pnB550M-ITX/ac:pvrToBeFilledByO.E.M.:rvnASRock:rnB550M-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: B550M-ITX/ac dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy kubuntu ubuntu ** Attachment added: "Screenshot - screen configuration" https://bugs.launchpad.net/bugs/2020709/+attachment/5675472/+files/Screenshot_20230522_113736.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2020709 Title: Screens won't turn on after manually suspending Status in xorg package in Ubuntu: New Bug description: SUMMARY When returning from "suspend" (sleep mode), the monitors do not turn on, or rarely return
[Desktop-packages] [Bug 2019137] Re: gnome-software should (?) be separated from the packagekit
Also, I would like to emphasize that I am essentially just suggesting that make gnome-software more "modular". I'm not proposing to completely eliminate/cut out and not ship PackageKit as a basic package, if it's really needed somewhere. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/2019137 Title: gnome-software should (?) be separated from the packagekit Status in gnome-software package in Ubuntu: Confirmed Bug description: Given that the Snap Store is currently the default in Ubuntu instead of GNOME Software, the only reason GNOME Software (along with the Snap Store) can be installed is to support Flatpak applications. In the current instance, if you want to add flatpak support, GNOME Software is installed with both the apt packagekit add-on and the flatpak plugin, which is duplication of work (Software Updater already works on updates, and Snap Store works on showing deb apps). And since the future app store explicitly refuses [1], [2] to support flatpak applications, users who need this package format will be forced to put GNOME Software with everything I pointed out above. Therefore, it would be very nice if the developers removed the packagekit add-on from the "gnome-software part" and made it a "plug- in for gnome-software". I, unfortunately, have no such experience with packaging deb packages at the moment, and it turns out that it will obviously be necessary to work out both the code part (which, as far as I can see, won't be very difficult [3]), as well as the part where we will have to figure out where and how to insert the plugin as mandatory (for example, when the user completely gives up on snap packages) and as optional (because the Snap Store already stands). Also, let me know if this needs to be sent to upstream (Debian) instead of here. --- 1. https://github.com/ubuntu-flutter-community/software/issues/126 2. https://github.com/ubuntu-flutter-community/software/issues/30 3. https://build.opensuse.org/request/show/1031279 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/2019137/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2019137] Re: gnome-software should (?) be separated from the packagekit
Matthias, I did not suggest to remove PackageKit support completely. I was suggesting to separate PackageKit and make it a separate plugin. This would make it possible to install GNOME Software exclusively with the flatpak plugin, for those times when you only need to install flatpak to the current Ubuntu installations which already include the Snap Store by default. At the moment when trying to add something related to flatpak, one more store (besides Snap Store) is installed which operates with deb packages. This makes no sense, since Snap Store already does this (and it does it, as I understand, wherever snap is installed). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/2019137 Title: gnome-software should (?) be separated from the packagekit Status in gnome-software package in Ubuntu: Confirmed Bug description: Given that the Snap Store is currently the default in Ubuntu instead of GNOME Software, the only reason GNOME Software (along with the Snap Store) can be installed is to support Flatpak applications. In the current instance, if you want to add flatpak support, GNOME Software is installed with both the apt packagekit add-on and the flatpak plugin, which is duplication of work (Software Updater already works on updates, and Snap Store works on showing deb apps). And since the future app store explicitly refuses [1], [2] to support flatpak applications, users who need this package format will be forced to put GNOME Software with everything I pointed out above. Therefore, it would be very nice if the developers removed the packagekit add-on from the "gnome-software part" and made it a "plug- in for gnome-software". I, unfortunately, have no such experience with packaging deb packages at the moment, and it turns out that it will obviously be necessary to work out both the code part (which, as far as I can see, won't be very difficult [3]), as well as the part where we will have to figure out where and how to insert the plugin as mandatory (for example, when the user completely gives up on snap packages) and as optional (because the Snap Store already stands). Also, let me know if this needs to be sent to upstream (Debian) instead of here. --- 1. https://github.com/ubuntu-flutter-community/software/issues/126 2. https://github.com/ubuntu-flutter-community/software/issues/30 3. https://build.opensuse.org/request/show/1031279 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/2019137/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2019137] Re: gnome-software should (?) be separated from the packagekit
** Changed in: gnome-software (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/2019137 Title: gnome-software should (?) be separated from the packagekit Status in gnome-software package in Ubuntu: Confirmed Bug description: Given that the Snap Store is currently the default in Ubuntu instead of GNOME Software, the only reason GNOME Software (along with the Snap Store) can be installed is to support Flatpak applications. In the current instance, if you want to add flatpak support, GNOME Software is installed with both the apt packagekit add-on and the flatpak plugin, which is duplication of work (Software Updater already works on updates, and Snap Store works on showing deb apps). And since the future app store explicitly refuses [1], [2] to support flatpak applications, users who need this package format will be forced to put GNOME Software with everything I pointed out above. Therefore, it would be very nice if the developers removed the packagekit add-on from the "gnome-software part" and made it a "plug- in for gnome-software". I, unfortunately, have no such experience with packaging deb packages at the moment, and it turns out that it will obviously be necessary to work out both the code part (which, as far as I can see, won't be very difficult [3]), as well as the part where we will have to figure out where and how to insert the plugin as mandatory (for example, when the user completely gives up on snap packages) and as optional (because the Snap Store already stands). Also, let me know if this needs to be sent to upstream (Debian) instead of here. --- 1. https://github.com/ubuntu-flutter-community/software/issues/126 2. https://github.com/ubuntu-flutter-community/software/issues/30 3. https://build.opensuse.org/request/show/1031279 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/2019137/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2019137] [NEW] gnome-software should (?) be separated from the packagekit
Public bug reported: Given that the Snap Store is currently the default in Ubuntu instead of GNOME Software, the only reason GNOME Software (along with the Snap Store) can be installed is to support Flatpak applications. In the current instance, if you want to add flatpak support, GNOME Software is installed with both the apt packagekit add-on and the flatpak plugin, which is duplication of work (Software Updater already works on updates, and Snap Store works on showing deb apps). And since the future app store explicitly refuses [1], [2] to support flatpak applications, users who need this package format will be forced to put GNOME Software with everything I pointed out above. Therefore, it would be very nice if the developers removed the packagekit add-on from the "gnome-software part" and made it a "plug-in for gnome-software". I, unfortunately, have no such experience with packaging deb packages at the moment, and it turns out that it will obviously be necessary to work out both the code part (which, as far as I can see, won't be very difficult [3]), as well as the part where we will have to figure out where and how to insert the plugin as mandatory (for example, when the user completely gives up on snap packages) and as optional (because the Snap Store already stands). Also, let me know if this needs to be sent to upstream (Debian) instead of here. --- 1. https://github.com/ubuntu-flutter-community/software/issues/126 2. https://github.com/ubuntu-flutter-community/software/issues/30 3. https://build.opensuse.org/request/show/1031279 ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/2019137 Title: gnome-software should (?) be separated from the packagekit Status in gnome-software package in Ubuntu: Confirmed Bug description: Given that the Snap Store is currently the default in Ubuntu instead of GNOME Software, the only reason GNOME Software (along with the Snap Store) can be installed is to support Flatpak applications. In the current instance, if you want to add flatpak support, GNOME Software is installed with both the apt packagekit add-on and the flatpak plugin, which is duplication of work (Software Updater already works on updates, and Snap Store works on showing deb apps). And since the future app store explicitly refuses [1], [2] to support flatpak applications, users who need this package format will be forced to put GNOME Software with everything I pointed out above. Therefore, it would be very nice if the developers removed the packagekit add-on from the "gnome-software part" and made it a "plug- in for gnome-software". I, unfortunately, have no such experience with packaging deb packages at the moment, and it turns out that it will obviously be necessary to work out both the code part (which, as far as I can see, won't be very difficult [3]), as well as the part where we will have to figure out where and how to insert the plugin as mandatory (for example, when the user completely gives up on snap packages) and as optional (because the Snap Store already stands). Also, let me know if this needs to be sent to upstream (Debian) instead of here. --- 1. https://github.com/ubuntu-flutter-community/software/issues/126 2. https://github.com/ubuntu-flutter-community/software/issues/30 3. https://build.opensuse.org/request/show/1031279 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/2019137/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006468] Re: firefox does not detect mousemove events
What triggers this issue is moving the focus away from Firefox. I do a lot of alt+tab and the issue appears after several of them. Then I need to close Firefox and start again to fix the issue. Others have pointed out that this is Firefox issue with Wayland. Even those that have installed Firefox using apt have experienced the same. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/2006468 Title: firefox does not detect mousemove events Status in firefox package in Ubuntu: Confirmed Bug description: I have an issue, which I saw only on Firefox : after some time (or some event which I haven't identified yet), Firefox does not react to my mouse movement events meaning : * when hovering over an HTML item, it does not highlight/change appearance even if it is supposed to do so, * when hovering over a clickable item, the cursor does not change, * when hovering over selectable text, the cursor does not change, * tooltips do not appear, * etc ... if I trigger other GUI events (if I *click*, or if I *press any keyboard key* -- `[A]`, `[Shift]`, `[Ctrl]` ...), then the GUI reacts (cursor changes, tooltips appear, animations get triggered ...), a bit as if, by handling that other event, firefox realized "oh, the cursor is actually there", but with no external event, my mousenter/mouseleave events seem to be ignored, or stalled. Running Ubuntu 22.10 (kinetic), and regular firefox snap install (my current version: 109.0.1-1). As said in the previous sentence: firefox is installed through snap (which, if I am correct, is the default way to install firefox on a Ubuntu system these days) not through an apt package. Is this a known issue ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2006468/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990200] Re: goa-daemon crashed with SIGABRT
Since the update, I've suspended and woken up the computer numerous times, and I haven't seen the error once. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to librest in Ubuntu. https://bugs.launchpad.net/bugs/1990200 Title: goa-daemon crashed with SIGABRT Status in gnome-online-accounts: New Status in gnome-online-accounts package in Ubuntu: Invalid Status in librest package in Ubuntu: Fix Released Status in librest source package in Kinetic: Fix Committed Bug description: * Impact The gnome-online-accounts sometime crash after resuming from suspend * Test case Install the librest update, restart your system and verify that configured online accounts keep working. Taking a Google account example, calendar events should show in gnome-calendar and the top panel widget, evolution should list your email account and nautilus should be able to browse your gdrive folder. We should also confirm that error reports stop with the library update * Regression potential The patch makes the code better handle an empty payload. The librest rdepends in the archive are gnome-initial-setup/gnome-online- accounts/gnome-maps so we should verify that those keep working as expected. - Unknown cause of this crash. Was alerted to it after waking the system from sleep mode. ProblemType: Crash DistroRelease: Ubuntu 22.10 Package: gnome-online-accounts 3.45.2-3 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 Date: Mon Sep 19 19:26:29 2022 ExecutablePath: /usr/libexec/goa-daemon InstallationDate: Installed on 2022-09-17 (2 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220917) ProcCmdline: /usr/libexec/goa-daemon ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 Signal: 6 SourcePackage: gnome-online-accounts StacktraceTop: () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /lib/x86_64-linux-gnu/librest-1.0.so.0 rest_proxy_call_sync () at /lib/x86_64-linux-gnu/librest-1.0.so.0 () at /lib/x86_64-linux-gnu/libgoa-backend-1.0.so.1 Title: goa-daemon crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-online-accounts/+bug/1990200/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990200] Re: goa-daemon crashed with SIGABRT
I experienced this bug as well, so I updated to the proposed librest package (https://launchpad.net/ubuntu/+source/librest/0.9.1-2ubuntu1). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to librest in Ubuntu. https://bugs.launchpad.net/bugs/1990200 Title: goa-daemon crashed with SIGABRT Status in gnome-online-accounts: New Status in gnome-online-accounts package in Ubuntu: Invalid Status in librest package in Ubuntu: Fix Released Status in librest source package in Kinetic: Fix Committed Bug description: * Impact The gnome-online-accounts sometime crash after resuming from suspend * Test case Install the librest update, restart your system and verify that configured online accounts keep working. Taking a Google account example, calendar events should show in gnome-calendar and the top panel widget, evolution should list your email account and nautilus should be able to browse your gdrive folder. We should also confirm that error reports stop with the library update * Regression potential The patch makes the code better handle an empty payload. The librest rdepends in the archive are gnome-initial-setup/gnome-online- accounts/gnome-maps so we should verify that those keep working as expected. - Unknown cause of this crash. Was alerted to it after waking the system from sleep mode. ProblemType: Crash DistroRelease: Ubuntu 22.10 Package: gnome-online-accounts 3.45.2-3 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 Date: Mon Sep 19 19:26:29 2022 ExecutablePath: /usr/libexec/goa-daemon InstallationDate: Installed on 2022-09-17 (2 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220917) ProcCmdline: /usr/libexec/goa-daemon ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 Signal: 6 SourcePackage: gnome-online-accounts StacktraceTop: () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /lib/x86_64-linux-gnu/librest-1.0.so.0 rest_proxy_call_sync () at /lib/x86_64-linux-gnu/librest-1.0.so.0 () at /lib/x86_64-linux-gnu/libgoa-backend-1.0.so.1 Title: goa-daemon crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-online-accounts/+bug/1990200/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1995396] Re: /usr/lib/x86_64-linux-gnu/webkit2gtk-4.1/WebKitWebProcess:6:std::__throw_bad_optional_access:std::optional:WebCore::ColorInputType::valueAsColor:WebCore::ColorInpu
I find a way to remove the « Transparency scrool chooser bar » tested on my webkit2gtk (2.38.1-1) that I rebuilt with that bar off for now. ref: https://docs.gtk.org/gtk3/method.ColorChooser.set_use_alpha.html Check the patch. Temporary remove that bar solve my problem for now. Thank you ** Patch added: "remove_alpha_from_color_chooser.patch" https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/1995396/+attachment/5628322/+files/remove_alpha_from_color_chooser.patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webkit2gtk in Ubuntu. https://bugs.launchpad.net/bugs/1995396 Title: /usr/lib/x86_64-linux- gnu/webkit2gtk-4.1/WebKitWebProcess:6:std::__throw_bad_optional_access:std::optional:WebCore::ColorInputType::valueAsColor:WebCore::ColorInputType::didChooseColor:IPC::callMemberFunctionImpl Status in webkit2gtk package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding webkit2gtk. This problem was most recently seen with package version 2.38.0-1, the problem page at https://errors.ubuntu.com/problem/9a29462dc27e2727d25b296c660a56a6d15068de contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/1995396/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1970663]
> sudo snap connect firefox:icon-themes gtk-common-themes:icon-themes Confirming, worked for me as well. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1970663 Title: Tiny mouse cursor in firefox snap Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Since a few day I've updated to Ubuntu Mate 22.04 with the firefox snap. Since then I've been having this strange bug. I have a 4k screen which I'm running at a 2180p resolution with scaling on HiDPI. This runs just fine except for in firefox. In the new firefox snap I get a really tiny mouse cursor. I also checked other snap, it is not the case there. Regards, Chris --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-02-02 (83 days ago) InstallationMedia: Ubuntu-MATE 21.10 "Impish Indri" - Release amd64 (20211012) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: ubuntu-mate-artwork ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Snap: firefox 99.0.1-1 (stable) Snap.Changes: no changes found Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-19 (7 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-02-02 (83 days ago) InstallationMedia: Ubuntu-MATE 21.10 "Impish Indri" - Release amd64 (20211012) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: ubuntu-mate-artwork ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Snap: firefox 99.0.1-1 (stable) Snap.Changes: no changes found Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-19 (7 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1970663/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1970663]
Another interesting observation. The cursor theme switches back to the correct system one while dragging the Firefox window. But drops to the tiny defaults as soon as you let go of dragging and move the cursor. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1970663 Title: Tiny mouse cursor in firefox snap Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Since a few day I've updated to Ubuntu Mate 22.04 with the firefox snap. Since then I've been having this strange bug. I have a 4k screen which I'm running at a 2180p resolution with scaling on HiDPI. This runs just fine except for in firefox. In the new firefox snap I get a really tiny mouse cursor. I also checked other snap, it is not the case there. Regards, Chris --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-02-02 (83 days ago) InstallationMedia: Ubuntu-MATE 21.10 "Impish Indri" - Release amd64 (20211012) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: ubuntu-mate-artwork ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Snap: firefox 99.0.1-1 (stable) Snap.Changes: no changes found Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-19 (7 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-02-02 (83 days ago) InstallationMedia: Ubuntu-MATE 21.10 "Impish Indri" - Release amd64 (20211012) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: ubuntu-mate-artwork ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Snap: firefox 99.0.1-1 (stable) Snap.Changes: no changes found Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-19 (7 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1970663/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1970663]
Created attachment 9296037 Old-style tiny cursor screenshot In fact, it seems to use the old X pre-modern desktop era cursors. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1970663 Title: Tiny mouse cursor in firefox snap Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Fix Released Bug description: Since a few day I've updated to Ubuntu Mate 22.04 with the firefox snap. Since then I've been having this strange bug. I have a 4k screen which I'm running at a 2180p resolution with scaling on HiDPI. This runs just fine except for in firefox. In the new firefox snap I get a really tiny mouse cursor. I also checked other snap, it is not the case there. Regards, Chris --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-02-02 (83 days ago) InstallationMedia: Ubuntu-MATE 21.10 "Impish Indri" - Release amd64 (20211012) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: ubuntu-mate-artwork ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Snap: firefox 99.0.1-1 (stable) Snap.Changes: no changes found Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-19 (7 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-02-02 (83 days ago) InstallationMedia: Ubuntu-MATE 21.10 "Impish Indri" - Release amd64 (20211012) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: ubuntu-mate-artwork ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Snap: firefox 99.0.1-1 (stable) Snap.Changes: no changes found Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-19 (7 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1970663/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1970663]
Seeing the same with 105.0 with the rest of setup exactly like sahab.yazdani. Interestingly, my other laptop with an Intel video and fractional scaling doesn't have the problem. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1970663 Title: Tiny mouse cursor in firefox snap Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Fix Released Bug description: Since a few day I've updated to Ubuntu Mate 22.04 with the firefox snap. Since then I've been having this strange bug. I have a 4k screen which I'm running at a 2180p resolution with scaling on HiDPI. This runs just fine except for in firefox. In the new firefox snap I get a really tiny mouse cursor. I also checked other snap, it is not the case there. Regards, Chris --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-02-02 (83 days ago) InstallationMedia: Ubuntu-MATE 21.10 "Impish Indri" - Release amd64 (20211012) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: ubuntu-mate-artwork ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Snap: firefox 99.0.1-1 (stable) Snap.Changes: no changes found Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-19 (7 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-02-02 (83 days ago) InstallationMedia: Ubuntu-MATE 21.10 "Impish Indri" - Release amd64 (20211012) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: ubuntu-mate-artwork ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Snap: firefox 99.0.1-1 (stable) Snap.Changes: no changes found Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-19 (7 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1970663/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965123] Re: Active launchers area pixels (corners) missing
It seems to be something when loading the session, because after locking and unlocking the screen, it goes back to normal. ** Attachment added: "Captura de tela de 2022-09-14 13-04-59.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965123/+attachment/5616056/+files/Captura%20de%20tela%20de%202022-09-14%2013-04-59.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1965123 Title: Active launchers area pixels (corners) missing Status in Dash to dock: Unknown Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: Ubuntu 22.04 development branch @ 16/03/2022 after yesterdays updates to gnome 42 beta the docks area around the active launcher is missing 4 pixels in the corners when hovering mouse over them switching to another active launchers can be reproduced non-active area around launchers does not suffer this bug ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-ubuntu-dock 72~ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Mar 16 12:55:20 2022 PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1965123/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965123] Re: Active launchers area pixels (corners) missing
The problem also occurs for me on laptop with Intel Graphics. I use the dark theme. ** Attachment added: "BdSZUtI.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965123/+attachment/5615491/+files/BdSZUtI.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1965123 Title: Active launchers area pixels (corners) missing Status in Dash to dock: Unknown Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: Ubuntu 22.04 development branch @ 16/03/2022 after yesterdays updates to gnome 42 beta the docks area around the active launcher is missing 4 pixels in the corners when hovering mouse over them switching to another active launchers can be reproduced non-active area around launchers does not suffer this bug ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-ubuntu-dock 72~ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Mar 16 12:55:20 2022 PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1965123/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1987711] Re: Ubuntu display get shifted after some time.
I restarted pc, and this error occured again today at 1AM. i.e. 26.8.2022 01:18:34 +- 1second. logs should be in attachment. ** Attachment added: "errLog.zip" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1987711/+attachment/5611969/+files/errLog.zip -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1987711 Title: Ubuntu display get shifted after some time. Status in xorg-server package in Ubuntu: Incomplete Bug description: It is continuation of this bug: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1986583 where advised fix was applied. Summay: After ubuntu is turned on, after some time screen gets shifted to side. (and starts to overlap) I setup webcamera to record screen, and video below shows what it looked like. after fix were applied. www.ms.mff.cuni.cz/~krasicei/capture-0231.bug.crop.slow.mp4 (video was cropped, and slowed down 2x) before fix was applied shift looked somehow like this: www.ms.mff.cuni.cz/~krasicei/bug17-50-18-8-2022.c.mp4 (video is also cropped, and slowed down 2x) During shift no one was present on computer. Is there any idea how to enable some more detailed log or something? I probably can pinpoint exact moment in time when shift happened. i tried to read log journalctl, but I found nothing interesting. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: CasperMD5CheckResult: unknown Date: Fri Aug 26 02:31:10 2022 DistUpgraded: 2022-08-02 14:36:41,704 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:2015] InstallationDate: Installed on 2022-02-17 (189 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 222a:0001 ILI Technology Corp. Multi-Touch Screen Bus 001 Device 002: ID 1a2c:2d23 China Resource Semico Co., Ltd Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Default string Default string ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=582fb3cc-8ef6-460b-b9ae-a16f81c604a7 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to jammy on 2022-08-02 (23 days ago) dmi.bios.date: 10/07/2021 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GSKU0504.V54 dmi.board.asset.tag: Default string dmi.board.name: SKYBAY dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGSKU0504.V54:bd10/07/2021:br5.12:svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnDefaultstring:rnSKYBAY:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: Default string dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Default string version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1987711/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1987711] Re: Ubuntu display get shifted after some time.
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1987711 Title: Ubuntu display get shifted after some time. Status in xorg-server package in Ubuntu: Incomplete Bug description: It is continuation of this bug: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1986583 where advised fix was applied. Summay: After ubuntu is turned on, after some time screen gets shifted to side. (and starts to overlap) I setup webcamera to record screen, and video below shows what it looked like. after fix were applied. www.ms.mff.cuni.cz/~krasicei/capture-0231.bug.crop.slow.mp4 (video was cropped, and slowed down 2x) before fix was applied shift looked somehow like this: www.ms.mff.cuni.cz/~krasicei/bug17-50-18-8-2022.c.mp4 (video is also cropped, and slowed down 2x) During shift no one was present on computer. Is there any idea how to enable some more detailed log or something? I probably can pinpoint exact moment in time when shift happened. i tried to read log journalctl, but I found nothing interesting. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: CasperMD5CheckResult: unknown Date: Fri Aug 26 02:31:10 2022 DistUpgraded: 2022-08-02 14:36:41,704 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:2015] InstallationDate: Installed on 2022-02-17 (189 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 222a:0001 ILI Technology Corp. Multi-Touch Screen Bus 001 Device 002: ID 1a2c:2d23 China Resource Semico Co., Ltd Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Default string Default string ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=582fb3cc-8ef6-460b-b9ae-a16f81c604a7 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to jammy on 2022-08-02 (23 days ago) dmi.bios.date: 10/07/2021 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GSKU0504.V54 dmi.board.asset.tag: Default string dmi.board.name: SKYBAY dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGSKU0504.V54:bd10/07/2021:br5.12:svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnDefaultstring:rnSKYBAY:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: Default string dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Default string version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1987711/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1986583] Re: Screen after some time get shifted and starts to overlap
Just, one more question, I removed config, and removed xserver-xorg-video-intel driver but I do not know if it took any effect. How do I find out what driver was used before, and what is used now? lshw -c video shows: driver=i915 is it that obsolete driver? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1986583 Title: Screen after some time get shifted and starts to overlap Status in xserver-xorg-video-intel package in Ubuntu: Won't Fix Bug description: problem resembles a lot this one: https://askubuntu.com/questions/07/ubuntu-desktop-shifted-to-right "I am encountering a strange problem, my whole desktop has shifted to right." But different in a way, that when pc is started it shows everything just fine. But when computer is powered on a few days straight, display gets shifted. Some times just cca 1/4 of screen, sometimes it shifts over half of the screen. Computer should be used to run 8hours straight (it is intended for customer) When i switch from graphic display to tty (ctrl+alt+num) and back, display gets "restarted" and problem is fixed. But it is just temporary. Restart fixes it also. Last time i encountered this behavior today between 17-18hour. But have no idea what or where to look for. yes, and when one connects to display over X11 or teamviewer screen appears to be okay, so one will notice this problem if using pc remotely 1) lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 2) xorg: Installed: 1:7.7+23ubuntu2 Candidate: 1:7.7+23ubuntu2 Version table: *** 1:7.7+23ubuntu2 500 500 http://cz.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status 3) expect that display will stay where it is on the start of computer 4) display gets shifted to some distance from unknown reason (Maybe x11vnc or teamviewer usage or something). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Aug 15 22:27:55 2022 DistUpgraded: 2022-08-02 14:36:41,704 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:2015] InstallationDate: Installed on 2022-02-17 (179 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 222a:0001 ILI Technology Corp. Multi-Touch Screen Bus 001 Device 002: ID 1a2c:2d23 China Resource Semico Co., Ltd Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Default string Default string ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=582fb3cc-8ef6-460b-b9ae-a16f81c604a7 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to jammy on 2022-08-02 (13 days ago) dmi.bios.date: 10/07/2021 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GSKU0504.V54 dmi.board.asset.tag: Default string dmi.board.name: SKYBAY dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGSKU0504.V54:bd10/07/2021:br5.12:svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnDefaultstring:rnSKYBAY:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: Default string dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Default string version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to:
Re: [Desktop-packages] [Bug 1986510] Re: No settings options for "Dock" under setting>>appearance
This solved the problem. Thank you On Thu, Aug 18, 2022 at 4:11 PM Jeremy Bicha <1986...@bugs.launchpad.net> wrote: > Please run this command in a terminal: > > sudo apt install ubuntu-desktop > > Then log out and log back in. > > ** Changed in: gnome-control-center (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1986510 > > Title: > No settings options for "Dock" under setting>>appearance > > Status in gnome-control-center package in Ubuntu: > Incomplete > > Bug description: > There are no options for customizing the Dock under > settings>>appearance. > > Even withe gnome-tweaks installed, the options don't show up. > > ProblemType: Bug > DistroRelease: Ubuntu 22.04 > Package: ubuntu-release-upgrader-core 1:22.04.13 > ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 > Uname: Linux 5.15.0-46-generic x86_64 > NonfreeKernelModules: wl nvidia_modeset nvidia > ApportVersion: 2.20.11-0ubuntu82.1 > Architecture: amd64 > CasperMD5CheckResult: unknown > CrashDB: ubuntu > CurrentDesktop: ubuntu:GNOME > Date: Mon Aug 15 11:01:15 2022 > InstallationDate: Installed on 2020-02-03 (924 days ago) > InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) > PackageArchitecture: all > SourcePackage: ubuntu-release-upgrader > Symptom: release-upgrade > UpgradeStatus: No upgrade log present (probably fresh install) > VarLogDistupgradeTermlog: > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1986510/+subscriptions > > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1986510 Title: No settings options for "Dock" under setting>>appearance Status in gnome-control-center package in Ubuntu: Incomplete Bug description: There are no options for customizing the Dock under settings>>appearance. Even withe gnome-tweaks installed, the options don't show up. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.13 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: wl nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Mon Aug 15 11:01:15 2022 InstallationDate: Installed on 2020-02-03 (924 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1986510/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1986583] Re: Screen after some time get shifted and starts to overlap
yeah, I added config to xorg.conf which contains this: Section "Device" Identifier "Card0" Driver "intel" BusID "PCI:0:2:0" Option "DRI" "3" Option "TearFree" "true" EndSection I have no deep understanding about how to switch drivers or how to use another one(which one?), but without this config, I had following problems: a) Option "DRI" "3" when this is not present it causes that strip of screen from time to time flicker - i would describe it like subset of pixels in some rectangle area are swapped to another color for a period of half seconds, and then it turns back to normal. It does not happen often but occasionally. b) "TearFree" "True" - without this when window is moved from up to bottom it is clearly seen that left part of screen is updated earlier then the right one. Is there a way to switch to another driver without losing this configuration? also in Wayland does not work x11vnc, and I did not found suitable replacement. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1986583 Title: Screen after some time get shifted and starts to overlap Status in xserver-xorg-video-intel package in Ubuntu: Incomplete Bug description: problem resembles a lot this one: https://askubuntu.com/questions/07/ubuntu-desktop-shifted-to-right "I am encountering a strange problem, my whole desktop has shifted to right." But different in a way, that when pc is started it shows everything just fine. But when computer is powered on a few days straight, display gets shifted. Some times just cca 1/4 of screen, sometimes it shifts over half of the screen. Computer should be used to run 8hours straight (it is intended for customer) When i switch from graphic display to tty (ctrl+alt+num) and back, display gets "restarted" and problem is fixed. But it is just temporary. Restart fixes it also. Last time i encountered this behavior today between 17-18hour. But have no idea what or where to look for. yes, and when one connects to display over X11 or teamviewer screen appears to be okay, so one will notice this problem if using pc remotely 1) lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 2) xorg: Installed: 1:7.7+23ubuntu2 Candidate: 1:7.7+23ubuntu2 Version table: *** 1:7.7+23ubuntu2 500 500 http://cz.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status 3) expect that display will stay where it is on the start of computer 4) display gets shifted to some distance from unknown reason (Maybe x11vnc or teamviewer usage or something). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Aug 15 22:27:55 2022 DistUpgraded: 2022-08-02 14:36:41,704 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:2015] InstallationDate: Installed on 2022-02-17 (179 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 222a:0001 ILI Technology Corp. Multi-Touch Screen Bus 001 Device 002: ID 1a2c:2d23 China Resource Semico Co., Ltd Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Default string Default string ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=582fb3cc-8ef6-460b-b9ae-a16f81c604a7 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to jammy on 2022-08-02 (13 days ago) dmi.bios.date: 10/07/2021 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GSKU0504.V54 dmi.board.asset.tag: Default string dmi.board.name: SKYBAY dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGSKU0504.V54:bd10/07/2021:br5.12:svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnDefaultstring:rnSKYBAY:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: Default string dmi.product.sku:
[Desktop-packages] [Bug 1986583] [NEW] Screen after some time get shifted and starts to overlap
Public bug reported: problem resembles a lot this one: https://askubuntu.com/questions/07/ubuntu-desktop-shifted-to-right "I am encountering a strange problem, my whole desktop has shifted to right." But different in a way, that when pc is started it shows everything just fine. But when computer is powered on a few days straight, display gets shifted. Some times just cca 1/4 of screen, sometimes it shifts over half of the screen. Computer should be used to run 8hours straight (it is intended for customer) When i switch from graphic display to tty (ctrl+alt+num) and back, display gets "restarted" and problem is fixed. But it is just temporary. Restart fixes it also. Last time i encountered this behavior today between 17-18hour. But have no idea what or where to look for. yes, and when one connects to display over X11 or teamviewer screen appears to be okay, so one will notice this problem if using pc remotely 1) lsb_release -rd Description:Ubuntu 22.04.1 LTS Release:22.04 2) xorg: Installed: 1:7.7+23ubuntu2 Candidate: 1:7.7+23ubuntu2 Version table: *** 1:7.7+23ubuntu2 500 500 http://cz.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status 3) expect that display will stay where it is on the start of computer 4) display gets shifted to some distance from unknown reason (Maybe x11vnc or teamviewer usage or something). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Aug 15 22:27:55 2022 DistUpgraded: 2022-08-02 14:36:41,704 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:2015] InstallationDate: Installed on 2022-02-17 (179 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 222a:0001 ILI Technology Corp. Multi-Touch Screen Bus 001 Device 002: ID 1a2c:2d23 China Resource Semico Co., Ltd Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Default string Default string ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=582fb3cc-8ef6-460b-b9ae-a16f81c604a7 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to jammy on 2022-08-02 (13 days ago) dmi.bios.date: 10/07/2021 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GSKU0504.V54 dmi.board.asset.tag: Default string dmi.board.name: SKYBAY dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGSKU0504.V54:bd10/07/2021:br5.12:svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnDefaultstring:rnSKYBAY:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: Default string dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Default string version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1986583 Title: Screen after some time get shifted and starts to overlap Status in xorg package in Ubuntu: New Bug description: problem resembles a lot this one: https://askubuntu.com/questions/07/ubuntu-desktop-shifted-to-right "I am encountering a strange problem, my whole desktop has shifted to right." But different in a way, that when pc is started it shows everything just fine. But when computer is powered on a few days straight, display gets shifted. Some times just cca 1/4 of screen,
[Desktop-packages] [Bug 1956369] Re: Asus GX701LV | ALC294 | Speakers don't work
** Summary changed: - The headphones work without problems, as does the microphone but there is no sound on the speakers + Asus GX701LV | ALC294 | Speakers don't work -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1956369 Title: Asus GX701LV | ALC294 | Speakers don't work Status in alsa-driver package in Ubuntu: New Bug description: I have a problem with my Asus GX701LWS, the headphones work without problems, as does the microphone but there is no sound on the speakers. hwinfo --sound 22: PCI 1f.3: 0403 Audio device [Created at pci.386] Unique ID: nS1_.Qb7ky1jjQRD SysFS ID: /devices/pci:00/:00:1f.3 SysFS BusID: :00:1f.3 Hardware Class: sound Model: "Intel Audio device" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x06c8 SubVendor: pci 0x1043 "ASUSTeK Computer Inc." SubDevice: pci 0x1f01 Driver: "snd_hda_intel" Driver Modules: "snd_hda_intel" Memory Range: 0x9830-0x98303fff (rw,non-prefetchable) Memory Range: 0x9810-0x981f (rw,non-prefetchable) IRQ: 171 (910 events) Module Alias: "pci:v8086d06C8sv1043sd1F01bc04sc03i80" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Driver Info #1: Driver Status: snd_sof_pci_intel_cnl is active Driver Activation Cmd: "modprobe snd_sof_pci_intel_cnl" Config Status: cfg=new, avail=yes, need=no, active=unknown17 aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC294 Analog [ALC294 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: NVidia [HDA NVidia], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: NVidia [HDA NVidia], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: NVidia [HDA NVidia], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: NVidia [HDA NVidia], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: NVidia [HDA NVidia], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: NVidia [HDA NVidia], device 11: HDMI 5 [HDMI 5] Subdevices: 1/1 Subdevice #0: subdevice #0 pacmd list-sinks 1 sink(s) available. * index: 0 name: driver: flags: HARDWARE HW_MUTE_CTRL HW_VOLUME_CTRL DECIBEL_VOLUME LATENCY DYNAMIC_LATENCY state: SUSPENDED suspend cause: IDLE priority: 9039 volume: front-left: 65536 / 100% / 0,00 dB, front-right: 65536 / 100% / 0,00 dB balance 0,00 base volume: 65536 / 100% / 0,00 dB volume steps: 65537 muted: no current latency: 0,00 ms max request: 0 KiB max rewind: 0 KiB monitor source: 0 sample spec: s16le 2ch 48000Hz channel map: front-left,front-right Stereo used by: 0 linked by: 0 configured latency: 0,00 ms; range is 0,50 .. 2000,00 ms card: 1 module: 8 properties: alsa.resolution_bits = "16" device.api = "alsa" device.class = "sound" alsa.class = "generic" alsa.subclass = "generic-mix" alsa.name = "ALC294 Analog" alsa.id = "ALC294 Analog" alsa.subdevice = "0" alsa.subdevice_name = "subdevice #0" alsa.device = "0" alsa.card = "0" alsa.card_name = "HDA Intel PCH" alsa.long_card_name = "HDA Intel PCH at 0x9830 irq 171" alsa.driver_name = "snd_hda_intel" device.bus_path = "pci-:00:1f.3" sysfs.path = "/devices/pci:00/:00:1f.3/sound/card0" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "06c8" device.form_factor = "internal" device.string = "front:0" device.buffering.buffer_size = "384000" device.buffering.fragment_size = "192000" device.access_mode = "mmap+timer" device.profile.name = "analog-stereo" device.profile.description = "Analog Stereo" device.description = "Built-in Audio Analog Stereo" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" ports: analog-output-speaker: Speakers (priority 1, latency offset 0 usec, available: unknown) properties: device.icon_name = "audio-speakers" analog-output-headphones: Headphones (priority 9900, latency offset 0 usec, available: no) properties: device.icon_name = "audio-headphones" active port: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1956369/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1970043] Re: [amdgpu] freeze occurs when wayland is connected to a second monitor
Comment #30 saved my day! I started to be affected by this bug just today, everything fine until now. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1970043 Title: [amdgpu] freeze occurs when wayland is connected to a second monitor Status in gnome-shell package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Confirmed Bug description: I didn't encounter this bug with ubuntu 21.10 and when I tried to use x11 in 22.04 everything was fine, so it seems to be related to mutter42. And my computer is an amd 47 4800u machine and should only have one integrated graphics card ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Apr 24 00:38:15 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-04-23 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-04-26 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Package: mutter PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: mutter-common 42.0-3ubuntu2 Tags: jammy wayland-session Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1970043/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972889] Re: Screen reader reads the data while computer is locked
Also, I want to make sure that we did not miss this part: Opened browser is Brave. It's a chromium-based browser, and then I would lock a computer, with this, pressing Alt+Super+S would start reading chromium interface. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1972889 Title: Screen reader reads the data while computer is locked Status in gnome-shell package in Ubuntu: Incomplete Bug description: # lsb_release -rd Description: Ubuntu 22.04 LTS Release: 22.04 # apt-cache policy gnome-shell gnome-shell: Installed: 42.0-2ubuntu1 Candidate: 42.0-2ubuntu1 Version table: *** 42.0-2ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status Ubuntu is installed on a laptop. Within five minutes of inactivity, the screen lock activates and locks the system. Computer is secured. 10 minutes later, my cat (her name is Loaf) comes up to the laptop and sits down on the keyboard. This activates a screen reader. (Shortcut is Alt + Super + S) What I've expected: Screen reader would start reading the contents of a lock screen What happened: Screen reader app started reading contents of a Brave Browser window that was opened on my desktop. It read all tabs and proceeded reading the opened web page. I've reported this bug at secur...@ubuntu.org and got the following answer: > Nice find - I am able to reproduce this locally in Ubuntu 22.04 LTS too > - I suspect this is a vulnerability in gnome-shell as it is > responsible for handling the lock screen in standard Ubuntu. As per further directions, I'm posting this bug here and in gnome repo. P.S. I expect Loaf being credited for this find. She really likes treats. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-10-24 (201 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Package: gnome-shell 42.0-2ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: mutter-common 42.0-3ubuntu2 Tags: wayland-session jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-28 (15 days ago) UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1972889/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972889] ShellJournal.txt
apport information ** Attachment added: "ShellJournal.txt" https://bugs.launchpad.net/bugs/1972889/+attachment/5589688/+files/ShellJournal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1972889 Title: Screen reader reads the data while computer is locked Status in gnome-shell package in Ubuntu: Incomplete Bug description: # lsb_release -rd Description: Ubuntu 22.04 LTS Release: 22.04 # apt-cache policy gnome-shell gnome-shell: Installed: 42.0-2ubuntu1 Candidate: 42.0-2ubuntu1 Version table: *** 42.0-2ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status Ubuntu is installed on a laptop. Within five minutes of inactivity, the screen lock activates and locks the system. Computer is secured. 10 minutes later, my cat (her name is Loaf) comes up to the laptop and sits down on the keyboard. This activates a screen reader. (Shortcut is Alt + Super + S) What I've expected: Screen reader would start reading the contents of a lock screen What happened: Screen reader app started reading contents of a Brave Browser window that was opened on my desktop. It read all tabs and proceeded reading the opened web page. I've reported this bug at secur...@ubuntu.org and got the following answer: > Nice find - I am able to reproduce this locally in Ubuntu 22.04 LTS too > - I suspect this is a vulnerability in gnome-shell as it is > responsible for handling the lock screen in standard Ubuntu. As per further directions, I'm posting this bug here and in gnome repo. P.S. I expect Loaf being credited for this find. She really likes treats. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-10-24 (201 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Package: gnome-shell 42.0-2ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: mutter-common 42.0-3ubuntu2 Tags: wayland-session jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-28 (15 days ago) UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1972889/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972889] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/1972889/+attachment/5589686/+files/GsettingsChanges.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1972889 Title: Screen reader reads the data while computer is locked Status in gnome-shell package in Ubuntu: Incomplete Bug description: # lsb_release -rd Description: Ubuntu 22.04 LTS Release: 22.04 # apt-cache policy gnome-shell gnome-shell: Installed: 42.0-2ubuntu1 Candidate: 42.0-2ubuntu1 Version table: *** 42.0-2ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status Ubuntu is installed on a laptop. Within five minutes of inactivity, the screen lock activates and locks the system. Computer is secured. 10 minutes later, my cat (her name is Loaf) comes up to the laptop and sits down on the keyboard. This activates a screen reader. (Shortcut is Alt + Super + S) What I've expected: Screen reader would start reading the contents of a lock screen What happened: Screen reader app started reading contents of a Brave Browser window that was opened on my desktop. It read all tabs and proceeded reading the opened web page. I've reported this bug at secur...@ubuntu.org and got the following answer: > Nice find - I am able to reproduce this locally in Ubuntu 22.04 LTS too > - I suspect this is a vulnerability in gnome-shell as it is > responsible for handling the lock screen in standard Ubuntu. As per further directions, I'm posting this bug here and in gnome repo. P.S. I expect Loaf being credited for this find. She really likes treats. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-10-24 (201 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Package: gnome-shell 42.0-2ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: mutter-common 42.0-3ubuntu2 Tags: wayland-session jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-28 (15 days ago) UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1972889/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972889] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1972889/+attachment/5589687/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1972889 Title: Screen reader reads the data while computer is locked Status in gnome-shell package in Ubuntu: Incomplete Bug description: # lsb_release -rd Description: Ubuntu 22.04 LTS Release: 22.04 # apt-cache policy gnome-shell gnome-shell: Installed: 42.0-2ubuntu1 Candidate: 42.0-2ubuntu1 Version table: *** 42.0-2ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status Ubuntu is installed on a laptop. Within five minutes of inactivity, the screen lock activates and locks the system. Computer is secured. 10 minutes later, my cat (her name is Loaf) comes up to the laptop and sits down on the keyboard. This activates a screen reader. (Shortcut is Alt + Super + S) What I've expected: Screen reader would start reading the contents of a lock screen What happened: Screen reader app started reading contents of a Brave Browser window that was opened on my desktop. It read all tabs and proceeded reading the opened web page. I've reported this bug at secur...@ubuntu.org and got the following answer: > Nice find - I am able to reproduce this locally in Ubuntu 22.04 LTS too > - I suspect this is a vulnerability in gnome-shell as it is > responsible for handling the lock screen in standard Ubuntu. As per further directions, I'm posting this bug here and in gnome repo. P.S. I expect Loaf being credited for this find. She really likes treats. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-10-24 (201 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Package: gnome-shell 42.0-2ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: mutter-common 42.0-3ubuntu2 Tags: wayland-session jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-28 (15 days ago) UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1972889/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972889] monitors.xml.txt
apport information ** Attachment added: "monitors.xml.txt" https://bugs.launchpad.net/bugs/1972889/+attachment/5589689/+files/monitors.xml.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1972889 Title: Screen reader reads the data while computer is locked Status in gnome-shell package in Ubuntu: Incomplete Bug description: # lsb_release -rd Description: Ubuntu 22.04 LTS Release: 22.04 # apt-cache policy gnome-shell gnome-shell: Installed: 42.0-2ubuntu1 Candidate: 42.0-2ubuntu1 Version table: *** 42.0-2ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status Ubuntu is installed on a laptop. Within five minutes of inactivity, the screen lock activates and locks the system. Computer is secured. 10 minutes later, my cat (her name is Loaf) comes up to the laptop and sits down on the keyboard. This activates a screen reader. (Shortcut is Alt + Super + S) What I've expected: Screen reader would start reading the contents of a lock screen What happened: Screen reader app started reading contents of a Brave Browser window that was opened on my desktop. It read all tabs and proceeded reading the opened web page. I've reported this bug at secur...@ubuntu.org and got the following answer: > Nice find - I am able to reproduce this locally in Ubuntu 22.04 LTS too > - I suspect this is a vulnerability in gnome-shell as it is > responsible for handling the lock screen in standard Ubuntu. As per further directions, I'm posting this bug here and in gnome repo. P.S. I expect Loaf being credited for this find. She really likes treats. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-10-24 (201 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Package: gnome-shell 42.0-2ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: mutter-common 42.0-3ubuntu2 Tags: wayland-session jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-28 (15 days ago) UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1972889/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972889] Re: Screen reader reads the data while computer is locked
apport information ** Tags added: apport-collected wayland-session ** Description changed: # lsb_release -rd Description: Ubuntu 22.04 LTS Release: 22.04 # apt-cache policy gnome-shell gnome-shell: Installed: 42.0-2ubuntu1 Candidate: 42.0-2ubuntu1 Version table: *** 42.0-2ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status Ubuntu is installed on a laptop. Within five minutes of inactivity, the screen lock activates and locks the system. Computer is secured. 10 minutes later, my cat (her name is Loaf) comes up to the laptop and sits down on the keyboard. This activates a screen reader. (Shortcut is Alt + Super + S) What I've expected: Screen reader would start reading the contents of a lock screen What happened: Screen reader app started reading contents of a Brave Browser window that was opened on my desktop. It read all tabs and proceeded reading the opened web page. I've reported this bug at secur...@ubuntu.org and got the following answer: > Nice find - I am able to reproduce this locally in Ubuntu 22.04 LTS too > - I suspect this is a vulnerability in gnome-shell as it is > responsible for handling the lock screen in standard Ubuntu. As per further directions, I'm posting this bug here and in gnome repo. P.S. I expect Loaf being credited for this find. She really likes treats. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu82 + Architecture: amd64 + CasperMD5CheckResult: pass + CurrentDesktop: ubuntu:GNOME + DisplayManager: gdm3 + DistroRelease: Ubuntu 22.04 + InstallationDate: Installed on 2021-10-24 (201 days ago) + InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) + Package: gnome-shell 42.0-2ubuntu1 + PackageArchitecture: amd64 + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/usr/bin/zsh + ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 + RelatedPackageVersions: mutter-common 42.0-3ubuntu2 + Tags: wayland-session jammy + Uname: Linux 5.15.0-27-generic x86_64 + UpgradeStatus: Upgraded to jammy on 2022-04-28 (15 days ago) + UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1972889/+attachment/5589685/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1972889 Title: Screen reader reads the data while computer is locked Status in gnome-shell package in Ubuntu: Incomplete Bug description: # lsb_release -rd Description: Ubuntu 22.04 LTS Release: 22.04 # apt-cache policy gnome-shell gnome-shell: Installed: 42.0-2ubuntu1 Candidate: 42.0-2ubuntu1 Version table: *** 42.0-2ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status Ubuntu is installed on a laptop. Within five minutes of inactivity, the screen lock activates and locks the system. Computer is secured. 10 minutes later, my cat (her name is Loaf) comes up to the laptop and sits down on the keyboard. This activates a screen reader. (Shortcut is Alt + Super + S) What I've expected: Screen reader would start reading the contents of a lock screen What happened: Screen reader app started reading contents of a Brave Browser window that was opened on my desktop. It read all tabs and proceeded reading the opened web page. I've reported this bug at secur...@ubuntu.org and got the following answer: > Nice find - I am able to reproduce this locally in Ubuntu 22.04 LTS too > - I suspect this is a vulnerability in gnome-shell as it is > responsible for handling the lock screen in standard Ubuntu. As per further directions, I'm posting this bug here and in gnome repo. P.S. I expect Loaf being credited for this find. She really likes treats. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-10-24 (201 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Package: gnome-shell 42.0-2ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: mutter-common 42.0-3ubuntu2 Tags: wayland-session jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-28 (15 days ago) UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
[Desktop-packages] [Bug 1964541] Re: Cannot use Drag and Drop in gnome-shell 42 (Wayland session)
> I hope we get back to Firefox with Wayland enabled soon because the performance difference was noticeable last time I checked. Plus, rendering of the entire Firefox window got blurry with fractional scaling. (Just to add one more reason :-) ) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1964541 Title: Cannot use Drag and Drop in gnome-shell 42 (Wayland session) Status in Mozilla Firefox: New Status in Mutter: Unknown Status in firefox package in Ubuntu: Invalid Status in mutter package in Ubuntu: Fix Released Bug description: Since 42~beta-1ubuntu1, and still present in 42~beta-1ubuntu2, attempting to re-arrange tabs in Firefox fails. Click and drag the tab and release, nothing changes. The next click to the tab is ignored. syslog has the following: Mar 11 13:06:47 desktop firefox[2192]: Attempting to add a widget with type GtkWindow to a container of type GtkWindow, but the widget is already inside a container of type GtkWindow, please remove the widget from its existing container first. Mar 11 13:06:48 desktop firefox[2192]: Attempting to add a widget with type GtkWindow to a container of type GtkWindow, but the widget is already inside a container of type GtkWindow, please remove the widget from its existing container first. Mar 11 13:06:50 desktop firefox[2192]: Attempting to add a widget with type GtkWindow to a container of type GtkWindow, but the widget is already inside a container of type GtkWindow, please remove the widget from its existing container first. Mar 11 13:06:51 desktop firefox[2192]: Attempting to add a widget with type GtkWindow to a container of type GtkWindow, but the widget is already inside a container of type GtkWindow, please remove the widget from its existing container first. gnome-shell 42~beta-1ubuntu2 Firefox Snap 98.0-3 (1073) A similar behavior can also be observed in gedit, nautilus and other GNOME applications whether they are confined or not (while snapped ones seems to underline the issue more) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1964541/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965535] Re: Stop recommending snap
> Judging by the size of this other thread [1], I'd venture many other users feel equally about this. Indeed. Just so that we are clear about the importance of this: At present, the bug linked to by @guiambros, which triggered opening this bug in ubuntu-meta as well, is the 3rd highest by heat *for all bugs recorded in launchpad in all ubuntu packages*: https://bugs.launchpad.net/ubuntu/+bugs?orderby=-heat=0 I think that says something. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1965535 Title: Stop recommending snap Status in ubuntu-meta package in Ubuntu: Opinion Bug description: Currently, ubuntu recommends installing snap by default, and some apps are slowly transitioning from DEB-based installation to Snap-based installation. APT is great, and facilitates having a clean, maintainable system. The snap project is not very well designed or engineered (just changing the location of where snap data is located is taking the project more than 5 years because it was hardcoded: https://bugs.launchpad.net/snapd/+bug/1575053). Snaps are large and VERY slow. The design of snap, as well as the way that decisions are made, are very questionable, and are receiving increasing amounts of criticism. I'd like to request that Ubuntu stops recommending snap, stops transitioning towards snaps, and we come back to defaulting to DEB/APT-based installation for all apps. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1965535/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965535] Re: Stop recommending snap
So far, 12 people have already indicated that this bug affects them (several giving more detailed descriptions). This bug is now in the top 5 of open bugs with most heat for ubuntu-meta. Given that others are affected, would it be reasonable to set the status to Confirmed so it is given further consideration? EDIT: simplify text -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1965535 Title: Stop recommending snap Status in ubuntu-meta package in Ubuntu: Opinion Bug description: Currently, ubuntu recommends installing snap by default, and some apps are slowly transitioning from DEB-based installation to Snap-based installation. APT is great, and facilitates having a clean, maintainable system. The snap project is not very well designed or engineered (just changing the location of where snap data is located is taking the project more than 5 years because it was hardcoded: https://bugs.launchpad.net/snapd/+bug/1575053). Snaps are large and VERY slow. The design of snap, as well as the way that decisions are made, are very questionable, and are receiving increasing amounts of criticism. I'd like to request that Ubuntu stops recommending snap, stops transitioning towards snaps, and we come back to defaulting to DEB/APT-based installation for all apps. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1965535/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965535] Re: Stop recommending snap
** Description changed: Currently, ubuntu recommends installing snap by default, and some apps are slowly transitioning from DEB-based installation to Snap-based installation. APT is great, and facilitates having a clean, maintainable system. - The snap project is not very well designed or engineered (just changing the location of where snap data is located is taking the project more than 5 years because it was hardcoded: https://bugs.launchpad.net/snapd/+bug/1575053). Snaps are large and VERY slow. The design of snap, as well as the way decisions are made, are very questionable, and are receiving - increasing amounts of criticism. + The snap project is not very well designed or engineered (just changing + the location of where snap data is located is taking the project more + than 5 years because it was hardcoded: + https://bugs.launchpad.net/snapd/+bug/1575053). Snaps are large and VERY + slow. The design of snap, as well as the way that decisions are made, + are very questionable, and are receiving increasing amounts of + criticism. I'd like to request that Ubuntu stops recommending snap, stops transitioning towards snaps, and we come back to defaulting to DEB/APT- based installation for all apps. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1965535 Title: Stop recommending snap Status in ubuntu-meta package in Ubuntu: Opinion Bug description: Currently, ubuntu recommends installing snap by default, and some apps are slowly transitioning from DEB-based installation to Snap-based installation. APT is great, and facilitates having a clean, maintainable system. The snap project is not very well designed or engineered (just changing the location of where snap data is located is taking the project more than 5 years because it was hardcoded: https://bugs.launchpad.net/snapd/+bug/1575053). Snaps are large and VERY slow. The design of snap, as well as the way that decisions are made, are very questionable, and are receiving increasing amounts of criticism. I'd like to request that Ubuntu stops recommending snap, stops transitioning towards snaps, and we come back to defaulting to DEB/APT-based installation for all apps. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1965535/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965535] Re: Stop recommending snap
** Description changed: Currently, ubuntu recommends installing snap by default, and some apps are slowly transitioning from DEB-based installation to Snap-based installation. APT is great, and facilitates having a clean, maintainable system. - The snap project is not very well designed or engineered (just changing - the location of where snap data is located is taking the project more - than 5 years because it was hardcoded: - https://bugs.launchpad.net/snapd/+bug/1575053). The design of snap, and - many decisions made in the project that impact users, are very - questionable, and snaps are large and VERY slow. + The snap project is not very well designed or engineered (just changing the location of where snap data is located is taking the project more than 5 years because it was hardcoded: https://bugs.launchpad.net/snapd/+bug/1575053). Snaps are large and VERY slow. The design of snap, as well as the way decisions are made, are very questionable, and are receiving + increasing amounts of criticism. I'd like to request that Ubuntu stops recommending snap, stops transitioning towards snaps, and we come back to defaulting to DEB/APT- based installation for all apps. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1965535 Title: Stop recommending snap Status in ubuntu-meta package in Ubuntu: New Bug description: Currently, ubuntu recommends installing snap by default, and some apps are slowly transitioning from DEB-based installation to Snap-based installation. APT is great, and facilitates having a clean, maintainable system. The snap project is not very well designed or engineered (just changing the location of where snap data is located is taking the project more than 5 years because it was hardcoded: https://bugs.launchpad.net/snapd/+bug/1575053). Snaps are large and VERY slow. The design of snap, as well as the way decisions are made, are very questionable, and are receiving increasing amounts of criticism. I'd like to request that Ubuntu stops recommending snap, stops transitioning towards snaps, and we come back to defaulting to DEB/APT-based installation for all apps. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1965535/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965535] [NEW] Stop recommending snap
Public bug reported: Currently, ubuntu recommends installing snap by default, and some apps are slowly transitioning from DEB-based installation to Snap-based installation. APT is great, and facilitates having a clean, maintainable system. The snap project is not very well designed or engineered (just changing the location of where snap data is located is taking the project more than 5 years because it was hardcoded: https://bugs.launchpad.net/snapd/+bug/1575053). The design of snap, and many decisions made in the project that impact users, are very questionable, and snaps are large and VERY slow. I'd like to request that Ubuntu stops recommending snap, stops transitioning towards snaps, and we come back to defaulting to DEB/APT- based installation for all apps. ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1965535 Title: Stop recommending snap Status in ubuntu-meta package in Ubuntu: New Bug description: Currently, ubuntu recommends installing snap by default, and some apps are slowly transitioning from DEB-based installation to Snap-based installation. APT is great, and facilitates having a clean, maintainable system. The snap project is not very well designed or engineered (just changing the location of where snap data is located is taking the project more than 5 years because it was hardcoded: https://bugs.launchpad.net/snapd/+bug/1575053). The design of snap, and many decisions made in the project that impact users, are very questionable, and snaps are large and VERY slow. I'd like to request that Ubuntu stops recommending snap, stops transitioning towards snaps, and we come back to defaulting to DEB/APT-based installation for all apps. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1965535/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1956369] [NEW] The headphones work without problems, as does the microphone but there is no sound on the speakers
Public bug reported: I have a problem with my Asus GX701LWS, the headphones work without problems, as does the microphone but there is no sound on the speakers. hwinfo --sound 22: PCI 1f.3: 0403 Audio device [Created at pci.386] Unique ID: nS1_.Qb7ky1jjQRD SysFS ID: /devices/pci:00/:00:1f.3 SysFS BusID: :00:1f.3 Hardware Class: sound Model: "Intel Audio device" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x06c8 SubVendor: pci 0x1043 "ASUSTeK Computer Inc." SubDevice: pci 0x1f01 Driver: "snd_hda_intel" Driver Modules: "snd_hda_intel" Memory Range: 0x9830-0x98303fff (rw,non-prefetchable) Memory Range: 0x9810-0x981f (rw,non-prefetchable) IRQ: 171 (910 events) Module Alias: "pci:v8086d06C8sv1043sd1F01bc04sc03i80" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Driver Info #1: Driver Status: snd_sof_pci_intel_cnl is active Driver Activation Cmd: "modprobe snd_sof_pci_intel_cnl" Config Status: cfg=new, avail=yes, need=no, active=unknown17 aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC294 Analog [ALC294 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: NVidia [HDA NVidia], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: NVidia [HDA NVidia], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: NVidia [HDA NVidia], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: NVidia [HDA NVidia], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: NVidia [HDA NVidia], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: NVidia [HDA NVidia], device 11: HDMI 5 [HDMI 5] Subdevices: 1/1 Subdevice #0: subdevice #0 pacmd list-sinks 1 sink(s) available. * index: 0 name: driver: flags: HARDWARE HW_MUTE_CTRL HW_VOLUME_CTRL DECIBEL_VOLUME LATENCY DYNAMIC_LATENCY state: SUSPENDED suspend cause: IDLE priority: 9039 volume: front-left: 65536 / 100% / 0,00 dB, front-right: 65536 / 100% / 0,00 dB balance 0,00 base volume: 65536 / 100% / 0,00 dB volume steps: 65537 muted: no current latency: 0,00 ms max request: 0 KiB max rewind: 0 KiB monitor source: 0 sample spec: s16le 2ch 48000Hz channel map: front-left,front-right Stereo used by: 0 linked by: 0 configured latency: 0,00 ms; range is 0,50 .. 2000,00 ms card: 1 module: 8 properties: alsa.resolution_bits = "16" device.api = "alsa" device.class = "sound" alsa.class = "generic" alsa.subclass = "generic-mix" alsa.name = "ALC294 Analog" alsa.id = "ALC294 Analog" alsa.subdevice = "0" alsa.subdevice_name = "subdevice #0" alsa.device = "0" alsa.card = "0" alsa.card_name = "HDA Intel PCH" alsa.long_card_name = "HDA Intel PCH at 0x9830 irq 171" alsa.driver_name = "snd_hda_intel" device.bus_path = "pci-:00:1f.3" sysfs.path = "/devices/pci:00/:00:1f.3/sound/card0" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "06c8" device.form_factor = "internal" device.string = "front:0" device.buffering.buffer_size = "384000" device.buffering.fragment_size = "192000" device.access_mode = "mmap+timer" device.profile.name = "analog-stereo" device.profile.description = "Analog Stereo" device.description = "Built-in Audio Analog Stereo" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" ports: analog-output-speaker: Speakers (priority 1, latency offset 0 usec, available: unknown) properties: device.icon_name = "audio-speakers" analog-output-headphones: Headphones (priority 9900, latency offset 0 usec, available: no) properties: device.icon_name = "audio-headphones" active port: ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: alc294 asus gx701 sound -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1956369 Title: The headphones work without problems, as does the microphone but there is no sound on the speakers Status in alsa-driver package in Ubuntu: New Bug description: I have a problem with my Asus GX701LWS, the headphones work without problems, as does the microphone but there is no sound on the speakers. hwinfo --sound 22: PCI 1f.3: 0403 Audio device [Created at pci.386] Unique ID: nS1_.Qb7ky1jjQRD SysFS ID: /devices/pci:00/:00:1f.3 SysFS BusID: :00:1f.3 Hardware Class: sound Model: "Intel Audio device" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x06c8 SubVendor: pci 0x1043 "ASUSTeK Computer Inc." SubDevice: pci 0x1f01 Driver: "snd_hda_intel" Driver Modules: "snd_hda_intel" Memory Range: 0x9830-0x98303fff (rw,non-prefetchable) Memory Range:
[Desktop-packages] [Bug 1038479] Re: [Satellite L755, Conexant CX20585, Speaker, Internal] fails after a while
It doesn't work for my Asus gx701lws. The headphones work without problems, as does the microphone but there is no sound on the speakers. hwinfo --sound 22: PCI 1f.3: 0403 Audio device [Created at pci.386] Unique ID: nS1_.Qb7ky1jjQRD SysFS ID: /devices/pci:00/:00:1f.3 SysFS BusID: :00:1f.3 Hardware Class: sound Model: "Intel Audio device" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x06c8 SubVendor: pci 0x1043 "ASUSTeK Computer Inc." SubDevice: pci 0x1f01 Driver: "snd_hda_intel" Driver Modules: "snd_hda_intel" Memory Range: 0x9830-0x98303fff (rw,non-prefetchable) Memory Range: 0x9810-0x981f (rw,non-prefetchable) IRQ: 171 (910 events) Module Alias: "pci:v8086d06C8sv1043sd1F01bc04sc03i80" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Driver Info #1: Driver Status: snd_sof_pci_intel_cnl is active Driver Activation Cmd: "modprobe snd_sof_pci_intel_cnl" Config Status: cfg=new, avail=yes, need=no, active=unknown17 aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC294 Analog [ALC294 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: NVidia [HDA NVidia], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: NVidia [HDA NVidia], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: NVidia [HDA NVidia], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: NVidia [HDA NVidia], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: NVidia [HDA NVidia], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: NVidia [HDA NVidia], device 11: HDMI 5 [HDMI 5] Subdevices: 1/1 Subdevice #0: subdevice #0 pacmd list-sinks 1 sink(s) available. * index: 0 name: driver: flags: HARDWARE HW_MUTE_CTRL HW_VOLUME_CTRL DECIBEL_VOLUME LATENCY DYNAMIC_LATENCY state: SUSPENDED suspend cause: IDLE priority: 9039 volume: front-left: 65536 / 100% / 0,00 dB, front-right: 65536 / 100% / 0,00 dB balance 0,00 base volume: 65536 / 100% / 0,00 dB volume steps: 65537 muted: no current latency: 0,00 ms max request: 0 KiB max rewind: 0 KiB monitor source: 0 sample spec: s16le 2ch 48000Hz channel map: front-left,front-right Stereo used by: 0 linked by: 0 configured latency: 0,00 ms; range is 0,50 .. 2000,00 ms card: 1 module: 8 properties: alsa.resolution_bits = "16" device.api = "alsa" device.class = "sound" alsa.class = "generic" alsa.subclass = "generic-mix" alsa.name = "ALC294 Analog" alsa.id = "ALC294 Analog" alsa.subdevice = "0" alsa.subdevice_name = "subdevice #0" alsa.device = "0" alsa.card = "0" alsa.card_name = "HDA Intel PCH" alsa.long_card_name = "HDA Intel PCH at 0x9830 irq 171" alsa.driver_name = "snd_hda_intel" device.bus_path = "pci-:00:1f.3" sysfs.path = "/devices/pci:00/:00:1f.3/sound/card0" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "06c8" device.form_factor = "internal" device.string = "front:0" device.buffering.buffer_size = "384000" device.buffering.fragment_size = "192000" device.access_mode = "mmap+timer" device.profile.name = "analog-stereo" device.profile.description = "Analog Stereo" device.description = "Built-in Audio Analog Stereo" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" ports: analog-output-speaker: Speakers (priority 1, latency offset 0 usec, available: unknown) properties: device.icon_name = "audio-speakers" analog-output-headphones: Headphones (priority 9900, latency offset 0 usec, available: no) properties: device.icon_name = "audio-headphones" active port: -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1038479 Title: [Satellite L755, Conexant CX20585, Speaker, Internal] fails after a while Status in alsa-driver package in Ubuntu: Confirmed Bug description: Restart will fix the issue, but sound always quits from internal
[Desktop-packages] [Bug 1628707] Re: Highlighting a region in emacs is invisible because region color equals window color
I experience this or a similar problem with emacs-26 on Ubuntu 20.04 (the standard Gnome DE). Somehow having the "region" face set to having gtk_selection_bg_color makes the selected region not noticeable (or hardly noticeable?..). I have delete-selection-mode enabled. After changing it, it is OK; to yellow in my case: (custom-set-faces ;; custom-set-faces was added by Custom. ;; If you edit it by hand, you could mess it up, so be careful. ;; Your init file should contain only one such instance. ;; If there is more than one, they won't work right. '(region ((t (:background "yellow" :distant-foreground "gtk_selection_fg_color") I wonder why the selection in Firefox is noticeable and has the standard orange-brown color whereas Emacs doesn't get it. ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Oct 6 20:08:01 2021 Dependencies: adduser 3.118ubuntu2 adwaita-icon-theme 3.36.1-2ubuntu0.20.04.2 alsa-topology-conf 1.2.2-1 alsa-ucm-conf 1.2.2-1ubuntu0.10 apt 2.0.6 apt-utils 2.0.6 at-spi2-core 2.36.0-2 ca-certificates 20210119~20.04.2 coreutils 8.30-3ubuntu2 dbus 1.12.16-2ubuntu2.1 dconf-gsettings-backend 0.36.0-1 dconf-service 0.36.0-1 debconf 1.5.73 debconf-i18n 1.5.73 dpkg 1.19.7ubuntu3 emacs-bin-common 1:26.3+1-1ubuntu2 emacs-common 1:26.3+1-1ubuntu2 emacs-el 1:26.3+1-1ubuntu2 emacs-gtk 1:26.3+1-1ubuntu2 emacsen-common 3.0.4 fontconfig 2.13.1-2ubuntu3 fontconfig-config 2.13.1-2ubuntu3 fonts-dejavu-core 2.37-1 fonts-droid-fallback 1:6.0.1r16-1.1 fonts-noto-mono 20200323-1build1~ubuntu20.04.1 fonts-urw-base35 20170801.1-3 gcc-10-base 10.3.0-1ubuntu1~20.04 ghostscript 9.50~dfsg-5ubuntu4.3 glib-networking 2.64.2-1ubuntu0.1 glib-networking-common 2.64.2-1ubuntu0.1 glib-networking-services 2.64.2-1ubuntu0.1 gpgv 2.2.19-3ubuntu2.1 gsettings-desktop-schemas 3.36.0-1ubuntu1 gsfonts 1:8.11+urwcyr1.0.7~pre44-4.4 gtk-update-icon-cache 3.24.20-0ubuntu1 hicolor-icon-theme 0.17-2 humanity-icon-theme 0.6.15 imagemagick-6-common 8:6.9.10.23+dfsg-2.1ubuntu11.4 install-info 6.7.0.dfsg.2-5 krb5-locales 1.17-6ubuntu4.1 libacl1 2.2.53-6 libapparmor1 2.13.3-7ubuntu5.1 libapt-pkg6.0 2.0.6 libasound2 1.2.2-2.1ubuntu2.4 libasound2-data 1.2.2-2.1ubuntu2.4 libatk-bridge2.0-0 2.34.2-0ubuntu2~20.04.1 libatk1.0-0 2.35.1-1ubuntu2 libatk1.0-data 2.35.1-1ubuntu2 libatspi2.0-0 2.36.0-2 libattr1 1:2.4.48-5 libaudit-common 1:2.8.5-2ubuntu6 libaudit1 1:2.8.5-2ubuntu6 libavahi-client3 0.7-4ubuntu7.1 libavahi-common-data 0.7-4ubuntu7.1 libavahi-common3 0.7-4ubuntu7.1 libblkid1 2.34-0.1ubuntu9.1 libbrotli1 1.0.7-6ubuntu0.1 libbsd0 0.10.0-1 libbz2-1.0 1.0.8-2 libc6 2.31-0ubuntu9.2 libcairo-gobject2 1.16.0-4ubuntu1 libcairo2 1.16.0-4ubuntu1 libcap-ng0 0.7.9-2.1build1 libcolord2 1.4.4-2 libcom-err2 1.45.5-2ubuntu1 libcrypt1 1:4.4.10-10ubuntu4 libcups2 2.3.1-9ubuntu1.1 libdatrie1 0.2.12-3 libdb5.3 5.3.28+dfsg1-0.6ubuntu2 libdbus-1-3 1.12.16-2ubuntu2.1 libdconf1 0.36.0-1 libepoxy0 1.5.4-1 libexpat1 2.2.9-1build1 libffi7 3.3-4 libfftw3-double3 3.3.8-2ubuntu1 libfontconfig1 2.13.1-2ubuntu3 libfreetype6 2.10.1-2ubuntu0.1 libfribidi0 1.0.8-2 libgcc-s1 10.3.0-1ubuntu1~20.04 libgcrypt20 1.8.5-5ubuntu1.1 libgd3 2.2.5-5.2ubuntu2.1 libgdk-pixbuf2.0-0 2.40.0+dfsg-3ubuntu0.2 libgdk-pixbuf2.0-bin 2.40.0+dfsg-3ubuntu0.2 libgdk-pixbuf2.0-common 2.40.0+dfsg-3ubuntu0.2 libgif7 5.1.9-1 libglib2.0-0 2.64.6-1~ubuntu20.04.4 libglib2.0-data 2.64.6-1~ubuntu20.04.4 libgmp10 2:6.2.0+dfsg-4 libgnutls30 3.6.13-2ubuntu1.6 libgomp1 10.3.0-1ubuntu1~20.04 libgpg-error0 1.37-1 libgpm2 1.20.7-5 libgraphite2-3 1.3.13-11build1 libgs9 9.50~dfsg-5ubuntu4.3 libgs9-common 9.50~dfsg-5ubuntu4.3 libgssapi-krb5-2 1.17-6ubuntu4.1 libgtk-3-0 3.24.20-0ubuntu1 libgtk-3-bin 3.24.20-0ubuntu1 libgtk-3-common 3.24.20-0ubuntu1 libharfbuzz0b 2.6.4-1ubuntu4 libhogweed5 3.5.1+really3.5.1-2ubuntu0.2 libice6 2:1.0.10-0ubuntu1 libicu66 66.1-2ubuntu2 libidn11 1.33-2.2ubuntu2 libidn2-0 2.2.0-2 libijs-0.35 0.35-15 libjbig0 2.1-3.1build1 libjbig2dec0 0.18-1ubuntu1 libjpeg-turbo8 2.0.3-0ubuntu1.20.04.1 libjpeg8 8c-2ubuntu8 libjson-glib-1.0-0 1.4.4-2ubuntu2 libjson-glib-1.0-common 1.4.4-2ubuntu2 libk5crypto3 1.17-6ubuntu4.1 libkeyutils1 1.6-6ubuntu1 libkrb5-3 1.17-6ubuntu4.1 libkrb5support0 1.17-6ubuntu4.1 liblcms2-2 2.9-4 liblocale-gettext-perl 1.07-4 liblqr-1-0 0.4.2-2.1 libltdl7 2.4.6-14 liblz4-1 1.9.2-2ubuntu0.20.04.1 liblzma5 5.2.4-1ubuntu1 libm17n-0 1.8.0-2 libmagickcore-6.q16-6 8:6.9.10.23+dfsg-2.1ubuntu11.4 libmagickwand-6.q16-6 8:6.9.10.23+dfsg-2.1ubuntu11.4 libmount1 2.34-0.1ubuntu9.1 libnettle7 3.5.1+really3.5.1-2ubuntu0.2 libopenjp2-7 2.3.1-1ubuntu4.20.04.1 libotf0 0.9.13-7 libp11-kit0 0.23.20-1ubuntu0.1 libpam-modules 1.3.1-5ubuntu4.2 libpam-modules-bin 1.3.1-5ubuntu4.2 libpam0g 1.3.1-5ubuntu4.2 libpango-1.0-0 1.44.7-2ubuntu4 libpangocairo-1.0-0 1.44.7-2ubuntu4 libpangoft2-1.0-0
[Desktop-packages] [Bug 1628707] Re: Highlighting a region in emacs is invisible because region color equals window color
** Also affects: emacs (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to emacs24 in Ubuntu. https://bugs.launchpad.net/bugs/1628707 Title: Highlighting a region in emacs is invisible because region color equals window color Status in emacs package in Ubuntu: New Status in emacs24 package in Ubuntu: Confirmed Bug description: If you open an Emacs window in Plasma/KDE, and you try to highlight a region of text by dragging the mouse, no highlighting appears. This is because the color for highlighting a region is identical to the color for the window background. I believe this color clash occurs between Ubuntu's emacs24 package and Ubuntu's X resource settings. To reproduce, log into Plasma, remove your $HOME/.emacs init file (so you have no personal customizations), and run emacs in an X window: $ emacs The window's background color is a light gray. Then type any text, click and drag the mouse over the text (or use keystroke commands to define a region). No highlighting appears, because the "region" color is also light gray. You can see this by running the emacs command: M-x list-faces-display I'll attach a screenshot so you can see that the "region" highlighting doesn't show up. The problem goes away if you disable the Ubuntu-supplied emacs init files: $ emacs -Q This is why I suspect the color is set badly in the Ubuntu emacs24 package. You can see the X background color by running the "appres" command in a shell window, which proves a light gray background is set, the same color as region highlighting: *background:#eff0f1 I tried to find the file where this background color is set, but I was not successful. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: emacs24 24.5+1-6ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: KDE Date: Wed Sep 28 18:07:25 2016 InstallationDate: Installed on 2016-09-25 (3 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: emacs24 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/emacs/+bug/1628707/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901294] Re: nouveau timeout and system lockup
I spoke too soon. This bug is back for me. ** Attachment added: "dmesg_gpu_freeze.log" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1901294/+attachment/5502015/+files/dmesg_gpu_freeze.log ** Tags added: hirsute -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1901294 Title: nouveau timeout and system lockup Status in xserver-xorg-video-nouveau package in Ubuntu: Confirmed Bug description: After upgrading from 20.04 to 20.10 system is unusable anymore due to GPU issues with nouveau. Same system worked fine on 20.04. Switching to nvidia proprietary driver and Xorg fixes the issue. Symptoms: System starts just fine, but overall UI performance is bad, everything seems slow and CPU usage seems too high even when idle. After a while UI freezes completly. Sometimes it recovers after several minutes, other times it doesn't and system freezes forever, requiring hard reboot. Setup: Ubuntu 20.10. nouveau. Wayland. nVidia GTX 1080 Ti. Intel Xeon E3-1231 v3. dmesg output attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1901294/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901294] Re: nouveau timeout and system lockup
This is fixed in 21.04. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1901294 Title: nouveau timeout and system lockup Status in xserver-xorg-video-nouveau package in Ubuntu: Confirmed Bug description: After upgrading from 20.04 to 20.10 system is unusable anymore due to GPU issues with nouveau. Same system worked fine on 20.04. Switching to nvidia proprietary driver and Xorg fixes the issue. Symptoms: System starts just fine, but overall UI performance is bad, everything seems slow and CPU usage seems too high even when idle. After a while UI freezes completly. Sometimes it recovers after several minutes, other times it doesn't and system freezes forever, requiring hard reboot. Setup: Ubuntu 20.10. nouveau. Wayland. nVidia GTX 1080 Ti. Intel Xeon E3-1231 v3. dmesg output attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1901294/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1925742] Re: Recent iCloud versions trigger an issue in IMAP x
Tested on: Ubuntu 21.04 Package: evolution-data-server 3.40.1-2 (from Impish-proposed) There aren't packages for hursuit (21.04) but I just tried the impish (21.10) package and works. Thanks again -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1925742 Title: Recent iCloud versions trigger an issue in IMAP x Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution-data-server source package in Focal: Fix Committed Bug description: * Impact The Icloud service introduced changes that are confusing evolution- data-server which means evolution is now failing to connect to the email server * Test case Set up an iCloud account and try to use it for emails in evolution * Regression potential The change is in the imapx connection code, it could create problems with other type of servers so we should try to test on different providers. - The bug has been fixed yesterday by Evolution's developer: https://gitlab.gnome.org/GNOME/evolution/-/issues/1468 However, the package in Ubuntu (at least in Focal Fosa) still needs to be updated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1925742/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1925742] Re: Recent iCloud versions trigger an issue in IMAP x
Tested on: Ubuntu 20.04.2 LTS Package: evolution-data-server 3.36.5-0ubuntu1 amd64 Personal iCloud account, now is solved. Thanks -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1925742 Title: Recent iCloud versions trigger an issue in IMAP x Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution-data-server source package in Focal: Fix Committed Bug description: * Impact The Icloud service introduced changes that are confusing evolution- data-server which means evolution is now failing to connect to the email server * Test case Set up an iCloud account and try to use it for emails in evolution * Regression potential The change is in the imapx connection code, it could create problems with other type of servers so we should try to test on different providers. - The bug has been fixed yesterday by Evolution's developer: https://gitlab.gnome.org/GNOME/evolution/-/issues/1468 However, the package in Ubuntu (at least in Focal Fosa) still needs to be updated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1925742/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1872298] Re: No permission to access files on storage device
In a current version it's work ok вт, 15 дек. 2020 г., 13:21 soredake <1872...@bugs.launchpad.net>: > Any progress on this? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1872298 > > Title: > No permission to access files on storage device > > Status in udisks2 package in Ubuntu: > New > > Bug description: > 1. Insert an encrypted flash drive (by cryptsetup) > 2. Enter the password > Expected result - get access to files > Actual result - Error message: Failed to open directory "fleshka" > Error opening directory '/media/xubuntu/fleshka':Permission denied > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: udisks2 2.8.4-1ubuntu1 > ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 > Uname: Linux 5.4.0-21-generic x86_64 > NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair > ApportVersion: 2.20.11-0ubuntu26 > Architecture: amd64 > CasperMD5CheckResult: skip > CasperVersion: 1.445 > CurrentDesktop: XFCE > Date: Sun Apr 12 12:51:39 2020 > LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200411) > MachineType: Acer Aspire 5734Z > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > ProcKernelCmdLine: file=/cdrom/preseed/username.seed > initrd=/casper/initrd quiet splash --- maybe-ubiquity > SourcePackage: udisks2 > Symptom: storage > Title: No permission to access files on storage device > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 04/16/2010 > dmi.bios.vendor: Acer > dmi.bios.version: V1.01 > dmi.board.asset.tag: Base Board Asset Tag > dmi.board.name: Aspire 5734Z > dmi.board.vendor: Acer > dmi.board.version: V1.01 > dmi.chassis.type: 10 > dmi.chassis.vendor: Acer > dmi.chassis.version: V1.01 > dmi.modalias: > dmi:bvnAcer:bvrV1.01:bd04/16/2010:svnAcer:pnAspire5734Z:pvrV1.01:rvnAcer:rnAspire5734Z:rvrV1.01:cvnAcer:ct10:cvrV1.01: > dmi.product.family: Intel_Mobile > dmi.product.name: Aspire 5734Z > dmi.product.sku: Montevina_Fab > dmi.product.version: V1.01 > dmi.sys.vendor: Acer > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1872298/+subscriptions > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1872298 Title: No permission to access files on storage device Status in udisks2 package in Ubuntu: New Bug description: 1. Insert an encrypted flash drive (by cryptsetup) 2. Enter the password Expected result - get access to files Actual result - Error message: Failed to open directory "fleshka" Error opening directory '/media/xubuntu/fleshka':Permission denied ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: udisks2 2.8.4-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CasperVersion: 1.445 CurrentDesktop: XFCE Date: Sun Apr 12 12:51:39 2020 LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200411) MachineType: Acer Aspire 5734Z ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity SourcePackage: udisks2 Symptom: storage Title: No permission to access files on storage device UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/16/2010 dmi.bios.vendor: Acer dmi.bios.version: V1.01 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Aspire 5734Z dmi.board.vendor: Acer dmi.board.version: V1.01 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.01 dmi.modalias: dmi:bvnAcer:bvrV1.01:bd04/16/2010:svnAcer:pnAspire5734Z:pvrV1.01:rvnAcer:rnAspire5734Z:rvrV1.01:cvnAcer:ct10:cvrV1.01: dmi.product.family: Intel_Mobile dmi.product.name: Aspire 5734Z dmi.product.sku: Montevina_Fab dmi.product.version: V1.01 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1872298/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1902652] Re: [arm64] [Libre Computer Board AML-S805X-AC] 3D rendering is very slow
This iso won't install. On Tue, Nov 3, 2020 at 8:35 PM Daniel van Vugt <1902...@bugs.launchpad.net> wrote: > Please run these commands: > > ls -l /dev/dri/* > dri.txt > glxinfo > glx.txt > > and attach the resulting text files here. > > ** Changed in: mesa (Ubuntu) >Status: New => Incomplete > > ** Changed in: xf86-video-armsoc (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1902652 > > Title: > [arm64] [Libre Computer Board AML-S805X-AC] 3D rendering is very slow > > Status in mesa package in Ubuntu: > Incomplete > Status in xf86-video-armsoc package in Ubuntu: > Incomplete > > Bug description: > 3d rendering is very slow, also when surfing the internet, webpages > take a while to render. Internet access is not the problem. > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: xorg 1:7.7+19ubuntu7.1 > Uname: Linux 4.19.64+ aarch64 > ApportVersion: 2.20.9-0ubuntu7.18 > Architecture: arm64 > BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' > CompizPlugins: No value set for > `/apps/compiz-1/general/screen0/options/active_plugins' > CompositorRunning: None > CurrentDesktop: XFCE > Date: Tue Nov 3 05:42:00 2020 > DistUpgraded: Fresh install > DistroCodename: bionic > DistroVariant: ubuntu > ExtraDebuggingInterest: Yes, if not too technical > GraphicsCard: > > Lspci: > > ProcEnviron: >LANGUAGE=en >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.19.64+ > root=UUID=ed29fecf-6335-4caf-989f-7400b169cb82 ro rootflags=subvol=@ > noquiet splash vt.handoff=1 > Renderer: Software > SourcePackage: xorg > Symptom: display > UpgradeStatus: No upgrade log present (probably fresh install) > XorgConf: >Section "Device" > Identifier "Allwinner sun4i DRM driver" > Driver "armsoc" > Option "DRI2" "true" >EndSection > version.compiz: compiz N/A > version.libdrm2: libdrm2 2.4.101-2~18.04.1 > version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 > version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 > version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.7 > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A > version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 > version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1902652/+subscriptions > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1902652 Title: [arm64] [Libre Computer Board AML-S805X-AC] 3D rendering is very slow Status in mesa package in Ubuntu: Incomplete Status in xf86-video-armsoc package in Ubuntu: Incomplete Bug description: 3d rendering is very slow, also when surfing the internet, webpages take a while to render. Internet access is not the problem. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 Uname: Linux 4.19.64+ aarch64 ApportVersion: 2.20.9-0ubuntu7.18 Architecture: arm64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Tue Nov 3 05:42:00 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Lspci: ProcEnviron: LANGUAGE=en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.19.64+ root=UUID=ed29fecf-6335-4caf-989f-7400b169cb82 ro rootflags=subvol=@ noquiet splash vt.handoff=1 Renderer: Software SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) XorgConf: Section "Device" Identifier "Allwinner sun4i DRM driver" Driver "armsoc" Option "DRI2" "true" EndSection version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage
Re: [Desktop-packages] [Bug 1902652] Re: [arm64] [Libre Computer Board AML-S805X-AC] 3D rendering is very slow
there is no ubuntu 20 for my board. On Tue, Nov 3, 2020 at 12:25 AM Daniel van Vugt <1902...@bugs.launchpad.net> wrote: > ** Summary changed: > > - 3d rendering is very slow > + [arm64] [Libre Computer Board AML-S805X-AC] 3D rendering is very slow > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1902652 > > Title: > [arm64] [Libre Computer Board AML-S805X-AC] 3D rendering is very slow > > Status in xorg package in Ubuntu: > New > > Bug description: > 3d rendering is very slow, also when surfing the internet, webpages > take a while to render. Internet access is not the problem. > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: xorg 1:7.7+19ubuntu7.1 > Uname: Linux 4.19.64+ aarch64 > ApportVersion: 2.20.9-0ubuntu7.18 > Architecture: arm64 > BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' > CompizPlugins: No value set for > `/apps/compiz-1/general/screen0/options/active_plugins' > CompositorRunning: None > CurrentDesktop: XFCE > Date: Tue Nov 3 05:42:00 2020 > DistUpgraded: Fresh install > DistroCodename: bionic > DistroVariant: ubuntu > ExtraDebuggingInterest: Yes, if not too technical > GraphicsCard: > > Lspci: > > ProcEnviron: >LANGUAGE=en >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.19.64+ > root=UUID=ed29fecf-6335-4caf-989f-7400b169cb82 ro rootflags=subvol=@ > noquiet splash vt.handoff=1 > Renderer: Software > SourcePackage: xorg > Symptom: display > UpgradeStatus: No upgrade log present (probably fresh install) > XorgConf: >Section "Device" > Identifier "Allwinner sun4i DRM driver" > Driver "armsoc" > Option "DRI2" "true" >EndSection > version.compiz: compiz N/A > version.libdrm2: libdrm2 2.4.101-2~18.04.1 > version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 > version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 > version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.7 > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A > version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 > version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1902652/+subscriptions > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1902652 Title: [arm64] [Libre Computer Board AML-S805X-AC] 3D rendering is very slow Status in mesa package in Ubuntu: New Status in xf86-video-armsoc package in Ubuntu: New Bug description: 3d rendering is very slow, also when surfing the internet, webpages take a while to render. Internet access is not the problem. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 Uname: Linux 4.19.64+ aarch64 ApportVersion: 2.20.9-0ubuntu7.18 Architecture: arm64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Tue Nov 3 05:42:00 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Lspci: ProcEnviron: LANGUAGE=en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.19.64+ root=UUID=ed29fecf-6335-4caf-989f-7400b169cb82 ro rootflags=subvol=@ noquiet splash vt.handoff=1 Renderer: Software SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) XorgConf: Section "Device" Identifier "Allwinner sun4i DRM driver" Driver "armsoc" Option "DRI2" "true" EndSection version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1902652/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe
[Desktop-packages] [Bug 1902652] [NEW] 3d rendering is very slow
Public bug reported: 3d rendering is very slow, also when surfing the internet, webpages take a while to render. Internet access is not the problem. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 Uname: Linux 4.19.64+ aarch64 ApportVersion: 2.20.9-0ubuntu7.18 Architecture: arm64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Tue Nov 3 05:42:00 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Lspci: ProcEnviron: LANGUAGE=en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.19.64+ root=UUID=ed29fecf-6335-4caf-989f-7400b169cb82 ro rootflags=subvol=@ noquiet splash vt.handoff=1 Renderer: Software SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) XorgConf: Section "Device" Identifier "Allwinner sun4i DRM driver" Driver "armsoc" Option "DRI2" "true" EndSection version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 bionic performance ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1902652 Title: 3d rendering is very slow Status in xorg package in Ubuntu: New Bug description: 3d rendering is very slow, also when surfing the internet, webpages take a while to render. Internet access is not the problem. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 Uname: Linux 4.19.64+ aarch64 ApportVersion: 2.20.9-0ubuntu7.18 Architecture: arm64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Tue Nov 3 05:42:00 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Lspci: ProcEnviron: LANGUAGE=en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.19.64+ root=UUID=ed29fecf-6335-4caf-989f-7400b169cb82 ro rootflags=subvol=@ noquiet splash vt.handoff=1 Renderer: Software SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) XorgConf: Section "Device" Identifier "Allwinner sun4i DRM driver" Driver "armsoc" Option "DRI2" "true" EndSection version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1902652/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901294] Re: nouveau timeout and system lockup
Turns out high CPU Usage and slow UI issue is unrelated, it was due to CPU governor reset to powersave and always using min frequency. But the issue with nouveau timeout and system lockup still stays I guess. Unless it was triggered by low CPU frequency. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1901294 Title: nouveau timeout and system lockup Status in xserver-xorg-video-nouveau package in Ubuntu: New Bug description: After upgrading from 20.04 to 20.10 system is unusable anymore due to GPU issues with nouveau. Same system worked fine on 20.04. Switching to nvidia proprietary driver and Xorg fixes the issue. Symptoms: System starts just fine, but overall UI performance is bad, everything seems slow and CPU usage seems too high even when idle. After a while UI freezes completly. Sometimes it recovers after several minutes, other times it doesn't and system freezes forever, requiring hard reboot. Setup: Ubuntu 20.10. nouveau. Wayland. nVidia GTX 1080 Ti. Intel Xeon E3-1231 v3. dmesg output attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1901294/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901294] Re: nouveau timeout and system lockup
** Description changed: After upgrading from 20.04 to 20.10 system is unusable anymore due to GPU issues with nouveau. Same system worked fine on 20.04. Switching to nvidia proprietary driver and Xorg fixes the issue. Symptoms: System starts just fine, but overall UI performance is bad, everything seems slow and CPU usage seems too high even when idle. After a while UI freezes completly. Sometimes it recovers after several minutes, other times it doesn't and system freezes forever, requiring hard reboot. - Setup: Ubuntu 20.10. nouveau. Wayland. nVidia GTX 1080 Ti. + Setup: Ubuntu 20.10. nouveau. Wayland. nVidia GTX 1080 Ti. Intel Xeon + E3-1231 v3. dmesg output attached. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1901294 Title: nouveau timeout and system lockup Status in xserver-xorg-video-nouveau package in Ubuntu: New Bug description: After upgrading from 20.04 to 20.10 system is unusable anymore due to GPU issues with nouveau. Same system worked fine on 20.04. Switching to nvidia proprietary driver and Xorg fixes the issue. Symptoms: System starts just fine, but overall UI performance is bad, everything seems slow and CPU usage seems too high even when idle. After a while UI freezes completly. Sometimes it recovers after several minutes, other times it doesn't and system freezes forever, requiring hard reboot. Setup: Ubuntu 20.10. nouveau. Wayland. nVidia GTX 1080 Ti. Intel Xeon E3-1231 v3. dmesg output attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1901294/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901294] Re: nouveau timeout and system lockup
Tried 5.9.1 mainline kernel and got the same issue. The only difference is Wayland recovered much faster (under 1 min). I didn't wait after recovery to see if system will lockup completely and rebooted with proprietary driver. Attaching dmesg output. ** Attachment added: "dmesg_5.9.1_mainline.log" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1901294/+attachment/5426606/+files/dmesg_5.9.1_mainline.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1901294 Title: nouveau timeout and system lockup Status in xserver-xorg-video-nouveau package in Ubuntu: New Bug description: After upgrading from 20.04 to 20.10 system is unusable anymore due to GPU issues with nouveau. Same system worked fine on 20.04. Switching to nvidia proprietary driver and Xorg fixes the issue. Symptoms: System starts just fine, but overall UI performance is bad, everything seems slow and CPU usage seems too high even when idle. After a while UI freezes completly. Sometimes it recovers after several minutes, other times it doesn't and system freezes forever, requiring hard reboot. Setup: Ubuntu 20.10. nouveau. Wayland. nVidia GTX 1080 Ti. dmesg output attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1901294/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901294] Re: nouveau timeout and system lockup
** Description changed: After upgrading from 20.04 to 20.10 system is unusable anymore due to GPU issues with nouveau. Same system worked fine on 20.04. Switching to nvidia proprietary driver and Xorg fixes the issue. Symptoms: System starts just fine, but overall UI performance is bad, everything seems slow and CPU usage seems too high even when idle. After a while UI freezes completly. Sometimes it recovers after several minutes, other - times it doesn't and system freezes forever, requiring hard revoot. + times it doesn't and system freezes forever, requiring hard reboot. Setup: Ubuntu 20.10. nouveau. Wayland. nVidia GTX 1080 Ti. dmesg output attached. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1901294 Title: nouveau timeout and system lockup Status in xserver-xorg-video-nouveau package in Ubuntu: New Bug description: After upgrading from 20.04 to 20.10 system is unusable anymore due to GPU issues with nouveau. Same system worked fine on 20.04. Switching to nvidia proprietary driver and Xorg fixes the issue. Symptoms: System starts just fine, but overall UI performance is bad, everything seems slow and CPU usage seems too high even when idle. After a while UI freezes completly. Sometimes it recovers after several minutes, other times it doesn't and system freezes forever, requiring hard reboot. Setup: Ubuntu 20.10. nouveau. Wayland. nVidia GTX 1080 Ti. dmesg output attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1901294/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901294] Re: nouveau timeout and system lockup
** Description changed: After upgrading from 20.04 to 20.10 system is unusable anymore due to GPU issues with nouveau. Same system worked fine on 20.04. + + Switching to nvidia proprietary driver and Xorg fixes the issue. Symptoms: System starts just fine, but overall UI performance is bad, everything seems slow and CPU usage seems too high even when idle. After a while UI freezes completly. Sometimes it recovers after several minutes, other times it doesn't and system freezes forever, requiring hard revoot. Setup: Ubuntu 20.10. nouveau. Wayland. nVidia GTX 1080 Ti. dmesg output attached. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1901294 Title: nouveau timeout and system lockup Status in xserver-xorg-video-nouveau package in Ubuntu: New Bug description: After upgrading from 20.04 to 20.10 system is unusable anymore due to GPU issues with nouveau. Same system worked fine on 20.04. Switching to nvidia proprietary driver and Xorg fixes the issue. Symptoms: System starts just fine, but overall UI performance is bad, everything seems slow and CPU usage seems too high even when idle. After a while UI freezes completly. Sometimes it recovers after several minutes, other times it doesn't and system freezes forever, requiring hard revoot. Setup: Ubuntu 20.10. nouveau. Wayland. nVidia GTX 1080 Ti. dmesg output attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1901294/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901294] [NEW] nouveau timeout and system lockup
Public bug reported: After upgrading from 20.04 to 20.10 system is unusable anymore due to GPU issues with nouveau. Same system worked fine on 20.04. Symptoms: System starts just fine, but overall UI performance is bad, everything seems slow and CPU usage seems too high even when idle. After a while UI freezes completly. Sometimes it recovers after several minutes, other times it doesn't and system freezes forever, requiring hard revoot. Setup: Ubuntu 20.10. nouveau. Wayland. nVidia GTX 1080 Ti. dmesg output attached. ** Affects: xserver-xorg-video-nouveau (Ubuntu) Importance: Undecided Status: New ** Tags: groovy ** Attachment added: "dmesg.log" https://bugs.launchpad.net/bugs/1901294/+attachment/5426351/+files/dmesg.log ** Tags added: groovy ** Description changed: After upgrading from 20.04 to 20.10 system is unusable anymore due to GPU issues with nouveau. Same system worked fine on 20.04. Symptoms: System starts just fine, but overall UI performance is bad, everything seems slow and CPU usage seems too high even when idle. After a while UI freezes completly. Sometimes it recovers after several minutes, other - times it doesn't and system freezes completly. + times it doesn't and system freezes forever, requiring hard revoot. Setup: Ubuntu 20.10. nouveau. Wayland. nVidia GTX 1080 Ti. dmesg output attached. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1901294 Title: nouveau timeout and system lockup Status in xserver-xorg-video-nouveau package in Ubuntu: New Bug description: After upgrading from 20.04 to 20.10 system is unusable anymore due to GPU issues with nouveau. Same system worked fine on 20.04. Symptoms: System starts just fine, but overall UI performance is bad, everything seems slow and CPU usage seems too high even when idle. After a while UI freezes completly. Sometimes it recovers after several minutes, other times it doesn't and system freezes forever, requiring hard revoot. Setup: Ubuntu 20.10. nouveau. Wayland. nVidia GTX 1080 Ti. dmesg output attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1901294/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
They also mentioned the suspend problem at https://bugzilla.kernel.org/show_bug.cgi?id=207759#c19 , not only the problem of the touchpad that didn't work. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in Pop!_OS: New Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Status in linux package in Arch Linux: Fix Committed Status in linux package in Fedora: Confirmed Status in linux package in openSUSE: New Bug description: Hello The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at all (pointer and click never move when touchpad is touched). This has been reported by other users in various websites, with various linux systems including other Ubuntu systems, but I saw no launchpad bug so I post one. Example of websites covering the issue : - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly the same laptop) - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar laptop) xinput indentifies it as MSFT0001:00 04F3:3140 Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Ideapad extra buttons id=15 [slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=18 [slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] Thanks a lot for your time. It does not help, but I can confirm what was reported on askubuntu by another user : the touchpad does work on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1567 F pulseaudio /dev/snd/controlC1: nicolas1567 F pulseaudio /dev/snd/controlC2: nicolas1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 20:14:25 2020 InstallationDate: Installed on 2020-07-02 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 82B5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN19WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 15ARH05 dmi.modalias: dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05: dmi.product.family: Legion 5 15ARH05 dmi.product.name: 82B5 dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5
[Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
I had problems (the touchpad not working and the suspend not working) with ELAN0001:00 04F3:3140 under linux-image-unsigned-5.6.0-1021-oem on Ubuntu, but they are gone if I manually unbind the device from elants_i2c driver and bind it to i2c_hid -- https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.6/+bug/1900254 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in Pop!_OS: New Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Status in linux package in Arch Linux: Fix Committed Status in linux package in Fedora: Confirmed Status in linux package in openSUSE: New Bug description: Hello The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at all (pointer and click never move when touchpad is touched). This has been reported by other users in various websites, with various linux systems including other Ubuntu systems, but I saw no launchpad bug so I post one. Example of websites covering the issue : - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly the same laptop) - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar laptop) xinput indentifies it as MSFT0001:00 04F3:3140 Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Ideapad extra buttons id=15 [slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=18 [slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] Thanks a lot for your time. It does not help, but I can confirm what was reported on askubuntu by another user : the touchpad does work on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1567 F pulseaudio /dev/snd/controlC1: nicolas1567 F pulseaudio /dev/snd/controlC2: nicolas1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 20:14:25 2020 InstallationDate: Installed on 2020-07-02 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 82B5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN19WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 15ARH05 dmi.modalias:
[Desktop-packages] [Bug 1760818] Re: gedit and gnome-calculator transparency/graphics corruption issue when GTK_IM_MODULE=xim is set
I solved the problem changing the gnome theme to Adwaita using gnome tweaks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to im-config in Ubuntu. https://bugs.launchpad.net/bugs/1760818 Title: gedit and gnome-calculator transparency/graphics corruption issue when GTK_IM_MODULE=xim is set Status in Ubuntu: Confirmed Status in im-config package in Ubuntu: Fix Released Status in light-themes package in Ubuntu: Confirmed Bug description: In a "Ubuntu" (Xorg) session on 18.04 gedit and gnome-calculator suffer from a graphics issue where parts of their windows hold parts of wallpaper or other windows' contents as background. See attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: light-themes 16.10+18.04.20180328-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 3 09:12:31 2018 PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: Upgraded to bionic on 2018-02-07 (54 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1760818/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1824874] Re: undismissable, unclickable authentication dialog left on screen (top-left corner) after policykit authentication [pushModal: invocation of begin_modal failed]
Same here. Cannot kill it with xkill, but doing de Alt+f2 then press r does the trick. I'm on Ubuntu 20.04.1 LTS -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1824874 Title: undismissable, unclickable authentication dialog left on screen (top- left corner) after policykit authentication [pushModal: invocation of begin_modal failed] Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Triaged Bug description: In disco, when policykit prompted me for a password in order for update-manager to dispatch instructions to aptdaemon to perform package updates, the password dialog remained on the screen after I clicked 'authenticate'. The window is not clickable, it appears not to even be a window - mouse presses are received by the window underneath. The exception is that the 'cancel' button is active and receives mouse events - but clicking it does nothing. This may be a gnome-shell issue rather than policykit. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: policykit-1 0.105-25 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 15 13:14:33 2019 InstallationDate: Installed on 2010-09-24 (3125 days ago) InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1) SourcePackage: policykit-1 UpgradeStatus: Upgraded to disco on 2019-04-11 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1824874/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Legion 5 laptop with AMD - best I could do is add "blacklist hid_multitouch" to /etc/modprobe.d/blacklist.conf , it got the mouse to move but stutters a lot. [0.004610] ACPI: SSDT 0xCDFF4000 007216 (v02 LENOVO CB-01 0001 MSFT 0400) [2.467514] i2c_hid i2c-MSFT0001:00: supply vdd not found, using dummy regulator [2.467526] i2c_hid i2c-MSFT0001:00: supply vddl not found, using dummy regulator [2.632628] input: MSFT0001:00 06CB:7F28 Mouse as /devices/platform/AMDI0010:03/i2c-0/i2c-MSFT0001:00/0018:06CB:7F28.0001/input/input6 [2.632754] input: MSFT0001:00 06CB:7F28 Touchpad as /devices/platform/AMDI0010:03/i2c-0/i2c-MSFT0001:00/0018:06CB:7F28.0001/input/input7 [2.632894] hid-generic 0018:06CB:7F28.0001: input,hidraw0: I2C HID v1.00 Mouse [MSFT0001:00 06CB:7F28] on i2c-MSFT0001:00 I: Bus=0018 Vendor=06cb Product=7f28 Version=0100 N: Name="MSFT0001:00 06CB:7F28 Mouse" P: Phys=i2c-MSFT0001:00 S: Sysfs=/devices/platform/AMDI0010:03/i2c-0/i2c-MSFT0001:00/0018:06CB:7F28.0001/input/input6 U: Uniq= H: Handlers=mouse0 event6 B: PROP=0 B: EV=17 B: KEY=3 0 0 0 0 B: REL=3 B: MSC=10 I: Bus=0018 Vendor=06cb Product=7f28 Version=0100 N: Name="MSFT0001:00 06CB:7F28 Touchpad" P: Phys=i2c-MSFT0001:00 S: Sysfs=/devices/platform/AMDI0010:03/i2c-0/i2c-MSFT0001:00/0018:06CB:7F28.0001/input/input7 U: Uniq= H: Handlers=mouse1 event7 B: PROP=0 B: EV=1b B: KEY=400 1 0 0 0 0 B: ABS=103 B: MSC=10 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in Pop!_OS: New Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Status in linux package in Arch Linux: Confirmed Status in linux package in Fedora: Confirmed Status in linux package in openSUSE: New Bug description: Hello The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at all (pointer and click never move when touchpad is touched). This has been reported by other users in various websites, with various linux systems including other Ubuntu systems, but I saw no launchpad bug so I post one. Example of websites covering the issue : - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly the same laptop) - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar laptop) xinput indentifies it as MSFT0001:00 04F3:3140 Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Ideapad extra buttons id=15 [slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=18 [slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] Thanks a lot for your time. It does not help, but I can confirm what was reported on askubuntu by another user : the touchpad does work on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1567 F pulseaudio /dev/snd/controlC1: nicolas1567 F pulseaudio /dev/snd/controlC2: nicolas1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 20:14:25 2020 InstallationDate: Installed on 2020-07-02 (8 days ago)
[Desktop-packages] [Bug 938751] Re: Images are washed out or colors are skewed in some apps (particularly Image Viewer and Chrome)
A good demonstration of this bug is taking recursive screenshots, as it makes the distortion of the colours that much more noticeable (see attachment, made with eog and gnome-screenshot with a colour profile on). ** Attachment added: "Recursive screenshot (new <---> old)" https://bugs.launchpad.net/ubuntu/+source/eog/+bug/938751/+attachment/5409392/+files/with-screen-calibration.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/938751 Title: Images are washed out or colors are skewed in some apps (particularly Image Viewer and Chrome) Status in GNOME Shell: Unknown Status in chromium-browser package in Ubuntu: Confirmed Status in colord package in Ubuntu: Confirmed Status in eog package in Ubuntu: Confirmed Status in inkscape package in Ubuntu: Confirmed Bug description: Images are washed out or colors are skewed in some apps, notably Chrome/Chromium and Image Viewer (eog). Workaround: Settings > Devices > Colour > and disable or remove your monitor's colour profile Originally reported in https://bugzilla.gnome.org/show_bug.cgi?id=675645 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/938751/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892440] Re: Shell text is too small in mutter 3.36.4-0ubuntu0.20.04.2
Same issue here. New computer with freshly installed Ubuntu on empty SSD Ubuntu 20.04.1 LTS AMD Ryzen 5 Nvidia Geforce GT 710 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1892440 Title: Shell text is too small in mutter 3.36.4-0ubuntu0.20.04.2 Status in mutter package in Ubuntu: Confirmed Status in mutter source package in Focal: Confirmed Bug description: See also bug 1892521. The package mutter version (3.36.4-0ubuntu0.20.04.2) for Ubuntu 20.04 causes small text in GNOME Shell menu with NVIDIA cards. With a previous version (3.36.4-0ubuntu0.20.04.1) all works fine. The problem is after update to the (3.36.4-0ubuntu0.20.04.2). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-18 (2 days ago) InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" (20200815) NonfreeKernelModules: nvidia_modeset nvidia Package: mutter 3.36.4-0ubuntu0.20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-15T17:44:36 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870867] Re: gnome-shell crashed with SIGABRT meta_x11_get_stage_window: assertion failed: (META_IS_STAGE_X11 (impl))
I have mutter from proposed, and I don't see any newer version of gnome- shell in the proposed repository. I've attached the crash file as well. Also, I'm not really sure if the crash I reproduced is about this bug or not. I've had other crashes that were filed separately and have different stack traces but were caused by using the touchscreen also, such as https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1861542 Just in case, here's the actual versions: sibrus@poseidon:~/tmp$ dpkg --list | grep mutter ii gir1.2-mutter-6:amd64 3.36.3-0ubuntu0.20.04.1 amd64GObject introspection data for Mutter ii libmutter-6-0:amd64 3.36.3-0ubuntu0.20.04.1 amd64window manager library from the Mutter window manager ii mutter3.36.4-0ubuntu0.20.04.1 amd64Example window manager using GNOME's window manager library ii mutter-common 3.36.4-0ubuntu0.20.04.1 all shared files for the Mutter window manager sibrus@poseidon:~/tmp$ dpkg --list | grep gnome-shell ii chrome-gnome-shell10.1-5 all GNOME Shell extensions integration for web browsers ii gnome-shell 3.36.3-1ubuntu1~20.04.2 amd64graphical shell for the GNOME desktop ii gnome-shell-common3.36.3-1ubuntu1~20.04.2 all common files for the GNOME graphical shell ** Attachment added: "_usr_bin_gnome-shell.1000.crash" https://bugs.launchpad.net/ubuntu/focal/+source/mutter/+bug/1870867/+attachment/5395779/+files/_usr_bin_gnome-shell.1000.crash -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1870867 Title: gnome-shell crashed with SIGABRT meta_x11_get_stage_window: assertion failed: (META_IS_STAGE_X11 (impl)) Status in Mutter: Unknown Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Committed Bug description: [ Impact ] GNOME Shell crashes in meta_x11_get_stage_window. [ Test case ] Perform touch events via touchpad or touchscreen, eventually the shell will crash. Errors can be monitored at: https://errors.ubuntu.com/problem/1d4cdd9f2e9cd378a3e0aeed140079f319454bf2 [ Regression potential ] Windows might not be closed correctly when requested via delete-events (clicking on clientside decoration close button). --- ProblemType: CrashDistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 22:08:06 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1Signal: 6SourcePackage: gnome-shell StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 __GI_abort () at abort.c:79 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libmutter-6.so.0 Title: gnome-shell crashed with SIGABRT in __GI_raise() UpgradeStatus: Upgraded to focal on 2020-04-05 (0 days ago) UserGroups: adm cdrom dialout dip docker input libvirt lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1870867/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870867] Re: gnome-shell crashed with SIGABRT meta_x11_get_stage_window: assertion failed: (META_IS_STAGE_X11 (impl))
I ran another test of using the touchscreen and managed to make gnome- shell crash. It looks like apport uploaded it this time, but I couldn't figure out where it put it. I attached the *.uploaded file associated with the reproduction. There's some other files in /var/crash, but I guess they should have already been uploaded. Let me know if I should upload them. ** Attachment added: "_usr_bin_gnome-shell.1000.uploaded" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1870867/+attachment/5395034/+files/_usr_bin_gnome-shell.1000.uploaded -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1870867 Title: gnome-shell crashed with SIGABRT meta_x11_get_stage_window: assertion failed: (META_IS_STAGE_X11 (impl)) Status in Mutter: Unknown Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Committed Bug description: [ Impact ] GNOME Shell crashes in meta_x11_get_stage_window. [ Test case ] Perform touch events via touchpad or touchscreen, eventually the shell will crash. Errors can be monitored at: https://errors.ubuntu.com/problem/1d4cdd9f2e9cd378a3e0aeed140079f319454bf2 [ Regression potential ] Windows might not be closed correctly when requested via delete-events (clicking on clientside decoration close button). --- ProblemType: CrashDistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 22:08:06 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1Signal: 6SourcePackage: gnome-shell StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 __GI_abort () at abort.c:79 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libmutter-6.so.0 Title: gnome-shell crashed with SIGABRT in __GI_raise() UpgradeStatus: Upgraded to focal on 2020-04-05 (0 days ago) UserGroups: adm cdrom dialout dip docker input libvirt lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1870867/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870867] Re: gnome-shell crashed with SIGABRT meta_x11_get_stage_window: assertion failed: (META_IS_STAGE_X11 (impl))
Hi Brian, I installed the proposed package and tried to test this. My results were mixed. I used the touchscreen for a while without issues. But then xorg crashed (and this report was a crash in gnome-shell). Apport refused to submit the bug reports because apparently there were a few not-updated packges (there weren't yesterday). I think that's a different issue than this original report, but it's still a crash when using the touchscreen. I'll re-update all my packages and keep testing. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1870867 Title: gnome-shell crashed with SIGABRT meta_x11_get_stage_window: assertion failed: (META_IS_STAGE_X11 (impl)) Status in Mutter: Unknown Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Committed Bug description: [ Impact ] GNOME Shell crashes in meta_x11_get_stage_window. [ Test case ] Perform touch events via touchpad or touchscreen, eventually the shell will crash. Errors can be monitored at: https://errors.ubuntu.com/problem/1d4cdd9f2e9cd378a3e0aeed140079f319454bf2 [ Regression potential ] Windows might not be closed correctly when requested via delete-events (clicking on clientside decoration close button). --- ProblemType: CrashDistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 22:08:06 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1Signal: 6SourcePackage: gnome-shell StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 __GI_abort () at abort.c:79 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libmutter-6.so.0 Title: gnome-shell crashed with SIGABRT in __GI_raise() UpgradeStatus: Upgraded to focal on 2020-04-05 (0 days ago) UserGroups: adm cdrom dialout dip docker input libvirt lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1870867/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1883358] [NEW] ricerca errori so
Public bug reported: istruzioni per riparare ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-106.107-generic 4.15.18 Uname: Linux 4.15.0-106-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.15 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sat Jun 13 11:56:57 2020 DistUpgraded: 2020-06-12 17:46:39,366 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [8086:a011] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [1043:83ac] Subsystem: ASUSTeK Computer Inc. Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [1043:83ac] InstallationDate: Installed on 2020-06-11 (1 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release i386 (20190227.1) MachineType: ASUSTeK Computer INC. 1005P ProcEnviron: LANGUAGE=it PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-106-generic root=UUID=3de418b8-edb0-412d-8b9b-61a85d80ed34 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2020-06-12 (0 days ago) dmi.bios.date: 01/04/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0706 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 1005P dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer INC. dmi.chassis.version: x.x dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0706:bd01/04/2010:svnASUSTeKComputerINC.:pn1005P:pvrx.x:rvnASUSTeKComputerINC.:rn1005P:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x: dmi.product.family: Eee PC dmi.product.name: 1005P dmi.product.version: x.x dmi.sys.vendor: ASUSTeK Computer INC. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sat Jun 13 11:48:00 2020 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1001 vendor HSD xserver.version: 2:1.19.6-1ubuntu4.4 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug bionic compiz-0.9 i386 ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1883358 Title: ricerca errori so Status in xorg package in Ubuntu: New Bug description: istruzioni per riparare ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-106.107-generic 4.15.18 Uname: Linux 4.15.0-106-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.15 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sat Jun 13 11:56:57 2020 DistUpgraded: 2020-06-12 17:46:39,366 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [8086:a011] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [1043:83ac] Subsystem: ASUSTeK Computer Inc. Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [1043:83ac] InstallationDate: Installed on 2020-06-11 (1 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release i386 (20190227.1) MachineType: ASUSTeK Computer INC. 1005P ProcEnviron: LANGUAGE=it PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-106-generic root=UUID=3de418b8-edb0-412d-8b9b-61a85d80ed34 ro quiet splash vt.handoff=1
[Desktop-packages] [Bug 1871984] Re: gnome-shell crashed with SIGSEGV in st_theme_node_lookup_shadow()
I never isolated a way to reproduce this bug, and I haven't encountered it again (even with keeping the extensions enabled). In fact generally the gnome-shell crashes have largely stopped. I'm not sure at what point that was, but for at least the past few days, things that would often crash gnome-shell no longer cause crashes (such as clicking the top-bar widgets on the lock screen, which before reliably triggered https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1868440). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1871984 Title: gnome-shell crashed with SIGSEGV in st_theme_node_lookup_shadow() Status in gnome-shell package in Ubuntu: Incomplete Bug description: I can't really pinpoint the cause because I've had lots of gnome-shell crashes during normal use and I can't very well tell them apart. One more-common factor is clicking the top-bar, either when logged in or when the screen is locked. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 19:22:24 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 SegvAnalysis: Segfault happened at: 0x7fa819f2 : mov(%rax),%rdi PC (0x7fa819f2) ok source "(%rax)" (0x223d657079742000) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: st_theme_node_lookup_shadow () from /usr/lib/gnome-shell/libst-1.0.so st_theme_node_get_text_shadow () from /usr/lib/gnome-shell/libst-1.0.so st_theme_node_get_text_shadow () from /usr/lib/gnome-shell/libst-1.0.so st_theme_node_get_text_shadow () from /usr/lib/gnome-shell/libst-1.0.so st_theme_node_get_text_shadow () from /usr/lib/gnome-shell/libst-1.0.so Title: gnome-shell crashed with SIGSEGV in st_theme_node_lookup_shadow() UpgradeStatus: Upgraded to focal on 2020-04-05 (4 days ago) UserGroups: adm cdrom dialout dip docker input libvirt lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1871984/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872298] Re: No permission to access files on storage device
Hi, Sebastien! I'm not sure if this is exactly the udisk issue. I just did not fully understand the report procedure. Please tell me how to collect journalctl log. ** Changed in: udisks2 (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1872298 Title: No permission to access files on storage device Status in udisks2 package in Ubuntu: New Bug description: 1. Insert an encrypted flash drive (by cryptsetup) 2. Enter the password Expected result - get access to files Actual result - Error message: Failed to open directory "fleshka" Error opening directory '/media/xubuntu/fleshka':Permission denied ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: udisks2 2.8.4-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CasperVersion: 1.445 CurrentDesktop: XFCE Date: Sun Apr 12 12:51:39 2020 LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200411) MachineType: Acer Aspire 5734Z ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity SourcePackage: udisks2 Symptom: storage Title: No permission to access files on storage device UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/16/2010 dmi.bios.vendor: Acer dmi.bios.version: V1.01 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Aspire 5734Z dmi.board.vendor: Acer dmi.board.version: V1.01 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.01 dmi.modalias: dmi:bvnAcer:bvrV1.01:bd04/16/2010:svnAcer:pnAspire5734Z:pvrV1.01:rvnAcer:rnAspire5734Z:rvrV1.01:cvnAcer:ct10:cvrV1.01: dmi.product.family: Intel_Mobile dmi.product.name: Aspire 5734Z dmi.product.sku: Montevina_Fab dmi.product.version: V1.01 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1872298/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870184] Re: Snap store not showing ubuntu repository apt apps inthe store
@Tanal according this thread: https://discourse.ubuntu.com/t/is-ubuntu-software-going-to-be-remove-for-snap-snap-store/14542/87 It has to be fixed before the release. Gnome Software is available via focal repo and it works exactly the same way as in 18.04. I've uninstalled the new store and it didn't want to install it back with any update, at least not immediately after a reboot. So if it is not fixed for the release or doesn't work after the upgrade (as I understand it works in some cases, perhaps for upgrades but not for the clean installations). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1870184 Title: Snap store not showing ubuntu repository apt apps inthe store Status in snap-store: Confirmed Status in gnome-desktop package in Ubuntu: Invalid Status in gnome-software package in Ubuntu: Invalid Bug description: OS : Ubuntu 20.04 (20200401) Problem : repository (apt) apps are not showing Problem Simulation: Install ubuntu 20.04 current daily build > open Snap Store> Search gnome tweak (or anyother apt apps) > no results Expected Solution: The Snap store should show repository apps or the gnome software should have installed by default. Thank you To manage notifications about this bug go to: https://bugs.launchpad.net/snap-store/+bug/1870184/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870184] Re: Snap store not showing ubuntu repository apt apps inthe store
@corrado, that's not a solution, if you replace one app store with another it should manage apps installed by default. And it could be really confusing for the new users, if you cannot see the apps you have installed as the installed section. There's no way for a new user to know something else should be installed, this is workaround and not a solution. Besides it's clearly a downgrade from 18.04 where it works just fine. And as per my knowledge it was promised that the new store will support snaps along with .deb and also flatpacs. So indeed it must be fixed before the release, especially considering we're talking about LTS. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1870184 Title: Snap store not showing ubuntu repository apt apps inthe store Status in snap-store: Confirmed Status in gnome-desktop package in Ubuntu: Invalid Status in gnome-software package in Ubuntu: Invalid Bug description: OS : Ubuntu 20.04 (20200401) Problem : repository (apt) apps are not showing Problem Simulation: Install ubuntu 20.04 current daily build > open Snap Store> Search gnome tweak (or anyother apt apps) > no results Expected Solution: The Snap store should show repository apps or the gnome software should have installed by default. Thank you To manage notifications about this bug go to: https://bugs.launchpad.net/snap-store/+bug/1870184/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872298] [NEW] No permission to access files on storage device
Public bug reported: 1. Insert an encrypted flash drive (by cryptsetup) 2. Enter the password Expected result - get access to files Actual result - Error message: Failed to open directory "fleshka" Error opening directory '/media/xubuntu/fleshka':Permission denied ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: udisks2 2.8.4-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CasperVersion: 1.445 CurrentDesktop: XFCE Date: Sun Apr 12 12:51:39 2020 LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200411) MachineType: Acer Aspire 5734Z ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity SourcePackage: udisks2 Symptom: storage Title: No permission to access files on storage device UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/16/2010 dmi.bios.vendor: Acer dmi.bios.version: V1.01 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Aspire 5734Z dmi.board.vendor: Acer dmi.board.version: V1.01 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.01 dmi.modalias: dmi:bvnAcer:bvrV1.01:bd04/16/2010:svnAcer:pnAspire5734Z:pvrV1.01:rvnAcer:rnAspire5734Z:rvrV1.01:cvnAcer:ct10:cvrV1.01: dmi.product.family: Intel_Mobile dmi.product.name: Aspire 5734Z dmi.product.sku: Montevina_Fab dmi.product.version: V1.01 dmi.sys.vendor: Acer ** Affects: udisks2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1872298 Title: No permission to access files on storage device Status in udisks2 package in Ubuntu: New Bug description: 1. Insert an encrypted flash drive (by cryptsetup) 2. Enter the password Expected result - get access to files Actual result - Error message: Failed to open directory "fleshka" Error opening directory '/media/xubuntu/fleshka':Permission denied ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: udisks2 2.8.4-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CasperVersion: 1.445 CurrentDesktop: XFCE Date: Sun Apr 12 12:51:39 2020 LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200411) MachineType: Acer Aspire 5734Z ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity SourcePackage: udisks2 Symptom: storage Title: No permission to access files on storage device UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/16/2010 dmi.bios.vendor: Acer dmi.bios.version: V1.01 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Aspire 5734Z dmi.board.vendor: Acer dmi.board.version: V1.01 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.01 dmi.modalias: dmi:bvnAcer:bvrV1.01:bd04/16/2010:svnAcer:pnAspire5734Z:pvrV1.01:rvnAcer:rnAspire5734Z:rvrV1.01:cvnAcer:ct10:cvrV1.01: dmi.product.family: Intel_Mobile dmi.product.name: Aspire 5734Z dmi.product.sku: Montevina_Fab dmi.product.version: V1.01 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1872298/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop
I have the same issue with an Acer Swift 3 SF314-57 58D5. Now running ubuntu 18.04 At first neither speakers or mic were working. I managed to get the speakers working by modifying the file /etc/modprobe.d/alsa-base.confn adding a lines at the end "options snd-hda-intel dmic_detect=0" [without quotes]. /etc/ The output for "arecord -l" is as follows: """ List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: Generic Analog [Generic Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 """ Tried adding "blacklist snd_soc_skl" to the file /etc/modprobe.d/blacklist.conf No solution still found. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1840725 Title: Microphone not working in Ubuntu 18.04.3 LTS on new hp- spectre-x360-convertible-15 laptop Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp- spectre-x360-convertible-15 laptop. The microphone works perfectly on Windows 10 (present in Dual boot mode). Initially, Internal Microphone was not even detected but installing alsa-tools-gui and overriding pin 0x12 to the Internal Microphone fixed that issue. [Pin 0x13 does not work and causes static in a headphone if it is plugged in.] Microphone is not able to pick up any sound. I changed levels/settings in alsamixer, pavucontrol without any success: In alsamixer: Experimented with levels ranging from very low to very high for Internal Mic, Capture, etc. In pavucontrol: Set the Internal Mic as a fallback device, unlocked the channels for the mic, experimented with reducing the level for one of the channels (reduced right mic level to Silence while keeping the left mic level normal/high and vice versa). alsa-info: http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f arecord -l List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1840725/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1832988] Re: Intel 8260 Bluetooth not working
As a workaround I'm currently doing rmmod btusb && modprobe btusb after every boot which seem to do the magic. Attaching the dmesg for that just in case. ** Attachment added: "dmesg2.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832988/+attachment/5335332/+files/dmesg2.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1832988 Title: Intel 8260 Bluetooth not working Status in gnome-bluetooth package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Released Bug description: Expected behaviour: I can enable bluetooth in the system settings, and pair with my other devices. Actual behaviour: Always displays as 'off' in the settings dialog, and won't turn on. Bluetooth worked on the same machine with previous Ubuntu releases (18.10) & no hardware changes. "dmesg | grep -i bluetooth" reports the following: ``` [ 14.445902] Bluetooth: Core ver 2.22 [ 14.445918] Bluetooth: HCI device and connection manager initialized [ 14.445921] Bluetooth: HCI socket layer initialized [ 14.445923] Bluetooth: L2CAP socket layer initialized [ 14.445929] Bluetooth: SCO socket layer initialized [ 14.494345] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014 [ 14.499050] Bluetooth: hci0: Device revision is 5 [ 14.499052] Bluetooth: hci0: Secure boot is enabled [ 14.499053] Bluetooth: hci0: OTP lock is enabled [ 14.499053] Bluetooth: hci0: API lock is enabled [ 14.499054] Bluetooth: hci0: Debug lock is disabled [ 14.499055] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [ 14.503899] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi [ 14.558347] Bluetooth: hci0: Failed to send firmware data (-38) [ 15.497805] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 15.497806] Bluetooth: BNEP filters: protocol multicast [ 15.497810] Bluetooth: BNEP socket layer initialized ``` "lsb_release -rd" reports the following: ``` Description: Ubuntu 19.04 Release: 19.04 ``` "cat /proc/version_signature" reports the following: ``` Ubuntu 5.0.0-16.17-generic 5.0.8 ``` "apt-cache policy linux-firmware" reports the following: ``` linux-firmware: Installed: 1.178.1 Candidate: 1.178.1 Version table: *** 1.178.1 500 500 http://gb.archive.ubuntu.com/ubuntu disco-updates/main amd64 Packages 500 http://gb.archive.ubuntu.com/ubuntu disco-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu disco-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu disco-security/main i386 Packages 100 /var/lib/dpkg/status 1.178 500 500 http://gb.archive.ubuntu.com/ubuntu disco/main amd64 Packages 500 http://gb.archive.ubuntu.com/ubuntu disco/main i386 Packages ``` ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-16-generic 5.0.0-16.17 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: martin 2314 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Jun 16 12:31:07 2019 InstallationDate: Installed on 2019-06-02 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1c7a:0603 LighTuning Technology Inc. Bus 001 Device 003: ID 5986:066d Acer, Inc Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: PC Specialist Limited N15_17RD ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-16-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-16-generic N/A linux-backports-modules-5.0.0-16-generic N/A linux-firmware1.178.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.11 dmi.board.asset.tag: Tag 12345 dmi.board.name: N15_17RD dmi.board.vendor: CLEVO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.11:bd12/25/2015:svnPCSpecialistLimited:pnN15_17RD:pvrNotApplicable:rvnCLEVO:rnN15_17RD:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N15_17RD dmi.product.sku: Not Applicable dmi.product.version: Not
[Desktop-packages] [Bug 1832988] Re: Intel 8260 Bluetooth not working
Still failing with the same error on latest Eoan (kernel 5.3.0-40-generic). Dmesg with default kernel and usbcore.dyndbg=+p attached. ** Attachment added: "dmesg.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832988/+attachment/5335331/+files/dmesg.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1832988 Title: Intel 8260 Bluetooth not working Status in gnome-bluetooth package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Released Bug description: Expected behaviour: I can enable bluetooth in the system settings, and pair with my other devices. Actual behaviour: Always displays as 'off' in the settings dialog, and won't turn on. Bluetooth worked on the same machine with previous Ubuntu releases (18.10) & no hardware changes. "dmesg | grep -i bluetooth" reports the following: ``` [ 14.445902] Bluetooth: Core ver 2.22 [ 14.445918] Bluetooth: HCI device and connection manager initialized [ 14.445921] Bluetooth: HCI socket layer initialized [ 14.445923] Bluetooth: L2CAP socket layer initialized [ 14.445929] Bluetooth: SCO socket layer initialized [ 14.494345] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014 [ 14.499050] Bluetooth: hci0: Device revision is 5 [ 14.499052] Bluetooth: hci0: Secure boot is enabled [ 14.499053] Bluetooth: hci0: OTP lock is enabled [ 14.499053] Bluetooth: hci0: API lock is enabled [ 14.499054] Bluetooth: hci0: Debug lock is disabled [ 14.499055] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [ 14.503899] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi [ 14.558347] Bluetooth: hci0: Failed to send firmware data (-38) [ 15.497805] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 15.497806] Bluetooth: BNEP filters: protocol multicast [ 15.497810] Bluetooth: BNEP socket layer initialized ``` "lsb_release -rd" reports the following: ``` Description: Ubuntu 19.04 Release: 19.04 ``` "cat /proc/version_signature" reports the following: ``` Ubuntu 5.0.0-16.17-generic 5.0.8 ``` "apt-cache policy linux-firmware" reports the following: ``` linux-firmware: Installed: 1.178.1 Candidate: 1.178.1 Version table: *** 1.178.1 500 500 http://gb.archive.ubuntu.com/ubuntu disco-updates/main amd64 Packages 500 http://gb.archive.ubuntu.com/ubuntu disco-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu disco-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu disco-security/main i386 Packages 100 /var/lib/dpkg/status 1.178 500 500 http://gb.archive.ubuntu.com/ubuntu disco/main amd64 Packages 500 http://gb.archive.ubuntu.com/ubuntu disco/main i386 Packages ``` ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-16-generic 5.0.0-16.17 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: martin 2314 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Jun 16 12:31:07 2019 InstallationDate: Installed on 2019-06-02 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1c7a:0603 LighTuning Technology Inc. Bus 001 Device 003: ID 5986:066d Acer, Inc Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: PC Specialist Limited N15_17RD ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-16-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-16-generic N/A linux-backports-modules-5.0.0-16-generic N/A linux-firmware1.178.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.11 dmi.board.asset.tag: Tag 12345 dmi.board.name: N15_17RD dmi.board.vendor: CLEVO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.11:bd12/25/2015:svnPCSpecialistLimited:pnN15_17RD:pvrNotApplicable:rvnCLEVO:rnN15_17RD:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N15_17RD dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor:
[Desktop-packages] [Bug 1860907] Re: gnome-shell crashes when using touchscreen
I reproduced the issue again, and sent the info per the instructions, it is here: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1861542 Sorry about not reading the instructions properly the first time, and thanks for your patience :) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1860907 Title: gnome-shell crashes when using touchscreen Status in gnome-shell package in Ubuntu: Incomplete Bug description: The crash isn't immediate, but reliably reproducible when using the touchscreen to interact with multiple full-screen native steam games. Typically happens within 30-120 minutes of normal use. (Same games don't crash at all if the touchscreen is not used.) I've reproduced the issue many times. Also seems to affect other full-screen applications such as the default video player (reproduced once). Typically right before the crash the reaction to touch input will become somewhat strange (touches seem to register, but the full-screen application doesn't respond as expected, for example moving the cursor but not actually performing the "tap" action). # lsb_release -rd Description: Ubuntu 19.10 Release: 19.10 # apt-cache policy gnome-shell gnome-shell: Installed: 3.34.1+git20191024-1ubuntu1~19.10.1 Candidate: 3.34.1+git20191024-1ubuntu1~19.10.1 Version table: *** 3.34.1+git20191024-1ubuntu1~19.10.1 500 500 http://archive.ubuntu.com/ubuntu eoan-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.34.1-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu eoan/main amd64 Packages 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 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jan 26 12:36:19 2020 DisplayManager: gdm3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.apport.crashdb.conf: 2020-01-25T22:33:07.611081 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1860907/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1860907] Re: gnome-shell crashes when using touchscreen
ubuntu-bug is telling me some packages were not the newest versions, I'm trying to reproduce again after upgrading my packages ** Attachment removed: "_usr_bin_gnome-shell.1000.crash" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1860907/+attachment/5324291/+files/_usr_bin_gnome-shell.1000.crash -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1860907 Title: gnome-shell crashes when using touchscreen Status in gnome-shell package in Ubuntu: Incomplete Bug description: The crash isn't immediate, but reliably reproducible when using the touchscreen to interact with multiple full-screen native steam games. Typically happens within 30-120 minutes of normal use. (Same games don't crash at all if the touchscreen is not used.) I've reproduced the issue many times. Also seems to affect other full-screen applications such as the default video player (reproduced once). Typically right before the crash the reaction to touch input will become somewhat strange (touches seem to register, but the full-screen application doesn't respond as expected, for example moving the cursor but not actually performing the "tap" action). # lsb_release -rd Description: Ubuntu 19.10 Release: 19.10 # apt-cache policy gnome-shell gnome-shell: Installed: 3.34.1+git20191024-1ubuntu1~19.10.1 Candidate: 3.34.1+git20191024-1ubuntu1~19.10.1 Version table: *** 3.34.1+git20191024-1ubuntu1~19.10.1 500 500 http://archive.ubuntu.com/ubuntu eoan-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.34.1-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu eoan/main amd64 Packages 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 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jan 26 12:36:19 2020 DisplayManager: gdm3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.apport.crashdb.conf: 2020-01-25T22:33:07.611081 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1860907/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1860907] Re: gnome-shell crashes when using touchscreen
Thanks for the guidance, Daniel I have uninstalled the extensions, rebooted, and was still able to reproduce the crash. I have uploaded the .crash file per the instructions you linked. Please let me know if there's anything else I can do to aid in the investigation. ** Attachment added: "_usr_bin_gnome-shell.1000.crash" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1860907/+attachment/5324291/+files/_usr_bin_gnome-shell.1000.crash -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1860907 Title: gnome-shell crashes when using touchscreen Status in gnome-shell package in Ubuntu: Incomplete Bug description: The crash isn't immediate, but reliably reproducible when using the touchscreen to interact with multiple full-screen native steam games. Typically happens within 30-120 minutes of normal use. (Same games don't crash at all if the touchscreen is not used.) I've reproduced the issue many times. Also seems to affect other full-screen applications such as the default video player (reproduced once). Typically right before the crash the reaction to touch input will become somewhat strange (touches seem to register, but the full-screen application doesn't respond as expected, for example moving the cursor but not actually performing the "tap" action). # lsb_release -rd Description: Ubuntu 19.10 Release: 19.10 # apt-cache policy gnome-shell gnome-shell: Installed: 3.34.1+git20191024-1ubuntu1~19.10.1 Candidate: 3.34.1+git20191024-1ubuntu1~19.10.1 Version table: *** 3.34.1+git20191024-1ubuntu1~19.10.1 500 500 http://archive.ubuntu.com/ubuntu eoan-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.34.1-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu eoan/main amd64 Packages 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 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jan 26 12:36:19 2020 DisplayManager: gdm3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.apport.crashdb.conf: 2020-01-25T22:33:07.611081 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1860907/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1860907] [NEW] gnome-shell crashes when using touchscreen
Public bug reported: The crash isn't immediate, but reliably reproducible when using the touchscreen to interact with multiple full-screen native steam games. Typically happens within 30-120 minutes of normal use. (Same games don't crash at all if the touchscreen is not used.) I've reproduced the issue many times. Also seems to affect other full-screen applications such as the default video player (reproduced once). Typically right before the crash the reaction to touch input will become somewhat strange (touches seem to register, but the full-screen application doesn't respond as expected, for example moving the cursor but not actually performing the "tap" action). # lsb_release -rd Description:Ubuntu 19.10 Release:19.10 # apt-cache policy gnome-shell gnome-shell: Installed: 3.34.1+git20191024-1ubuntu1~19.10.1 Candidate: 3.34.1+git20191024-1ubuntu1~19.10.1 Version table: *** 3.34.1+git20191024-1ubuntu1~19.10.1 500 500 http://archive.ubuntu.com/ubuntu eoan-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.34.1-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu eoan/main amd64 Packages 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 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jan 26 12:36:19 2020 DisplayManager: gdm3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.apport.crashdb.conf: 2020-01-25T22:33:07.611081 ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1860907 Title: gnome-shell crashes when using touchscreen Status in gnome-shell package in Ubuntu: New Bug description: The crash isn't immediate, but reliably reproducible when using the touchscreen to interact with multiple full-screen native steam games. Typically happens within 30-120 minutes of normal use. (Same games don't crash at all if the touchscreen is not used.) I've reproduced the issue many times. Also seems to affect other full-screen applications such as the default video player (reproduced once). Typically right before the crash the reaction to touch input will become somewhat strange (touches seem to register, but the full-screen application doesn't respond as expected, for example moving the cursor but not actually performing the "tap" action). # lsb_release -rd Description: Ubuntu 19.10 Release: 19.10 # apt-cache policy gnome-shell gnome-shell: Installed: 3.34.1+git20191024-1ubuntu1~19.10.1 Candidate: 3.34.1+git20191024-1ubuntu1~19.10.1 Version table: *** 3.34.1+git20191024-1ubuntu1~19.10.1 500 500 http://archive.ubuntu.com/ubuntu eoan-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.34.1-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu eoan/main amd64 Packages 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 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jan 26 12:36:19 2020 DisplayManager: gdm3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.apport.crashdb.conf: 2020-01-25T22:33:07.611081 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1860907/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1553685] Re: Lenovo Y700-17ISK subwoofer doesn't work
I tried it and it didn't work for me. In fact, I lost all sound and I had to revert the changes and reboot to fix. Still it might be something small that needs to be changed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1553685 Title: Lenovo Y700-17ISK subwoofer doesn't work Status in alsa-driver package in Ubuntu: Confirmed Bug description: Lenovo Y700-17ISK (Intel Core i7-6700HQ/RAM 16GB/SSD 512GB/Nvidia GTX960M 4GB) Operating system: Ubuntu 16.04 (xenial-desktop-amd64.iso 04-Mar-2016, kernel 4.4.0-10-generic, nvidia 361.28) Problem: Notebook subwoofer doesn't work. Judging from alsa-info.sh output, there is no pin declared for the bass output by BIOS. Please find a zip file attached: 'alsa-info_hdajackretask-unconnected-pins' ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-10-generic 4.4.0-10.25 ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3 Uname: Linux 4.4.0-10-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aljosa 1776 F pulseaudio CurrentDesktop: Unity Date: Sun Mar 6 11:02:21 2016 HibernationDevice: RESUME=UUID=ac022671-63df-40ae-bffe-66fff3b35125 InstallationDate: Installed on 2016-03-05 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304) MachineType: LENOVO 80Q0 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-10-generic.efi.signed root=UUID=aa4325c4-4b4c-4372-b8ca-a66c3e5b2aa6 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-10-generic N/A linux-backports-modules-4.4.0-10-generic N/A linux-firmware1.156 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2016 dmi.bios.vendor: LENOVO dmi.bios.version: CDCN30WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Allsparks 7A dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad Y700-17ISK dmi.modalias: dmi:bvnLENOVO:bvrCDCN30WW:bd01/31/2016:svnLENOVO:pn80Q0:pvrLenovoideapadY700-17ISK:rvnLENOVO:rnAllsparks7A:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapadY700-17ISK: dmi.product.name: 80Q0 dmi.product.version: Lenovo ideapad Y700-17ISK dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1553685/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1813701] Re: [amdgpu] Flickering graphics corruption (but none observed in kernels 4.18.10-4.18.12)
** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released ** Changed in: xserver-xorg-video-amdgpu (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1813701 Title: [amdgpu] Flickering graphics corruption (but none observed in kernels 4.18.10-4.18.12) Status in linux package in Ubuntu: Fix Released Status in xserver-xorg-video-amdgpu package in Ubuntu: Fix Released Bug description: The screen always flickers at a frequency of 75 GHz on the AMD RX 580 gpu. At 60 and 50 GHz, if you switch to any other than 75, the flickering will disappear until the display turns off. After switching on, flicker returns. At the core of 4.18.0-10, just like on the AMD Radeon HD7970 gpu, the problem is not visible. More in the video https://www.youtube.com/watch?v=d_LXHqWKTbk ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 29 13:13:19 2019 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X] [1002:67df] (rev e7) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Ellesmere [Radeon RX 470/480/570/570X/580/580X] [1043:0519] InstallationDate: Installed on 2019-01-22 (6 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: MSI MS-7693 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=ad22bc6d-c4e8-4393-a30b-6c247159b9dd ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/08/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V10.6 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 970A-G43 (MS-7693) dmi.board.vendor: MSI dmi.board.version: 3.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 3.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV10.6:bd01/08/2016:svnMSI:pnMS-7693:pvr3.0:rvnMSI:rn970A-G43(MS-7693):rvr3.0:cvnMSI:ct3:cvr3.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7693 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 3.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97+git1901221830.b7a7a9~oibaf~c version.libgl1-mesa-dri: libgl1-mesa-dri 19.0~git1901280730.d1d2bb~oibaf~c version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813701/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1852140] [NEW] package hplip-data 3.16.3+repack0-1 failed to install/upgrade: package hplip-data is already installed and configured
Public bug reported: he conseguido agregar la impresora a pesar del error ProblemType: Package DistroRelease: Ubuntu 16.04 Package: hplip-data 3.16.3+repack0-1 ProcVersionSignature: Ubuntu 4.15.0-66.75~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-66-generic i686 ApportVersion: 2.20.1-0ubuntu2.21 AptdaemonVersion: 1.1.1+bzr982-0ubuntu14.1 Architecture: i386 CupsErrorLog: Date: Mon Nov 11 22:57:50 2019 DuplicateSignature: package:hplip-data:3.16.3+repack0-1 Processing triggers for man-db (2.7.5-1) ... dpkg: error processing package libart-2.0-2:i386 (--configure): package libart-2.0-2:i386 is already installed and configured ErrorMessage: package hplip-data is already installed and configured InstallationDate: Installed on 2019-11-11 (0 days ago) InstallationMedia: Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: Packard Bell DOA150 PackageArchitecture: all Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-66-generic root=UUID=78936867-355d-46e8-9d95-523db97202d8 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.32 SourcePackage: hplip Title: package hplip-data 3.16.3+repack0-1 failed to install/upgrade: package hplip-data is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/09/2008 dmi.bios.vendor: Packard Bell dmi.bios.version: v0.3103 dmi.board.asset.tag: Base Board Asset Tag dmi.board.vendor: Packard Bell dmi.board.version: Base Board Version dmi.chassis.type: 1 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPackardBell:bvrv0.3103:bd10/09/2008:svnPackardBell:pnDOA150:pvrLU.B040B.016:rvnPackardBell:rn:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion: dmi.product.family: Intel_Mobile dmi.product.name: DOA150 dmi.product.version: LU.B040B.016 dmi.sys.vendor: Packard Bell ** Affects: hplip (Ubuntu) Importance: Undecided Status: New ** Tags: already-installed apport-package i386 xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1852140 Title: package hplip-data 3.16.3+repack0-1 failed to install/upgrade: package hplip-data is already installed and configured Status in hplip package in Ubuntu: New Bug description: he conseguido agregar la impresora a pesar del error ProblemType: Package DistroRelease: Ubuntu 16.04 Package: hplip-data 3.16.3+repack0-1 ProcVersionSignature: Ubuntu 4.15.0-66.75~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-66-generic i686 ApportVersion: 2.20.1-0ubuntu2.21 AptdaemonVersion: 1.1.1+bzr982-0ubuntu14.1 Architecture: i386 CupsErrorLog: Date: Mon Nov 11 22:57:50 2019 DuplicateSignature: package:hplip-data:3.16.3+repack0-1 Processing triggers for man-db (2.7.5-1) ... dpkg: error processing package libart-2.0-2:i386 (--configure): package libart-2.0-2:i386 is already installed and configured ErrorMessage: package hplip-data is already installed and configured InstallationDate: Installed on 2019-11-11 (0 days ago) InstallationMedia: Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: Packard Bell DOA150 PackageArchitecture: all Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-66-generic root=UUID=78936867-355d-46e8-9d95-523db97202d8 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.32 SourcePackage: hplip Title: package hplip-data 3.16.3+repack0-1 failed to install/upgrade: package hplip-data is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/09/2008 dmi.bios.vendor: Packard Bell dmi.bios.version: v0.3103 dmi.board.asset.tag: Base Board Asset Tag dmi.board.vendor: Packard Bell dmi.board.version: Base Board Version dmi.chassis.type: 1 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPackardBell:bvrv0.3103:bd10/09/2008:svnPackardBell:pnDOA150:pvrLU.B040B.016:rvnPackardBell:rn:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion: dmi.product.family: Intel_Mobile dmi.product.name: DOA150 dmi.product.version: LU.B040B.016 dmi.sys.vendor: Packard Bell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1852140/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1852025] [NEW] [TOSHIBA NB515, Realtek ALC269VB, Speaker, Internal] volume slider problem
Public bug reported: Everytime I boot there is no sound. With QasMixer I am able to fix it by selecting hw:0 (HDA Intel) and increasing the second slider from bottom to top, that slider says "auriculares" in spanish which is "headphones". I am not using headphones though and I didn't found any other way of increasing that slider in the standard programs that come installed by default in Ubuntu 19.10 (and many other older releases). ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 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.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: luigi 1637 F pulseaudio luigi 26280 F qasmixer /dev/snd/pcmC0D0p: luigi 1637 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Nov 10 19:38:04 2019 InstallationDate: Installed on 2012-07-29 (2660 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Audio Interno - HDA Intel Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: nov 10 17:18:45 luigi-netbook dbus-daemon[887]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.32' (uid=122 pid=1140 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined") nov 10 19:17:05 luigi-netbook pulseaudio[1140]: W: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended. Symptom_Type: Volume slider, or mixer problems Title: [TOSHIBA NB515, Realtek ALC269VB, Speaker, Internal] volume slider problem UpgradeStatus: Upgraded to eoan on 2019-11-10 (0 days ago) dmi.bios.date: 4/3/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 1.30 dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: MP dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvr1.30:bd4/3/2012:svnTOSHIBA:pnTOSHIBANB515:pvrPLL72P-013LM1:rvnTOSHIBA:rnPortablePC:rvrMP:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.family: Dolphin10 dmi.product.name: TOSHIBA NB515 dmi.product.sku: PLL72P-013LM1 dmi.product.version: PLL72P-013LM1 dmi.sys.vendor: TOSHIBA ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1852025 Title: [TOSHIBA NB515, Realtek ALC269VB, Speaker, Internal] volume slider problem Status in alsa-driver package in Ubuntu: New Bug description: Everytime I boot there is no sound. With QasMixer I am able to fix it by selecting hw:0 (HDA Intel) and increasing the second slider from bottom to top, that slider says "auriculares" in spanish which is "headphones". I am not using headphones though and I didn't found any other way of increasing that slider in the standard programs that come installed by default in Ubuntu 19.10 (and many other older releases). ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 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.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: luigi 1637 F pulseaudio luigi 26280 F qasmixer /dev/snd/pcmC0D0p: luigi 1637 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Nov 10 19:38:04 2019 InstallationDate: Installed on 2012-07-29 (2660 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Audio Interno - HDA Intel Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: nov 10 17:18:45 luigi-netbook dbus-daemon[887]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.32' (uid=122 pid=1140 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined") nov 10 19:17:05 luigi-netbook pulseaudio[1140]: W: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended. Symptom_Type: Volume slider, or mixer problems Title: [TOSHIBA NB515, Realtek ALC269VB, Speaker, Internal] volume slider problem UpgradeStatus: Upgraded to eoan on 2019-11-10 (0 days ago) dmi.bios.date: 4/3/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 1.30 dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: MP dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10
[Desktop-packages] [Bug 1852023] [NEW] Wayland doesn't work in GMA500
Public bug reported: I had to disable Wayland in GDM3 in order to be able to login. I guess an udev rule to disable Wayland for GMA500 is all that is needed. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Nov 10 19:14:19 2019 DistUpgraded: 2019-11-10 16:17:45,811 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Falló al ejecutar el proceso hijo «./xorg_fix_proprietary.py» (No existe el archivo o el directorio) (8)) DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Atom Processor D2xxx/N2xxx Integrated Graphics Controller [8086:0be1] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Atom Processor D2xxx/N2xxx Integrated Graphics Controller [1179:fc10] InstallationDate: Installed on 2012-07-29 (2660 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MachineType: TOSHIBA TOSHIBA NB515 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic root=UUID=5febd6a0-8053-4b1c-92f5-df934f0ea50b ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to eoan on 2019-11-10 (0 days ago) dmi.bios.date: 4/3/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 1.30 dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: MP dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvr1.30:bd4/3/2012:svnTOSHIBA:pnTOSHIBANB515:pvrPLL72P-013LM1:rvnTOSHIBA:rnPortablePC:rvrMP:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.family: Dolphin10 dmi.product.name: TOSHIBA NB515 dmi.product.sku: PLL72P-013LM1 dmi.product.version: PLL72P-013LM1 dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Mon Jul 1 17:43:10 2019 xserver.configfile: default xserver.errors: modeset(0): glamor initialization failed AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan freeze ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1852023 Title: Wayland doesn't work in GMA500 Status in xorg package in Ubuntu: New Bug description: I had to disable Wayland in GDM3 in order to be able to login. I guess an udev rule to disable Wayland for GMA500 is all that is needed. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Nov 10 19:14:19 2019 DistUpgraded: 2019-11-10 16:17:45,811 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Falló al ejecutar el proceso hijo «./xorg_fix_proprietary.py» (No existe el archivo o el directorio) (8)) DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Atom Processor D2xxx/N2xxx Integrated Graphics Controller [8086:0be1] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Atom Processor D2xxx/N2xxx Integrated Graphics Controller [1179:fc10] InstallationDate: Installed on 2012-07-29 (2660 days ago)
[Desktop-packages] [Bug 1850009] [NEW] Issue with detecting new state in dhclient-enter-hooks.d/resolved
Public bug reported: After upgrading to 19.10 I noticed that resolving hostnames stopped working. Quick release, which package and version info: root@caret:~# lsb_release -r Release:19.10 root@caret:~# dpkg -S /etc/dhcp/dhclient-enter-hooks.d/resolved systemd: /etc/dhcp/dhclient-enter-hooks.d/resolved root@caret:~# apt-cache policy systemd systemd: Installed: 242-7ubuntu3 Candidate: 242-7ubuntu3 Version table: *** 242-7ubuntu3 500 500 http://au.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status The file /etc/resolv.conf was pointing to the local instance of systemd-resolved however there was no search line, indicating something wasn't quite right. Restarting the systemd-resolved service did recreate /etc/resolv.conf with expected search line. After much debugging, I've worked out what was going wrong. The dhcp hook file /etc/dhcp/dhclient-enter-hooks.d/resolved has a bug in the resolver state change logic. This may also impact on tickets 1805183, 1832050, 1832053 and maybe others. When doing the md5sum of the old and new state, the command is wrong. It isn't sending STDOUT (and optionally STDERR) to the temp file but rather putting the md5sum command into the background and then creating an empty file for both states. Which obviously isn't different, so systemd- resolved doesn't restart. Quick diff of a working version (I'm not capturing STDERR but one can with "2>&1") === BEGIN PATCH === *** .brk-resolved-20191027 2019-10-27 11:19:56.210069032 +1030 --- resolved2019-10-27 11:30:17.156381734 +1030 *** *** 30,36 mkdir -p $statedir oldstate="$(mktemp)" ! md5sum $statedir/isc-dhcp-v4-$interface.conf $statedir/isc-dhcp-v6-$interface.conf &> $oldstate if [ -n "$new_domain_name_servers" ] ; then cat <$statedir/isc-dhcp-v4-$interface.conf [Resolve] --- 30,36 mkdir -p $statedir oldstate="$(mktemp)" ! md5sum $statedir/isc-dhcp-v4-$interface.conf $statedir/isc-dhcp-v6-$interface.conf > $oldstate if [ -n "$new_domain_name_servers" ] ; then cat <$statedir/isc-dhcp-v4-$interface.conf [Resolve] *** *** 55,61 fi newstate="$(mktemp)" ! md5sum $statedir/isc-dhcp-v4-$interface.conf $statedir/isc-dhcp-v6-$interface.conf &> $newstate if ! cmp $oldstate $newstate; then systemctl try-reload-or-restart systemd-resolved.service fi --- 55,61 fi newstate="$(mktemp)" ! md5sum $statedir/isc-dhcp-v4-$interface.conf $statedir/isc-dhcp-v6-$interface.conf > $newstate if ! cmp $oldstate $newstate; then systemctl try-reload-or-restart systemd-resolved.service fi === END PATCH === Also, the script removes the script removes the $oldstate file but doesn't remove the $newstate file. Not sure how this made it through QA testing... But breaking DHCP client shouldn't happen like this. ivan. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: network-manager 1.20.4-2ubuntu2 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 Date: Sun Oct 27 11:48:33 2019 InstallationDate: Installed on 2017-04-21 (918 days ago) InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 (20170412) IpRoute: default via 172.16.1.14 dev enp0s5 150.101.89.32/28 dev enp0s5 scope link 169.254.0.0/16 dev enp0s5 scope link metric 1000 172.16.1.0/24 dev enp0s5 proto kernel scope link src 172.16.1.120 IwConfig: lono wireless extensions. enp0s5no wireless extensions. NetworkManager.state: [main] NetworkingEnabled=false WirelessEnabled=true WWANEnabled=true ProcEnviron: LANGUAGE=en_AU:en TERM=vt100 PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash RfKill: SourcePackage: network-manager UpgradeStatus: Upgraded to eoan on 2019-10-26 (0 days ago) nmcli-con: nmcli-dev: DEVICE TYPE STATE IP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH enp0s5 ethernet unmanaged unknown unknown /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged unknown unknown /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.20.4 connected started unknown disabledenabled enabled enabled enabled ** Affects: systemd (Ubun
[Desktop-packages] [Bug 1792085] Re: MTP not working/very slow on Bionic
Same problem on Ubuntu 18.04.3 LTS. ls hangs in /run/user/1000/gvfs/mtp:host=... . -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1792085 Title: MTP not working/very slow on Bionic Status in libmtp: New Status in gvfs package in Ubuntu: Incomplete Bug description: Hi, unfortunately (for me) MTP android devices no more work on Ubuntu 18.04. I have used MTP on 16.04 without problems, but on 18.04 it does not work. When I connect my Android devices (Samsung A5 and Samsung J3) and I try to list directories with many files (e.g. /DCIM/Camera) the window hangs until I disconnect the device. Same issue if I try to post the command "ls /var/run/1000/gvfs/". I have installed Ubuntu 18.04 on two different machines - an older HP laptop and a recent DELL laptop - and the issue is present on the all of them. I suspect a defect on the "libmtp". I tried many alternative solutions suggested by the net (e.g. jmtpfs and so on) but anyone worked. That's all! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gvfs-fuse 1.36.1-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME Date: Wed Sep 12 06:20:07 2018 LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/libmtp/+bug/1792085/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1848090] Re: [snap] Unable to install Extensions
I have tested further installing the Chromium snap in Kubuntu and Xubuntu. Both allow me to install extensions. My Ubuntu install still has the issue. ~/snap/chromium/current/ has a symbolic link to ~/snap/chromium/861 which is empty All folders under ~/snap/chromium/ (861, 881, and common) are empty Permissions are 755 to ~/snap/chromium/861, ~/snap/chromium/881, and ~/snap/chromium/common and 777 to ~/snap/chromium/current -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1848090 Title: [snap] Unable to install Extensions Status in chromium-browser package in Ubuntu: Incomplete Bug description: When attempting to install an extension in the Snap version of Chromium I'm presented with an error message "An error has occurred Could not create download directory" Steps to recreate: Menu > More tools > Extensions Select any extension to install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1848090/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1848090] [NEW] [snap] Unable to install Extensions
Public bug reported: When attempting to install an extension in the Snap version of Chromium I'm presented with an error message "An error has occurred Could not create download directory" Steps to recreate: Menu > More tools > Extensions Select any extension to install ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: snap ** Attachment added: "Screenshot from 2019-10-14 21-13-20.png" https://bugs.launchpad.net/bugs/1848090/+attachment/5297149/+files/Screenshot%20from%202019-10-14%2021-13-20.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1848090 Title: [snap] Unable to install Extensions Status in chromium-browser package in Ubuntu: New Bug description: When attempting to install an extension in the Snap version of Chromium I'm presented with an error message "An error has occurred Could not create download directory" Steps to recreate: Menu > More tools > Extensions Select any extension to install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1848090/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1801540]
Gigabyte X470 AORUS ULTRA ALC1220, [1022:1457] subsys [1458:a0c3] Test Fis Patch no.5 on kernel 5.1.5: - sound playback OK - sound recording OK ( crackling disappeared ) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1801540 Title: Microphone distorted sound on ALC892/1220 on AMD chipsets Status in Linux: Confirmed Status in linux package in Ubuntu: Won't Fix Status in pulseaudio package in Ubuntu: Won't Fix Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1801540/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1580123] Re: xrandr --scale (again) confines mouse to native solution
VMWare has this cursor issue -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1580123 Title: xrandr --scale (again) confines mouse to native solution Status in X.Org X server: Fix Released Status in xorg-server package in Ubuntu: Confirmed Bug description: This might be a regression where the original issue is: https://bugs.launchpad.net/xorg-server/+bug/883319 It can be easily reproduced by doing something like: xrandr --output DP1 --scale 1.25x1.25 The mouse will be still constrained to the native solution (aka you can't move the mouse outside a box of whatever DP1 had as resolution before. $ lsb_release -rd Description: Ubuntu 16.04 LTS Release: 16.04 $ xrandr --version xrandr program version 1.5.0 Server reports RandR version 1.5 $ apt-cache policy xserver-xorg-core xserver-xorg-core: Installed: 2:1.18.3-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1580123/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1813701] Re: [amdgpu] Flickering graphics corruption (but none observed in kernels 4.18.10-4.18.12)
and https://bugs.freedesktop.org/show_bug.cgi?id=102646 ** Bug watch added: freedesktop.org Bugzilla #102646 https://bugs.freedesktop.org/show_bug.cgi?id=102646 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1813701 Title: [amdgpu] Flickering graphics corruption (but none observed in kernels 4.18.10-4.18.12) Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: The screen always flickers at a frequency of 75 GHz on the AMD RX 580 gpu. At 60 and 50 GHz, if you switch to any other than 75, the flickering will disappear until the display turns off. After switching on, flicker returns. At the core of 4.18.0-10, just like on the AMD Radeon HD7970 gpu, the problem is not visible. More in the video https://www.youtube.com/watch?v=d_LXHqWKTbk ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 29 13:13:19 2019 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X] [1002:67df] (rev e7) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Ellesmere [Radeon RX 470/480/570/570X/580/580X] [1043:0519] InstallationDate: Installed on 2019-01-22 (6 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: MSI MS-7693 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=ad22bc6d-c4e8-4393-a30b-6c247159b9dd ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/08/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V10.6 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 970A-G43 (MS-7693) dmi.board.vendor: MSI dmi.board.version: 3.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 3.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV10.6:bd01/08/2016:svnMSI:pnMS-7693:pvr3.0:rvnMSI:rn970A-G43(MS-7693):rvr3.0:cvnMSI:ct3:cvr3.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7693 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 3.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97+git1901221830.b7a7a9~oibaf~c version.libgl1-mesa-dri: libgl1-mesa-dri 19.0~git1901280730.d1d2bb~oibaf~c version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813701/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1813701] Re: [amdgpu] Flickering graphics corruption (but none observed in kernels 4.18.10-4.18.12)
has already https://bugs.freedesktop.org/show_bug.cgi?id=110199 ** Bug watch added: freedesktop.org Bugzilla #110199 https://bugs.freedesktop.org/show_bug.cgi?id=110199 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1813701 Title: [amdgpu] Flickering graphics corruption (but none observed in kernels 4.18.10-4.18.12) Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: The screen always flickers at a frequency of 75 GHz on the AMD RX 580 gpu. At 60 and 50 GHz, if you switch to any other than 75, the flickering will disappear until the display turns off. After switching on, flicker returns. At the core of 4.18.0-10, just like on the AMD Radeon HD7970 gpu, the problem is not visible. More in the video https://www.youtube.com/watch?v=d_LXHqWKTbk ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 29 13:13:19 2019 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X] [1002:67df] (rev e7) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Ellesmere [Radeon RX 470/480/570/570X/580/580X] [1043:0519] InstallationDate: Installed on 2019-01-22 (6 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: MSI MS-7693 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=ad22bc6d-c4e8-4393-a30b-6c247159b9dd ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/08/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V10.6 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 970A-G43 (MS-7693) dmi.board.vendor: MSI dmi.board.version: 3.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 3.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV10.6:bd01/08/2016:svnMSI:pnMS-7693:pvr3.0:rvnMSI:rn970A-G43(MS-7693):rvr3.0:cvnMSI:ct3:cvr3.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7693 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 3.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97+git1901221830.b7a7a9~oibaf~c version.libgl1-mesa-dri: libgl1-mesa-dri 19.0~git1901280730.d1d2bb~oibaf~c version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813701/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1813701] Re: [amdgpu] Flickering graphics corruption (but none observed in kernels 4.18.10-4.18.12)
Ok, I found a problem commit. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-4.18.y=d9ef158adf04b81772a7e9d682a054614ebac2fd -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1813701 Title: [amdgpu] Flickering graphics corruption (but none observed in kernels 4.18.10-4.18.12) Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: The screen always flickers at a frequency of 75 GHz on the AMD RX 580 gpu. At 60 and 50 GHz, if you switch to any other than 75, the flickering will disappear until the display turns off. After switching on, flicker returns. At the core of 4.18.0-10, just like on the AMD Radeon HD7970 gpu, the problem is not visible. More in the video https://www.youtube.com/watch?v=d_LXHqWKTbk ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 29 13:13:19 2019 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X] [1002:67df] (rev e7) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Ellesmere [Radeon RX 470/480/570/570X/580/580X] [1043:0519] InstallationDate: Installed on 2019-01-22 (6 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: MSI MS-7693 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=ad22bc6d-c4e8-4393-a30b-6c247159b9dd ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/08/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V10.6 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 970A-G43 (MS-7693) dmi.board.vendor: MSI dmi.board.version: 3.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 3.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV10.6:bd01/08/2016:svnMSI:pnMS-7693:pvr3.0:rvnMSI:rn970A-G43(MS-7693):rvr3.0:cvnMSI:ct3:cvr3.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7693 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 3.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97+git1901221830.b7a7a9~oibaf~c version.libgl1-mesa-dri: libgl1-mesa-dri 19.0~git1901280730.d1d2bb~oibaf~c version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813701/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1813701] Re: [amdgpu] Flickering graphics corruption (but none observed in kernels 4.18.10-4.18.12)
But following the description, the commit canceled the previous patch due to some problems. I think you need a more detailed study of the problem -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1813701 Title: [amdgpu] Flickering graphics corruption (but none observed in kernels 4.18.10-4.18.12) Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: The screen always flickers at a frequency of 75 GHz on the AMD RX 580 gpu. At 60 and 50 GHz, if you switch to any other than 75, the flickering will disappear until the display turns off. After switching on, flicker returns. At the core of 4.18.0-10, just like on the AMD Radeon HD7970 gpu, the problem is not visible. More in the video https://www.youtube.com/watch?v=d_LXHqWKTbk ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 29 13:13:19 2019 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X] [1002:67df] (rev e7) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Ellesmere [Radeon RX 470/480/570/570X/580/580X] [1043:0519] InstallationDate: Installed on 2019-01-22 (6 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: MSI MS-7693 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=ad22bc6d-c4e8-4393-a30b-6c247159b9dd ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/08/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V10.6 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 970A-G43 (MS-7693) dmi.board.vendor: MSI dmi.board.version: 3.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 3.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV10.6:bd01/08/2016:svnMSI:pnMS-7693:pvr3.0:rvnMSI:rn970A-G43(MS-7693):rvr3.0:cvnMSI:ct3:cvr3.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7693 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 3.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97+git1901221830.b7a7a9~oibaf~c version.libgl1-mesa-dri: libgl1-mesa-dri 19.0~git1901280730.d1d2bb~oibaf~c version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813701/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1716857] Re: gdm3, hybrid nvidia with modeset=1, no external monitors detected
Forgot to add: Ubuntu 18.04.2 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1716857 Title: gdm3, hybrid nvidia with modeset=1, no external monitors detected Status in gdm3 package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in gdm3 package in Debian: New Bug description: Context: 17.10 development packages, nvidia binary driver 375, modeset=1 for the nvidia driver. ubuntu desktop (gnome shell), fresh install ThinkPad W520 in Nvidia Optimus bios mode. Nvidia profile. Result: no external monitors are detected. xrandr does not even list them as disconnected (normally it would list five external disconnected monitors) lsmod shows that nvidia driver is loaded and the modesetting is working at some level because there is no tearing on the laptop panel Note: modeset=1 is the only way to get flicker-free graphics on the laptop panel. modeset=1 is not the default setting but it is highly desirable. It works if lightdm is used which is why I have reported this against gdm3 My sessions in this configuration have mostly crashed after a few minutes with a gdm3 fail whale message in syslog but nothing else looks interesting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1716857] Re: gdm3, hybrid nvidia with modeset=1, no external monitors detected
I confirm the bug exists and workarounds work, both with lightdm and ExecStartPre line. Also, adding xinit to ExecStartPre messes up suspend functionality. That is a pity... Laptop: Thinkpad P1 with nvidia graphics -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1716857 Title: gdm3, hybrid nvidia with modeset=1, no external monitors detected Status in gdm3 package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in gdm3 package in Debian: New Bug description: Context: 17.10 development packages, nvidia binary driver 375, modeset=1 for the nvidia driver. ubuntu desktop (gnome shell), fresh install ThinkPad W520 in Nvidia Optimus bios mode. Nvidia profile. Result: no external monitors are detected. xrandr does not even list them as disconnected (normally it would list five external disconnected monitors) lsmod shows that nvidia driver is loaded and the modesetting is working at some level because there is no tearing on the laptop panel Note: modeset=1 is the only way to get flicker-free graphics on the laptop panel. modeset=1 is not the default setting but it is highly desirable. It works if lightdm is used which is why I have reported this against gdm3 My sessions in this configuration have mostly crashed after a few minutes with a gdm3 fail whale message in syslog but nothing else looks interesting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1821108] [NEW] vga error when discconect and connect
Public bug reported: I have a HP elitebook G1. My problem appears when I disconnect the VGA cable, I can not display anything until reboot my computer each one! please, help!! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME Date: Wed Mar 20 18:16:25 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.18, 4.15.0-45-generic, x86_64: installed virtualbox, 5.2.18, 4.15.0-46-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics Controller [103c:198f] InstallationDate: Installed on 2018-07-12 (251 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Hewlett-Packard HP EliteBook 840 G1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-46-generic root=UUID=18907507-7e23-4e57-83f5-17b3ee3bc36a ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/12/2018 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L71 Ver. 01.44 dmi.board.name: 198F dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 15.59 dmi.chassis.asset.tag: CNU42897DP dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL71Ver.01.44:bd04/12/2018:svnHewlett-Packard:pnHPEliteBook840G1:pvrA3009DD10203:rvnHewlett-Packard:rn198F:rvrKBCVersion15.59:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP EliteBook 840 G1 dmi.product.version: A3009DD10203 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1821108 Title: vga error when discconect and connect Status in xorg package in Ubuntu: New Bug description: I have a HP elitebook G1. My problem appears when I disconnect the VGA cable, I can not display anything until reboot my computer each one! please, help!! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME Date: Wed Mar 20 18:16:25 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.18, 4.15.0-45-generic, x86_64: installed virtualbox, 5.2.18, 4.15.0-46-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics Controller [103c:198f] InstallationDate: Installed on 2018-07-12 (251 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Hewlett-Packard HP EliteBook 840 G1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-46-generic root=UUID=18907507-7e23-4e57-83f5-17b3ee3bc36a ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/12/2018 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L71 Ver. 01.44 dmi.board.name: 198F dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 15.59 dmi.chassis.asset.tag: CNU42897DP dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias:
[Desktop-packages] [Bug 1813701] Re: [amdgpu] Flickering graphics corruption (but none observed in kernels 4.18.10-4.18.12)
Why look for -rc? if there is no problem only in the kernel version 4.18. (10, 11, 12), in all other kernel versions 4.18 there is a bug -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1813701 Title: [amdgpu] Flickering graphics corruption (but none observed in kernels 4.18.10-4.18.12) Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: The screen always flickers at a frequency of 75 GHz on the AMD RX 580 gpu. At 60 and 50 GHz, if you switch to any other than 75, the flickering will disappear until the display turns off. After switching on, flicker returns. At the core of 4.18.0-10, just like on the AMD Radeon HD7970 gpu, the problem is not visible. More in the video https://www.youtube.com/watch?v=d_LXHqWKTbk ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 29 13:13:19 2019 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X] [1002:67df] (rev e7) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Ellesmere [Radeon RX 470/480/570/570X/580/580X] [1043:0519] InstallationDate: Installed on 2019-01-22 (6 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: MSI MS-7693 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=ad22bc6d-c4e8-4393-a30b-6c247159b9dd ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/08/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V10.6 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 970A-G43 (MS-7693) dmi.board.vendor: MSI dmi.board.version: 3.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 3.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV10.6:bd01/08/2016:svnMSI:pnMS-7693:pvr3.0:rvnMSI:rn970A-G43(MS-7693):rvr3.0:cvnMSI:ct3:cvr3.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7693 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 3.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97+git1901221830.b7a7a9~oibaf~c version.libgl1-mesa-dri: libgl1-mesa-dri 19.0~git1901280730.d1d2bb~oibaf~c version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813701/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1813701] Re: [amdgpu] Flickering graphics corruption (but none observed in kernels 4.18.10-4.18.12)
I tried the v5.0-rc7 and rc8 kernels. the problem is not solved ** Tags added: kernel-bug-exists-upstream -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1813701 Title: [amdgpu] Flickering graphics corruption (but none observed in kernels 4.18.10-4.18.12) Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: The screen always flickers at a frequency of 75 GHz on the AMD RX 580 gpu. At 60 and 50 GHz, if you switch to any other than 75, the flickering will disappear until the display turns off. After switching on, flicker returns. At the core of 4.18.0-10, just like on the AMD Radeon HD7970 gpu, the problem is not visible. More in the video https://www.youtube.com/watch?v=d_LXHqWKTbk ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 29 13:13:19 2019 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X] [1002:67df] (rev e7) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Ellesmere [Radeon RX 470/480/570/570X/580/580X] [1043:0519] InstallationDate: Installed on 2019-01-22 (6 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: MSI MS-7693 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=ad22bc6d-c4e8-4393-a30b-6c247159b9dd ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/08/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V10.6 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 970A-G43 (MS-7693) dmi.board.vendor: MSI dmi.board.version: 3.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 3.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV10.6:bd01/08/2016:svnMSI:pnMS-7693:pvr3.0:rvnMSI:rn970A-G43(MS-7693):rvr3.0:cvnMSI:ct3:cvr3.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7693 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 3.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97+git1901221830.b7a7a9~oibaf~c version.libgl1-mesa-dri: libgl1-mesa-dri 19.0~git1901280730.d1d2bb~oibaf~c version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813701/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1813701] Re: [amdgpu] Flickering graphics corruption in kernel 4.18.0-13.14-generic 4.18.17 (but none observed in kernel 4.18.0-10)
I rechecked all kernels of version 4.18 again. No bug kernels only: 4.18.0-10-generic #11-Ubuntu SMP Thu Oct 11 15:13:55 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux 4.18.12-041812-generic #201810032137 SMP Thu Oct 4 01:39:48 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux 4.18.11-041811-generic #201809290731 SMP Sat Sep 29 11:33:39 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux 4.18.10-041810-generic #201809260332 SMP Wed Sep 26 07:34:01 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux On all others starting 4.18.1 ending 4.18.20 there is a bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1813701 Title: [amdgpu] Flickering graphics corruption in kernel 4.18.0-13.14-generic 4.18.17 (but none observed in kernel 4.18.0-10) Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-video-amdgpu package in Ubuntu: Incomplete Bug description: The screen always flickers at a frequency of 75 GHz on the AMD RX 580 gpu. At 60 and 50 GHz, if you switch to any other than 75, the flickering will disappear until the display turns off. After switching on, flicker returns. At the core of 4.18.0-10, just like on the AMD Radeon HD7970 gpu, the problem is not visible. More in the video https://www.youtube.com/watch?v=d_LXHqWKTbk ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 29 13:13:19 2019 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X] [1002:67df] (rev e7) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Ellesmere [Radeon RX 470/480/570/570X/580/580X] [1043:0519] InstallationDate: Installed on 2019-01-22 (6 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: MSI MS-7693 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=ad22bc6d-c4e8-4393-a30b-6c247159b9dd ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/08/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V10.6 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 970A-G43 (MS-7693) dmi.board.vendor: MSI dmi.board.version: 3.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 3.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV10.6:bd01/08/2016:svnMSI:pnMS-7693:pvr3.0:rvnMSI:rn970A-G43(MS-7693):rvr3.0:cvnMSI:ct3:cvr3.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7693 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 3.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97+git1901221830.b7a7a9~oibaf~c version.libgl1-mesa-dri: libgl1-mesa-dri 19.0~git1901280730.d1d2bb~oibaf~c version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813701/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1813701] Re: [amdgpu] Flickering graphics corruption in kernel 4.18.0-13.14-generic 4.18.17 (but none observed in kernel 4.18.0-10)
Ok, I consistently checked the kernels from version 10.18.20 to 10.18.10. There is no bug at 10.18.10. If you need it later, I can check on versions from 10.18.9 to 10.18.1. What need to provide logs on the working core? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1813701 Title: [amdgpu] Flickering graphics corruption in kernel 4.18.0-13.14-generic 4.18.17 (but none observed in kernel 4.18.0-10) Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-video-amdgpu package in Ubuntu: Incomplete Bug description: The screen always flickers at a frequency of 75 GHz on the AMD RX 580 gpu. At 60 and 50 GHz, if you switch to any other than 75, the flickering will disappear until the display turns off. After switching on, flicker returns. At the core of 4.18.0-10, just like on the AMD Radeon HD7970 gpu, the problem is not visible. More in the video https://www.youtube.com/watch?v=d_LXHqWKTbk ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 29 13:13:19 2019 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X] [1002:67df] (rev e7) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Ellesmere [Radeon RX 470/480/570/570X/580/580X] [1043:0519] InstallationDate: Installed on 2019-01-22 (6 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: MSI MS-7693 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=ad22bc6d-c4e8-4393-a30b-6c247159b9dd ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/08/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V10.6 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 970A-G43 (MS-7693) dmi.board.vendor: MSI dmi.board.version: 3.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 3.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV10.6:bd01/08/2016:svnMSI:pnMS-7693:pvr3.0:rvnMSI:rn970A-G43(MS-7693):rvr3.0:cvnMSI:ct3:cvr3.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7693 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 3.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97+git1901221830.b7a7a9~oibaf~c version.libgl1-mesa-dri: libgl1-mesa-dri 19.0~git1901280730.d1d2bb~oibaf~c version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813701/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
