[Desktop-packages] [Bug 2011404] Re: vanilla-gnome-desktop depends on pulseaudio which conflicts with pipewire
** Tags added: noble -- 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/2011404 Title: vanilla-gnome-desktop depends on pulseaudio which conflicts with pipewire Status in pipewire package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Status in ubuntu-gnome-meta package in Ubuntu: Confirmed Bug description: Package vanilla-gnome-desktop 0.97 depends on pulseaudio which conflicts with pipewire-alsa and pipewire-audio which in turn are required for upgrading gnome to version 43. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/2011404/+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 2055006] [NEW] Xorg crash
Public bug reported: happens when I start wine. Checked /var/log/syslog and noticed GNOME Shell crashed with signal 5 reproduction : start wine. System slows, then crashes and asks me to relog . After that extensions are disabled, same issue I tried to change the nvidia drivers since there are some warning in dmesg ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-21.21-generic 6.5.8 Uname: Linux 6.5.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.154.05 Thu Dec 28 15:37:48 UTC 2023 GCC version: ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Feb 26 07:32:22 2024 DistUpgraded: 2023-12-12 18:06:14,008 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: mantic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GA104 [GeForce RTX 3070 Ti] [10de:2482] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GA104 [GeForce RTX 3070 Ti] [1458:408f] InstallationDate: Installed on 2022-12-22 (430 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']} ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-21-generic root=UUID=6bb46864-3883-4516-a1d5-eda3cd8908a7 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to mantic on 2023-12-12 (76 days ago) dmi.bios.date: 11/15/2022 dmi.bios.release: 5.27 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F21 dmi.board.asset.tag: Default string dmi.board.name: B660 GAMING X DDR4 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF21:bd11/15/2022:br5.27:svnMATERIEL.NET:pnBLACKBIRD:pvrV1:rvnGigabyteTechnologyCo.,Ltd.:rnB660GAMINGXDDR4:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuAR202209190058: dmi.product.family: CMA dmi.product.name: BLACKBIRD dmi.product.sku: AR202209190058 dmi.product.version: V1 dmi.sys.vendor: MATERIEL.NET version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.115-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 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 crash mantic 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/2055006 Title: Xorg crash Status in xorg package in Ubuntu: New Bug description: happens when I start wine. Checked /var/log/syslog and noticed GNOME Shell crashed with signal 5 reproduction : start wine. System slows, then crashes and asks me to relog . After that extensions are disabled, same issue I tried to change the nvidia drivers since there are some warning in dmesg ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-21.21-generic 6.5.8 Uname: Linux 6.5.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.154.05 Thu Dec 28 15:37:48 UTC 2023 GCC version: ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 BootLog: Error: [Errno 13]
[Desktop-packages] [Bug 2050850] [NEW] Selected encoding not taken into account when saving
Public bug reported: The file is saved in utf-8 even though I select iso-8859-1 as encoding when saving. Steps to reproduce: 1. Create a new file with non-ascii content, eg.: "çéè" (without quotes) 2. In the save dialog, select iso-8859-1 encoding 2. Check file size: it should be 3 bytes, but it is 7. Hexdump: c3 a7 c3 a9 c3 a8 0a |...| 0007 For instance, c3 a7 is the utf-8 encoding of "ç". The iso-8859-1 encoding of this char is the single byte e7. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-text-editor 45.1-1build1 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Tue Jan 23 00:30:01 2024 InstallationDate: Installed on 2018-12-14 (1866 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: gnome-text-editor UpgradeStatus: Upgraded to noble on 2023-11-07 (76 days ago) ** Affects: gnome-text-editor (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble wayland-session ** Summary changed: - Selected encoding not taken into account + Selected encoding not taken into account when saving -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-text-editor in Ubuntu. https://bugs.launchpad.net/bugs/2050850 Title: Selected encoding not taken into account when saving Status in gnome-text-editor package in Ubuntu: New Bug description: The file is saved in utf-8 even though I select iso-8859-1 as encoding when saving. Steps to reproduce: 1. Create a new file with non-ascii content, eg.: "çéè" (without quotes) 2. In the save dialog, select iso-8859-1 encoding 2. Check file size: it should be 3 bytes, but it is 7. Hexdump: c3 a7 c3 a9 c3 a8 0a |...| 0007 For instance, c3 a7 is the utf-8 encoding of "ç". The iso-8859-1 encoding of this char is the single byte e7. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-text-editor 45.1-1build1 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Tue Jan 23 00:30:01 2024 InstallationDate: Installed on 2018-12-14 (1866 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: gnome-text-editor UpgradeStatus: Upgraded to noble on 2023-11-07 (76 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-text-editor/+bug/2050850/+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 2023044] Re: New thumbnails are missing from file chooser
Just found this thread on the issue: https://discussion.fedoraproject.org/t/problem-with-new-file-picker-thumbnails-are-not-loaded/80073 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk4 in Ubuntu. https://bugs.launchpad.net/bugs/2023044 Title: New thumbnails are missing from file chooser Status in GTK+: New Status in gtk4 package in Ubuntu: Triaged Bug description: Impact -- Thumbnails do not show in the file chooser (provided by gtk4 which is also used by even non-GTK3 apps if they use xdg-desktop-portal-gnome) until the thumbnail is generated by for instance, viewing the folder in Nautilus. This bug is new to Ubuntu 23.04 because GTK 4.10 is the first stable GTK release to support the "grid view" in the filechooser. Test Case - 1. Use Firefox to download an image file. (This test case assumes you're using the default Firefox distributed as a Snap). 2. In Firefox, use the keyboard shortcut Ctrl+O to open the file chooser. 3. Navigate to where the file was downloaded (your Downloads/ folder?) 4. The file should show a thumbnail image Number 4 doesn't happen correctly until you open the folder in Nautilus at least once. Other Info -- I am linking to what upstream considers the master bug for this issue. But a duplicate of the issue is https://gitlab.gnome.org/GNOME/gtk/-/issues/5663 which has a clearer summary. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/2023044/+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 2023044] Re: New thumbnails are missing from file chooser
I've noticed it on 23.10 too. I think that the file picker does not GENERATE thumbnails. If thumbnails are generated beforehands by Nautilus, they get displayed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk4 in Ubuntu. https://bugs.launchpad.net/bugs/2023044 Title: New thumbnails are missing from file chooser Status in GTK+: New Status in gtk4 package in Ubuntu: Triaged Bug description: Impact -- Thumbnails do not show in the file chooser (provided by gtk4 which is also used by even non-GTK3 apps if they use xdg-desktop-portal-gnome) until the thumbnail is generated by for instance, viewing the folder in Nautilus. This bug is new to Ubuntu 23.04 because GTK 4.10 is the first stable GTK release to support the "grid view" in the filechooser. Test Case - 1. Use Firefox to download an image file. (This test case assumes you're using the default Firefox distributed as a Snap). 2. In Firefox, use the keyboard shortcut Ctrl+O to open the file chooser. 3. Navigate to where the file was downloaded (your Downloads/ folder?) 4. The file should show a thumbnail image Number 4 doesn't happen correctly until you open the folder in Nautilus at least once. Other Info -- I am linking to what upstream considers the master bug for this issue. But a duplicate of the issue is https://gitlab.gnome.org/GNOME/gtk/-/issues/5663 which has a clearer summary. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/2023044/+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 2025527] Re: nautilus segfault
upgraded ubuntu to 23.04 . got a lot more bugs but this one seems fixed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2025527 Title: nautilus segfault Status in nautilus package in Ubuntu: New Bug description: Later ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-47.49-generic 5.19.17 Uname: Linux 5.19.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jul 1 10:20:46 2023 GsettingsChanges: b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2022-12-22 (190 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 43.0-1 nautilus-dropbox 2019.02.14-1.2 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2025527/+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 2025527] Re: nautilus segfault
seems clone of https://gitlab.gnome.org/GNOME/pango/-/issues/715 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2025527 Title: nautilus segfault Status in nautilus package in Ubuntu: New Bug description: Later ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-47.49-generic 5.19.17 Uname: Linux 5.19.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jul 1 10:20:46 2023 GsettingsChanges: b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2022-12-22 (190 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 43.0-1 nautilus-dropbox 2019.02.14-1.2 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2025527/+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 2025527] Re: nautilus segfault
looking in /var/log/syslog kernel: [ 1272.348057] nautilus[10457]: segfault at 0 ip 7fcbf4e57ea6 sp 7ffcb4373be0 error 4 in libpango-1.0.so.0.5000.10[7fcbf4e4+37000] kernel: [ 1272.348095] Code: 55 89 f5 53 48 83 ec 70 64 48 8b 04 25 28 00 00 00 48 89 44 24 68 31 c0 49 89 e4 4c 89 e6 e8 a1 b0 00 00 48 8b 5c 24 10 31 c0 <48> 83 3b 00 75 43 e9 df 00 00 00 0f 1f 80 00 00 00 00 4c 89 ea 31 ** Bug watch added: gitlab.gnome.org/GNOME/pango/-/issues #715 https://gitlab.gnome.org/GNOME/pango/-/issues/715 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2025527 Title: nautilus segfault Status in nautilus package in Ubuntu: New Bug description: Later ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-47.49-generic 5.19.17 Uname: Linux 5.19.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jul 1 10:20:46 2023 GsettingsChanges: b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2022-12-22 (190 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 43.0-1 nautilus-dropbox 2019.02.14-1.2 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2025527/+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 2025527] Re: nautilus segfault
I tried to debug. using > G_DEBUG="all" NAUTILUS_DEBUG="All" nautilus . lead to instant crash Using > NAUTILUS_DEBUG="All" nautilus . nothing of value was visible, same bug Using > G_MESSAGES_DEBUG=all nautilus . >> ~/Desktop/trace_nautilus.log I had a bit more information but nothing related to the crash -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2025527 Title: nautilus segfault Status in nautilus package in Ubuntu: New Bug description: Later ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-47.49-generic 5.19.17 Uname: Linux 5.19.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jul 1 10:20:46 2023 GsettingsChanges: b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2022-12-22 (190 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 43.0-1 nautilus-dropbox 2019.02.14-1.2 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2025527/+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 2025527] Re: nautilus segfault
description : 1. I created a new file named .txt in my templates. Created it with contextual menu okay. This leads to file ".txt" created . 2. I right click this file, rename ; then I press "leftarrow" three times and nautilus crashed. 3. open nautilus in console with "nautilus ." goto 2. got a Segmentation fault (core dumped) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2025527 Title: nautilus segfault Status in nautilus package in Ubuntu: New Bug description: Later ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-47.49-generic 5.19.17 Uname: Linux 5.19.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jul 1 10:20:46 2023 GsettingsChanges: b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2022-12-22 (190 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 43.0-1 nautilus-dropbox 2019.02.14-1.2 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2025527/+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 2025527] [NEW] nautilus segfault
Public bug reported: Later ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-47.49-generic 5.19.17 Uname: Linux 5.19.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jul 1 10:20:46 2023 GsettingsChanges: b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2022-12-22 (190 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 43.0-1 nautilus-dropbox 2019.02.14-1.2 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic third-party-packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2025527 Title: nautilus segfault Status in nautilus package in Ubuntu: New Bug description: Later ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-47.49-generic 5.19.17 Uname: Linux 5.19.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jul 1 10:20:46 2023 GsettingsChanges: b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2022-12-22 (190 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 43.0-1 nautilus-dropbox 2019.02.14-1.2 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2025527/+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 2015061] Re: [nvidia][lunar] Corrupted/missing windows title background when opening windows
This seems to have been fixed as of latest nvidia drivers or recent Ubuntu packages updates, at least I'm not observing it anymore since this weekend -- 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/2015061 Title: [nvidia][lunar] Corrupted/missing windows title background when opening windows Status in mutter package in Ubuntu: Confirmed Bug description: Since upgrading to Ubuntu 23.04 (from 22.10), the title bar of some apps are corrupted when the windows first open. As soon as I de-focus and re-focus them, the title bar starts working mostly correctly. You'll find a screenshot attached. Basically, the window just repeats the pattern of the edge, until it is de-focused, and then it will properly draw the "window inactive" background color. When the window is de-focused, clicking the title bar won't focus it, although double- clicking on it will maximize it. I need to click within the window body to focus it. Edit: Looking at the screenshot file, it seems like the screenshot even assumed the title bar was actually transparent (the alpha channel of the status bar is 0 in the screenshot!) All GNOME settings were reset using dconf after upgrade, and custom themes have been removed (this is all Yaru defaults). This is happening with almost all apps, including Terminator or Thunderbird. Gnome package versions: ii gir1.2-gnomeautoar-0.1:amd640.4.4-1 amd64GObject introspection data for GnomeAutoar ii gir1.2-gnomebg-4.0:amd6444.0-1 amd64Introspection data for GnomeBG (GTK 4) ii gir1.2-gnomebluetooth-3.0:amd64 42.5-3 amd64Introspection data for GnomeBluetooth ii gir1.2-gnomedesktop-3.0:amd64 44.0-1 amd64Introspection data for GnomeDesktop (GTK 3) ii gir1.2-gnomedesktop-4.0:amd64 44.0-1 amd64Introspection data for GnomeDesktop (GTK 4) ii gkbd-capplet3.28.1-1 amd64GNOME control center tools for libgnomekbd ii gnome-accessibility-themes 3.28-2ubuntu1 all High Contrast GTK 2 theme and icons ii gnome-bluetooth-3-common42.5-3 all GNOME Bluetooth 3 common files ii gnome-bluetooth-sendto 42.5-3 amd64GNOME Bluetooth Send To app ii gnome-calculator 1:44.0-1ubuntu1amd64 GNOME desktop calculator ii gnome-calendar 44.0-1 amd64Calendar application for GNOME ii gnome-characters44.0-1 amd64character map application ii gnome-control-center 1:44.0-1ubuntu4amd64 utilities to configure the GNOME desktop ii gnome-control-center-data 1:44.0-1ubuntu4all configuration applets for GNOME - data files ii gnome-control-center-faces 1:44.0-1ubuntu4all utilities to configure the GNOME desktop - faces images ii gnome-desktop3-data 44.0-1 all Common files for GNOME desktop apps ii gnome-disk-utility 44.0-1ubuntu1 amd64manage and configure disk drives and media ii gnome-font-viewer 44.0-1 amd64font viewer for GNOME ii gnome-initial-setup 44.0-1ubuntu1 amd64Initial GNOME system setup helper ii gnome-keyring 42.1-1
[Desktop-packages] [Bug 2015061] Re: [nvidia][lunar] Corrupted/missing windows title background when opening windows
Yup, I have seen a few (rare and random this time) crashes when pressing the Activities corner button (or super shortcut key). It indeed restarts quickly after that, but I assumed it was linked to https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968383 Let me know if I can provide any other info or help :) -- 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/2015061 Title: [nvidia][lunar] Corrupted/missing windows title background when opening windows Status in mutter package in Ubuntu: New Bug description: Since upgrading to Ubuntu 23.04 (from 22.10), the title bar of some apps are corrupted when the windows first open. As soon as I de-focus and re-focus them, the title bar starts working mostly correctly. You'll find a screenshot attached. Basically, the window just repeats the pattern of the edge, until it is de-focused, and then it will properly draw the "window inactive" background color. When the window is de-focused, clicking the title bar won't focus it, although double- clicking on it will maximize it. I need to click within the window body to focus it. Edit: Looking at the screenshot file, it seems like the screenshot even assumed the title bar was actually transparent (the alpha channel of the status bar is 0 in the screenshot!) All GNOME settings were reset using dconf after upgrade, and custom themes have been removed (this is all Yaru defaults). This is happening with almost all apps, including Terminator or Thunderbird. Gnome package versions: ii gir1.2-gnomeautoar-0.1:amd640.4.4-1 amd64GObject introspection data for GnomeAutoar ii gir1.2-gnomebg-4.0:amd6444.0-1 amd64Introspection data for GnomeBG (GTK 4) ii gir1.2-gnomebluetooth-3.0:amd64 42.5-3 amd64Introspection data for GnomeBluetooth ii gir1.2-gnomedesktop-3.0:amd64 44.0-1 amd64Introspection data for GnomeDesktop (GTK 3) ii gir1.2-gnomedesktop-4.0:amd64 44.0-1 amd64Introspection data for GnomeDesktop (GTK 4) ii gkbd-capplet3.28.1-1 amd64GNOME control center tools for libgnomekbd ii gnome-accessibility-themes 3.28-2ubuntu1 all High Contrast GTK 2 theme and icons ii gnome-bluetooth-3-common42.5-3 all GNOME Bluetooth 3 common files ii gnome-bluetooth-sendto 42.5-3 amd64GNOME Bluetooth Send To app ii gnome-calculator 1:44.0-1ubuntu1amd64 GNOME desktop calculator ii gnome-calendar 44.0-1 amd64Calendar application for GNOME ii gnome-characters44.0-1 amd64character map application ii gnome-control-center 1:44.0-1ubuntu4amd64 utilities to configure the GNOME desktop ii gnome-control-center-data 1:44.0-1ubuntu4all configuration applets for GNOME - data files ii gnome-control-center-faces 1:44.0-1ubuntu4all utilities to configure the GNOME desktop - faces images ii gnome-desktop3-data 44.0-1 all Common files for GNOME desktop apps ii gnome-disk-utility 44.0-1ubuntu1 amd64manage and configure disk drives and media ii gnome-font-viewer 44.0-1 amd64font viewer for GNOME ii gnome-initial-setup 44.0-1ubuntu1
[Desktop-packages] [Bug 2015061] Re: [nvidia][lunar] Corrupted/missing windows title background when opening windows
Output of lspci -k Please note that this happens consistently, it's not random or a rare occurrence. After boot, opening Thunderbird for example makes it lack the title bar background immediately. ** Attachment added: "lspcik.txt" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2015061/+attachment/5660750/+files/lspcik.txt -- 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/2015061 Title: [nvidia][lunar] Corrupted/missing windows title background when opening windows Status in mutter package in Ubuntu: Incomplete Bug description: Since upgrading to Ubuntu 23.04 (from 22.10), the title bar of some apps are corrupted when the windows first open. As soon as I de-focus and re-focus them, the title bar starts working mostly correctly. You'll find a screenshot attached. Basically, the window just repeats the pattern of the edge, until it is de-focused, and then it will properly draw the "window inactive" background color. When the window is de-focused, clicking the title bar won't focus it, although double- clicking on it will maximize it. I need to click within the window body to focus it. Edit: Looking at the screenshot file, it seems like the screenshot even assumed the title bar was actually transparent (the alpha channel of the status bar is 0 in the screenshot!) All GNOME settings were reset using dconf after upgrade, and custom themes have been removed (this is all Yaru defaults). This is happening with almost all apps, including Terminator or Thunderbird. Gnome package versions: ii gir1.2-gnomeautoar-0.1:amd640.4.4-1 amd64GObject introspection data for GnomeAutoar ii gir1.2-gnomebg-4.0:amd6444.0-1 amd64Introspection data for GnomeBG (GTK 4) ii gir1.2-gnomebluetooth-3.0:amd64 42.5-3 amd64Introspection data for GnomeBluetooth ii gir1.2-gnomedesktop-3.0:amd64 44.0-1 amd64Introspection data for GnomeDesktop (GTK 3) ii gir1.2-gnomedesktop-4.0:amd64 44.0-1 amd64Introspection data for GnomeDesktop (GTK 4) ii gkbd-capplet3.28.1-1 amd64GNOME control center tools for libgnomekbd ii gnome-accessibility-themes 3.28-2ubuntu1 all High Contrast GTK 2 theme and icons ii gnome-bluetooth-3-common42.5-3 all GNOME Bluetooth 3 common files ii gnome-bluetooth-sendto 42.5-3 amd64GNOME Bluetooth Send To app ii gnome-calculator 1:44.0-1ubuntu1amd64 GNOME desktop calculator ii gnome-calendar 44.0-1 amd64Calendar application for GNOME ii gnome-characters44.0-1 amd64character map application ii gnome-control-center 1:44.0-1ubuntu4amd64 utilities to configure the GNOME desktop ii gnome-control-center-data 1:44.0-1ubuntu4all configuration applets for GNOME - data files ii gnome-control-center-faces 1:44.0-1ubuntu4all utilities to configure the GNOME desktop - faces images ii gnome-desktop3-data 44.0-1 all Common files for GNOME desktop apps ii gnome-disk-utility 44.0-1ubuntu1 amd64manage and configure disk drives and media ii gnome-font-viewer 44.0-1 amd64font viewer for GNOME ii gnome-initial-setup
[Desktop-packages] [Bug 2015061] Re: [nvidia][lunar] Corrupted/missing windows title background when opening windows
Output of journalctl -b0 ** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2015061/+attachment/5660743/+files/journal.txt -- 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/2015061 Title: [nvidia][lunar] Corrupted/missing windows title background when opening windows Status in mutter package in Ubuntu: Incomplete Bug description: Since upgrading to Ubuntu 23.04 (from 22.10), the title bar of some apps are corrupted when the windows first open. As soon as I de-focus and re-focus them, the title bar starts working mostly correctly. You'll find a screenshot attached. Basically, the window just repeats the pattern of the edge, until it is de-focused, and then it will properly draw the "window inactive" background color. When the window is de-focused, clicking the title bar won't focus it, although double- clicking on it will maximize it. I need to click within the window body to focus it. Edit: Looking at the screenshot file, it seems like the screenshot even assumed the title bar was actually transparent (the alpha channel of the status bar is 0 in the screenshot!) All GNOME settings were reset using dconf after upgrade, and custom themes have been removed (this is all Yaru defaults). This is happening with almost all apps, including Terminator or Thunderbird. Gnome package versions: ii gir1.2-gnomeautoar-0.1:amd640.4.4-1 amd64GObject introspection data for GnomeAutoar ii gir1.2-gnomebg-4.0:amd6444.0-1 amd64Introspection data for GnomeBG (GTK 4) ii gir1.2-gnomebluetooth-3.0:amd64 42.5-3 amd64Introspection data for GnomeBluetooth ii gir1.2-gnomedesktop-3.0:amd64 44.0-1 amd64Introspection data for GnomeDesktop (GTK 3) ii gir1.2-gnomedesktop-4.0:amd64 44.0-1 amd64Introspection data for GnomeDesktop (GTK 4) ii gkbd-capplet3.28.1-1 amd64GNOME control center tools for libgnomekbd ii gnome-accessibility-themes 3.28-2ubuntu1 all High Contrast GTK 2 theme and icons ii gnome-bluetooth-3-common42.5-3 all GNOME Bluetooth 3 common files ii gnome-bluetooth-sendto 42.5-3 amd64GNOME Bluetooth Send To app ii gnome-calculator 1:44.0-1ubuntu1amd64 GNOME desktop calculator ii gnome-calendar 44.0-1 amd64Calendar application for GNOME ii gnome-characters44.0-1 amd64character map application ii gnome-control-center 1:44.0-1ubuntu4amd64 utilities to configure the GNOME desktop ii gnome-control-center-data 1:44.0-1ubuntu4all configuration applets for GNOME - data files ii gnome-control-center-faces 1:44.0-1ubuntu4all utilities to configure the GNOME desktop - faces images ii gnome-desktop3-data 44.0-1 all Common files for GNOME desktop apps ii gnome-disk-utility 44.0-1ubuntu1 amd64manage and configure disk drives and media ii gnome-font-viewer 44.0-1 amd64font viewer for GNOME ii gnome-initial-setup 44.0-1ubuntu1 amd64Initial GNOME system setup helper ii gnome-keyring
[Desktop-packages] [Bug 2015061] monitors.xml.txt
apport information ** Attachment added: "monitors.xml.txt" https://bugs.launchpad.net/bugs/2015061/+attachment/5660359/+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/2015061 Title: Corrupted/missing windows title background when opening windows Status in gnome-shell package in Ubuntu: Incomplete Bug description: Since upgrading to Ubuntu 23.04 (from 22.10), the title bar of some apps are corrupted when the windows first open. As soon as I de-focus and re-focus them, the title bar starts working mostly correctly. You'll find a screenshot attached. Basically, the window just repeats the pattern of the edge, until it is de-focused, and then it will properly draw the "window inactive" background color. When the window is de-focused, clicking the title bar won't focus it, although double- clicking on it will maximize it. I need to click within the window body to focus it. Edit: Looking at the screenshot file, it seems like the screenshot even assumed the title bar was actually transparent (the alpha channel of the status bar is 0 in the screenshot!) All GNOME settings were reset using dconf after upgrade, and custom themes have been removed (this is all Yaru defaults). This is happening with almost all apps, including Terminator or Thunderbird. Gnome package versions: ii gir1.2-gnomeautoar-0.1:amd640.4.4-1 amd64GObject introspection data for GnomeAutoar ii gir1.2-gnomebg-4.0:amd6444.0-1 amd64Introspection data for GnomeBG (GTK 4) ii gir1.2-gnomebluetooth-3.0:amd64 42.5-3 amd64Introspection data for GnomeBluetooth ii gir1.2-gnomedesktop-3.0:amd64 44.0-1 amd64Introspection data for GnomeDesktop (GTK 3) ii gir1.2-gnomedesktop-4.0:amd64 44.0-1 amd64Introspection data for GnomeDesktop (GTK 4) ii gkbd-capplet3.28.1-1 amd64GNOME control center tools for libgnomekbd ii gnome-accessibility-themes 3.28-2ubuntu1 all High Contrast GTK 2 theme and icons ii gnome-bluetooth-3-common42.5-3 all GNOME Bluetooth 3 common files ii gnome-bluetooth-sendto 42.5-3 amd64GNOME Bluetooth Send To app ii gnome-calculator 1:44.0-1ubuntu1amd64 GNOME desktop calculator ii gnome-calendar 44.0-1 amd64Calendar application for GNOME ii gnome-characters44.0-1 amd64character map application ii gnome-control-center 1:44.0-1ubuntu4amd64 utilities to configure the GNOME desktop ii gnome-control-center-data 1:44.0-1ubuntu4all configuration applets for GNOME - data files ii gnome-control-center-faces 1:44.0-1ubuntu4all utilities to configure the GNOME desktop - faces images ii gnome-desktop3-data 44.0-1 all Common files for GNOME desktop apps ii gnome-disk-utility 44.0-1ubuntu1 amd64manage and configure disk drives and media ii gnome-font-viewer 44.0-1 amd64font viewer for GNOME ii gnome-initial-setup 44.0-1ubuntu1 amd64Initial GNOME system setup helper ii gnome-keyring 42.1-1
[Desktop-packages] [Bug 2015061] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/2015061/+attachment/5660357/+files/ProcEnviron.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/2015061 Title: Corrupted/missing windows title background when opening windows Status in gnome-shell package in Ubuntu: Incomplete Bug description: Since upgrading to Ubuntu 23.04 (from 22.10), the title bar of some apps are corrupted when the windows first open. As soon as I de-focus and re-focus them, the title bar starts working mostly correctly. You'll find a screenshot attached. Basically, the window just repeats the pattern of the edge, until it is de-focused, and then it will properly draw the "window inactive" background color. When the window is de-focused, clicking the title bar won't focus it, although double- clicking on it will maximize it. I need to click within the window body to focus it. Edit: Looking at the screenshot file, it seems like the screenshot even assumed the title bar was actually transparent (the alpha channel of the status bar is 0 in the screenshot!) All GNOME settings were reset using dconf after upgrade, and custom themes have been removed (this is all Yaru defaults). This is happening with almost all apps, including Terminator or Thunderbird. Gnome package versions: ii gir1.2-gnomeautoar-0.1:amd640.4.4-1 amd64GObject introspection data for GnomeAutoar ii gir1.2-gnomebg-4.0:amd6444.0-1 amd64Introspection data for GnomeBG (GTK 4) ii gir1.2-gnomebluetooth-3.0:amd64 42.5-3 amd64Introspection data for GnomeBluetooth ii gir1.2-gnomedesktop-3.0:amd64 44.0-1 amd64Introspection data for GnomeDesktop (GTK 3) ii gir1.2-gnomedesktop-4.0:amd64 44.0-1 amd64Introspection data for GnomeDesktop (GTK 4) ii gkbd-capplet3.28.1-1 amd64GNOME control center tools for libgnomekbd ii gnome-accessibility-themes 3.28-2ubuntu1 all High Contrast GTK 2 theme and icons ii gnome-bluetooth-3-common42.5-3 all GNOME Bluetooth 3 common files ii gnome-bluetooth-sendto 42.5-3 amd64GNOME Bluetooth Send To app ii gnome-calculator 1:44.0-1ubuntu1amd64 GNOME desktop calculator ii gnome-calendar 44.0-1 amd64Calendar application for GNOME ii gnome-characters44.0-1 amd64character map application ii gnome-control-center 1:44.0-1ubuntu4amd64 utilities to configure the GNOME desktop ii gnome-control-center-data 1:44.0-1ubuntu4all configuration applets for GNOME - data files ii gnome-control-center-faces 1:44.0-1ubuntu4all utilities to configure the GNOME desktop - faces images ii gnome-desktop3-data 44.0-1 all Common files for GNOME desktop apps ii gnome-disk-utility 44.0-1ubuntu1 amd64manage and configure disk drives and media ii gnome-font-viewer 44.0-1 amd64font viewer for GNOME ii gnome-initial-setup 44.0-1ubuntu1 amd64Initial GNOME system setup helper ii gnome-keyring 42.1-1
[Desktop-packages] [Bug 2015061] ShellJournal.txt
apport information ** Attachment added: "ShellJournal.txt" https://bugs.launchpad.net/bugs/2015061/+attachment/5660358/+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/2015061 Title: Corrupted/missing windows title background when opening windows Status in gnome-shell package in Ubuntu: Incomplete Bug description: Since upgrading to Ubuntu 23.04 (from 22.10), the title bar of some apps are corrupted when the windows first open. As soon as I de-focus and re-focus them, the title bar starts working mostly correctly. You'll find a screenshot attached. Basically, the window just repeats the pattern of the edge, until it is de-focused, and then it will properly draw the "window inactive" background color. When the window is de-focused, clicking the title bar won't focus it, although double- clicking on it will maximize it. I need to click within the window body to focus it. Edit: Looking at the screenshot file, it seems like the screenshot even assumed the title bar was actually transparent (the alpha channel of the status bar is 0 in the screenshot!) All GNOME settings were reset using dconf after upgrade, and custom themes have been removed (this is all Yaru defaults). This is happening with almost all apps, including Terminator or Thunderbird. Gnome package versions: ii gir1.2-gnomeautoar-0.1:amd640.4.4-1 amd64GObject introspection data for GnomeAutoar ii gir1.2-gnomebg-4.0:amd6444.0-1 amd64Introspection data for GnomeBG (GTK 4) ii gir1.2-gnomebluetooth-3.0:amd64 42.5-3 amd64Introspection data for GnomeBluetooth ii gir1.2-gnomedesktop-3.0:amd64 44.0-1 amd64Introspection data for GnomeDesktop (GTK 3) ii gir1.2-gnomedesktop-4.0:amd64 44.0-1 amd64Introspection data for GnomeDesktop (GTK 4) ii gkbd-capplet3.28.1-1 amd64GNOME control center tools for libgnomekbd ii gnome-accessibility-themes 3.28-2ubuntu1 all High Contrast GTK 2 theme and icons ii gnome-bluetooth-3-common42.5-3 all GNOME Bluetooth 3 common files ii gnome-bluetooth-sendto 42.5-3 amd64GNOME Bluetooth Send To app ii gnome-calculator 1:44.0-1ubuntu1amd64 GNOME desktop calculator ii gnome-calendar 44.0-1 amd64Calendar application for GNOME ii gnome-characters44.0-1 amd64character map application ii gnome-control-center 1:44.0-1ubuntu4amd64 utilities to configure the GNOME desktop ii gnome-control-center-data 1:44.0-1ubuntu4all configuration applets for GNOME - data files ii gnome-control-center-faces 1:44.0-1ubuntu4all utilities to configure the GNOME desktop - faces images ii gnome-desktop3-data 44.0-1 all Common files for GNOME desktop apps ii gnome-disk-utility 44.0-1ubuntu1 amd64manage and configure disk drives and media ii gnome-font-viewer 44.0-1 amd64font viewer for GNOME ii gnome-initial-setup 44.0-1ubuntu1 amd64Initial GNOME system setup helper ii gnome-keyring 42.1-1
[Desktop-packages] [Bug 2015061] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2015061/+attachment/5660356/+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/2015061 Title: Corrupted/missing windows title background when opening windows Status in gnome-shell package in Ubuntu: Incomplete Bug description: Since upgrading to Ubuntu 23.04 (from 22.10), the title bar of some apps are corrupted when the windows first open. As soon as I de-focus and re-focus them, the title bar starts working mostly correctly. You'll find a screenshot attached. Basically, the window just repeats the pattern of the edge, until it is de-focused, and then it will properly draw the "window inactive" background color. When the window is de-focused, clicking the title bar won't focus it, although double- clicking on it will maximize it. I need to click within the window body to focus it. Edit: Looking at the screenshot file, it seems like the screenshot even assumed the title bar was actually transparent (the alpha channel of the status bar is 0 in the screenshot!) All GNOME settings were reset using dconf after upgrade, and custom themes have been removed (this is all Yaru defaults). This is happening with almost all apps, including Terminator or Thunderbird. Gnome package versions: ii gir1.2-gnomeautoar-0.1:amd640.4.4-1 amd64GObject introspection data for GnomeAutoar ii gir1.2-gnomebg-4.0:amd6444.0-1 amd64Introspection data for GnomeBG (GTK 4) ii gir1.2-gnomebluetooth-3.0:amd64 42.5-3 amd64Introspection data for GnomeBluetooth ii gir1.2-gnomedesktop-3.0:amd64 44.0-1 amd64Introspection data for GnomeDesktop (GTK 3) ii gir1.2-gnomedesktop-4.0:amd64 44.0-1 amd64Introspection data for GnomeDesktop (GTK 4) ii gkbd-capplet3.28.1-1 amd64GNOME control center tools for libgnomekbd ii gnome-accessibility-themes 3.28-2ubuntu1 all High Contrast GTK 2 theme and icons ii gnome-bluetooth-3-common42.5-3 all GNOME Bluetooth 3 common files ii gnome-bluetooth-sendto 42.5-3 amd64GNOME Bluetooth Send To app ii gnome-calculator 1:44.0-1ubuntu1amd64 GNOME desktop calculator ii gnome-calendar 44.0-1 amd64Calendar application for GNOME ii gnome-characters44.0-1 amd64character map application ii gnome-control-center 1:44.0-1ubuntu4amd64 utilities to configure the GNOME desktop ii gnome-control-center-data 1:44.0-1ubuntu4all configuration applets for GNOME - data files ii gnome-control-center-faces 1:44.0-1ubuntu4all utilities to configure the GNOME desktop - faces images ii gnome-desktop3-data 44.0-1 all Common files for GNOME desktop apps ii gnome-disk-utility 44.0-1ubuntu1 amd64manage and configure disk drives and media ii gnome-font-viewer 44.0-1 amd64font viewer for GNOME ii gnome-initial-setup 44.0-1ubuntu1 amd64Initial GNOME system setup helper ii gnome-keyring
[Desktop-packages] [Bug 2015061] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/2015061/+attachment/5660355/+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/2015061 Title: Corrupted/missing windows title background when opening windows Status in gnome-shell package in Ubuntu: Incomplete Bug description: Since upgrading to Ubuntu 23.04 (from 22.10), the title bar of some apps are corrupted when the windows first open. As soon as I de-focus and re-focus them, the title bar starts working mostly correctly. You'll find a screenshot attached. Basically, the window just repeats the pattern of the edge, until it is de-focused, and then it will properly draw the "window inactive" background color. When the window is de-focused, clicking the title bar won't focus it, although double- clicking on it will maximize it. I need to click within the window body to focus it. Edit: Looking at the screenshot file, it seems like the screenshot even assumed the title bar was actually transparent (the alpha channel of the status bar is 0 in the screenshot!) All GNOME settings were reset using dconf after upgrade, and custom themes have been removed (this is all Yaru defaults). This is happening with almost all apps, including Terminator or Thunderbird. Gnome package versions: ii gir1.2-gnomeautoar-0.1:amd640.4.4-1 amd64GObject introspection data for GnomeAutoar ii gir1.2-gnomebg-4.0:amd6444.0-1 amd64Introspection data for GnomeBG (GTK 4) ii gir1.2-gnomebluetooth-3.0:amd64 42.5-3 amd64Introspection data for GnomeBluetooth ii gir1.2-gnomedesktop-3.0:amd64 44.0-1 amd64Introspection data for GnomeDesktop (GTK 3) ii gir1.2-gnomedesktop-4.0:amd64 44.0-1 amd64Introspection data for GnomeDesktop (GTK 4) ii gkbd-capplet3.28.1-1 amd64GNOME control center tools for libgnomekbd ii gnome-accessibility-themes 3.28-2ubuntu1 all High Contrast GTK 2 theme and icons ii gnome-bluetooth-3-common42.5-3 all GNOME Bluetooth 3 common files ii gnome-bluetooth-sendto 42.5-3 amd64GNOME Bluetooth Send To app ii gnome-calculator 1:44.0-1ubuntu1amd64 GNOME desktop calculator ii gnome-calendar 44.0-1 amd64Calendar application for GNOME ii gnome-characters44.0-1 amd64character map application ii gnome-control-center 1:44.0-1ubuntu4amd64 utilities to configure the GNOME desktop ii gnome-control-center-data 1:44.0-1ubuntu4all configuration applets for GNOME - data files ii gnome-control-center-faces 1:44.0-1ubuntu4all utilities to configure the GNOME desktop - faces images ii gnome-desktop3-data 44.0-1 all Common files for GNOME desktop apps ii gnome-disk-utility 44.0-1ubuntu1 amd64manage and configure disk drives and media ii gnome-font-viewer 44.0-1 amd64font viewer for GNOME ii gnome-initial-setup 44.0-1ubuntu1 amd64Initial GNOME system setup helper ii gnome-keyring 42.1-1
[Desktop-packages] [Bug 2015061] Re: Corrupted/missing windows title background when opening windows
apport information ** Tags added: apport-collected ** Description changed: Since upgrading to Ubuntu 23.04 (from 22.10), the title bar of some apps are corrupted when the windows first open. As soon as I de-focus and re- focus them, the title bar starts working mostly correctly. You'll find a screenshot attached. Basically, the window just repeats the pattern of the edge, until it is de-focused, and then it will properly draw the "window inactive" background color. When the window is de-focused, clicking the title bar won't focus it, although double- clicking on it will maximize it. I need to click within the window body to focus it. Edit: Looking at the screenshot file, it seems like the screenshot even assumed the title bar was actually transparent (the alpha channel of the status bar is 0 in the screenshot!) All GNOME settings were reset using dconf after upgrade, and custom themes have been removed (this is all Yaru defaults). This is happening with almost all apps, including Terminator or Thunderbird. Gnome package versions: ii gir1.2-gnomeautoar-0.1:amd640.4.4-1 amd64GObject introspection data for GnomeAutoar ii gir1.2-gnomebg-4.0:amd6444.0-1 amd64Introspection data for GnomeBG (GTK 4) ii gir1.2-gnomebluetooth-3.0:amd64 42.5-3 amd64Introspection data for GnomeBluetooth ii gir1.2-gnomedesktop-3.0:amd64 44.0-1 amd64Introspection data for GnomeDesktop (GTK 3) ii gir1.2-gnomedesktop-4.0:amd64 44.0-1 amd64Introspection data for GnomeDesktop (GTK 4) ii gkbd-capplet3.28.1-1 amd64GNOME control center tools for libgnomekbd ii gnome-accessibility-themes 3.28-2ubuntu1 all High Contrast GTK 2 theme and icons ii gnome-bluetooth-3-common42.5-3 all GNOME Bluetooth 3 common files ii gnome-bluetooth-sendto 42.5-3 amd64GNOME Bluetooth Send To app ii gnome-calculator 1:44.0-1ubuntu1amd64 GNOME desktop calculator ii gnome-calendar 44.0-1 amd64Calendar application for GNOME ii gnome-characters44.0-1 amd64character map application ii gnome-control-center 1:44.0-1ubuntu4amd64 utilities to configure the GNOME desktop ii gnome-control-center-data 1:44.0-1ubuntu4all configuration applets for GNOME - data files ii gnome-control-center-faces 1:44.0-1ubuntu4all utilities to configure the GNOME desktop - faces images ii gnome-desktop3-data 44.0-1 all Common files for GNOME desktop apps ii gnome-disk-utility 44.0-1ubuntu1 amd64manage and configure disk drives and media ii gnome-font-viewer 44.0-1 amd64font viewer for GNOME ii gnome-initial-setup 44.0-1ubuntu1 amd64Initial GNOME system setup helper ii gnome-keyring 42.1-1 amd64GNOME keyring services (daemon and tools) ii gnome-keyring-pkcs11:amd64 42.1-1 amd64GNOME keyring module for the PKCS#11 module loading library ii gnome-logs
[Desktop-packages] [Bug 2015061] [NEW] Corrupted/missing windows title background when opening windows
Public bug reported: Since upgrading to Ubuntu 23.04 (from 22.10), the title bar of some apps are corrupted when the windows first open. As soon as I de-focus and re- focus them, the title bar starts working mostly correctly. You'll find a screenshot attached. Basically, the window just repeats the pattern of the edge, until it is de-focused, and then it will properly draw the "window inactive" background color. When the window is de-focused, clicking the title bar won't focus it, although double- clicking on it will maximize it. I need to click within the window body to focus it. Edit: Looking at the screenshot file, it seems like the screenshot even assumed the title bar was actually transparent (the alpha channel of the status bar is 0 in the screenshot!) All GNOME settings were reset using dconf after upgrade, and custom themes have been removed (this is all Yaru defaults). This is happening with almost all apps, including Terminator or Thunderbird. Gnome package versions: ii gir1.2-gnomeautoar-0.1:amd640.4.4-1 amd64GObject introspection data for GnomeAutoar ii gir1.2-gnomebg-4.0:amd6444.0-1 amd64Introspection data for GnomeBG (GTK 4) ii gir1.2-gnomebluetooth-3.0:amd64 42.5-3 amd64Introspection data for GnomeBluetooth ii gir1.2-gnomedesktop-3.0:amd64 44.0-1 amd64Introspection data for GnomeDesktop (GTK 3) ii gir1.2-gnomedesktop-4.0:amd64 44.0-1 amd64Introspection data for GnomeDesktop (GTK 4) ii gkbd-capplet3.28.1-1 amd64GNOME control center tools for libgnomekbd ii gnome-accessibility-themes 3.28-2ubuntu1 all High Contrast GTK 2 theme and icons ii gnome-bluetooth-3-common42.5-3 all GNOME Bluetooth 3 common files ii gnome-bluetooth-sendto 42.5-3 amd64GNOME Bluetooth Send To app ii gnome-calculator1:44.0-1ubuntu1 amd64GNOME desktop calculator ii gnome-calendar 44.0-1 amd64Calendar application for GNOME ii gnome-characters44.0-1 amd64character map application ii gnome-control-center1:44.0-1ubuntu4 amd64utilities to configure the GNOME desktop ii gnome-control-center-data 1:44.0-1ubuntu4 all configuration applets for GNOME - data files ii gnome-control-center-faces 1:44.0-1ubuntu4 all utilities to configure the GNOME desktop - faces images ii gnome-desktop3-data 44.0-1 all Common files for GNOME desktop apps ii gnome-disk-utility 44.0-1ubuntu1 amd64manage and configure disk drives and media ii gnome-font-viewer 44.0-1 amd64font viewer for GNOME ii gnome-initial-setup 44.0-1ubuntu1 amd64Initial GNOME system setup helper ii gnome-keyring 42.1-1 amd64GNOME keyring services (daemon and tools) ii gnome-keyring-pkcs11:amd64 42.1-1 amd64GNOME keyring module for the PKCS#11 module loading library ii gnome-logs 43.0-1 amd64viewer for the systemd journal ii gnome-mahjongg
[Desktop-packages] [Bug 2015059] [NEW] Dead zone below the tray icon area
Public bug reported: Since upgrading to Ubuntu 23.04, I have an issue where the zone below tray icons is partly blocked by some transparent dead zone. With AnyDesk open and its tray icon in the bar, clicking below the tray icon (on a window title for example) triggers the click event on the AnyDesk tray icon, and opens the AnyDesk software. With AnyDesk closed (and the tray icon missing), the dead zone is still present, however clicking on it does nothing. You'll find attached a screenshot showcasing the dead zone (marked in orange, it is invisible), I can't click within this dead zone. When I have a maximized window for example, I can't click on the window buttons. I tried resetting all gnome-related dconf settings after upgrading, to no avail. It worked perfectly fine with Ubuntu 22.10. Here are Gnome-related packages versions I currently have installed: ``` $ dpkg -l | grep gnome rc chrome-gnome-shell 10.1-5 all GNOME Shell extensions integration for web browsers ii gir1.2-gnomeautoar-0.1:amd640.4.4-1 amd64GObject introspection data for GnomeAutoar ii gir1.2-gnomebg-4.0:amd6444.0-1 amd64Introspection data for GnomeBG (GTK 4) ii gir1.2-gnomebluetooth-3.0:amd64 42.5-3 amd64Introspection data for GnomeBluetooth ii gir1.2-gnomedesktop-3.0:amd64 44.0-1 amd64Introspection data for GnomeDesktop (GTK 3) ii gir1.2-gnomedesktop-4.0:amd64 44.0-1 amd64Introspection data for GnomeDesktop (GTK 4) ii gkbd-capplet3.28.1-1 amd64GNOME control center tools for libgnomekbd ii gnome-accessibility-themes 3.28-2ubuntu1 all High Contrast GTK 2 theme and icons ii gnome-bluetooth-3-common42.5-3 all GNOME Bluetooth 3 common files ii gnome-bluetooth-sendto 42.5-3 amd64GNOME Bluetooth Send To app ii gnome-calculator1:44.0-1ubuntu1 amd64GNOME desktop calculator ii gnome-calendar 44.0-1 amd64Calendar application for GNOME ii gnome-characters44.0-1 amd64character map application ii gnome-control-center1:44.0-1ubuntu4 amd64utilities to configure the GNOME desktop ii gnome-control-center-data 1:44.0-1ubuntu4 all configuration applets for GNOME - data files ii gnome-control-center-faces 1:44.0-1ubuntu4 all utilities to configure the GNOME desktop - faces images ii gnome-desktop3-data 44.0-1 all Common files for GNOME desktop apps ii gnome-disk-utility 44.0-1ubuntu1 amd64manage and configure disk drives and media ii gnome-font-viewer 44.0-1 amd64font viewer for GNOME ii gnome-initial-setup 44.0-1ubuntu1 amd64Initial GNOME system setup helper ii gnome-keyring 42.1-1 amd64GNOME keyring services (daemon and tools) ii gnome-keyring-pkcs11:amd64 42.1-1 amd64GNOME keyring module for the PKCS#11 module loading library ii gnome-logs 43.0-1
[Desktop-packages] [Bug 1993800]
openQA test passes. -- 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/1993800 Title: LLVM ERROR: Cannot select: 0x2f689c8: v4i32 = ARMISD::VCMPZ 0x2f696b8, Constant:i32<2> Status in LLVM: Fix Released Status in llvm-toolchain-15 package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in llvm-toolchain-15 package in openSUSE: Fix Released Bug description: LLVM ERROR: Cannot select: 0x2f689c8: v4i32 = ARMISD::VCMPZ 0x2f696b8, Constant:i32<2> 0x2f696b8: v4i32,ch = ARMISD::VLD1DUP<(load (s32) from %ir.212)> 0x2aad434, 0x2f84090:1, Constant:i32<4> 0x2f84090: i32,i32,ch = load<(load (s32) from %ir.209, align 8), > 0x2aad434, 0x2f63a30, Constant:i32<64> 0x2f63a30: i32,ch = CopyFromReg 0x2aad434, Register:i32 %23 0x2f51c10: i32 = Register %23 0x2f82500: i32 = Constant<64> 0x2f81b28: i32 = Constant<4> 0x2f81e40: i32 = Constant<2> In function: fs_variant_partial [https://launchpadlibrarian.net/629171689/buildlog_ubuntu-kinetic- armhf.mutter_43.0-1ubuntu3_BUILDING.txt.gz] Although "LLVM ERROR: Cannot select" seems to be from LLVM, I can't determine what project "fs_variant_partial" is in. Sounds like it might be in some old version of Mesa? The start of the log suggests it's running on focal. To manage notifications about this bug go to: https://bugs.launchpad.net/llvm/+bug/1993800/+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 1993864] [NEW] Nautilus extension for gnome-console bad localization
Public bug reported: I've installed the nautilus-extension-gnome-console to have a right click item in Nautilus to open the current folder in Console, but it doesn't match my system language (French) and keeps displaying "Open in Console"). Tested on Ubuntu 22.04 with : - nautilus-extension-gnome-console 42~beta-1 - libnautilus-extension1a:amd64 1:42.2-0ubuntu1 - nautilus 1:42.2-0ubuntu1 ** Affects: mutter (Ubuntu) Importance: Undecided Status: New -- 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/1993864 Title: Nautilus extension for gnome-console bad localization Status in mutter package in Ubuntu: New Bug description: I've installed the nautilus-extension-gnome-console to have a right click item in Nautilus to open the current folder in Console, but it doesn't match my system language (French) and keeps displaying "Open in Console"). Tested on Ubuntu 22.04 with : - nautilus-extension-gnome-console 42~beta-1 - libnautilus-extension1a:amd64 1:42.2-0ubuntu1 - nautilus 1:42.2-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1993864/+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 1993747] [NEW] Chromium browser "save as" window behaviour
Public bug reported: Hi! I have noticed that on both Ubuntu 22.04 and 22.10, when using a Chromium browser and opening a "save as" window (e.g. to save an image), I can't just push "Enter" and save nor push "Escape" and close the window. I have to click on the "Save" or "Cancel" buttons. All Chromium browsers look impacted. I tested on Chrome (106.0.5249.119), Brave (Version 1.44.112 Chromium: 106.0.5249.119 ) and Edge (Version 106.0.1370.52) tonight on Ubuntu 22.10. It was already the case a few months ago on Ubuntu 22.04 with both Brave (Version 1.39.122 Chromium: 102.0.5005.115) and Edge (Version 102.0.1245.44) - not tested with Chrome. That used to work on previous Ubuntu versions, and still works for other programs such as LibreOffice. Thanks a lot! ** Affects: meta-gnome3 (Ubuntu) Importance: Undecided Status: New ** Package changed: mutter (Ubuntu) => gtk4 (Ubuntu) ** Package changed: gtk4 (Ubuntu) => meta-gnome3 (Ubuntu) -- 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/1993747 Title: Chromium browser "save as" window behaviour Status in meta-gnome3 package in Ubuntu: New Bug description: Hi! I have noticed that on both Ubuntu 22.04 and 22.10, when using a Chromium browser and opening a "save as" window (e.g. to save an image), I can't just push "Enter" and save nor push "Escape" and close the window. I have to click on the "Save" or "Cancel" buttons. All Chromium browsers look impacted. I tested on Chrome (106.0.5249.119), Brave (Version 1.44.112 Chromium: 106.0.5249.119 ) and Edge (Version 106.0.1370.52) tonight on Ubuntu 22.10. It was already the case a few months ago on Ubuntu 22.04 with both Brave (Version 1.39.122 Chromium: 102.0.5005.115) and Edge (Version 102.0.1245.44) - not tested with Chrome. That used to work on previous Ubuntu versions, and still works for other programs such as LibreOffice. Thanks a lot! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/meta-gnome3/+bug/1993747/+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 1993360] [NEW] [Dell XPS 15 9520] Cannot resume after suspend
Public bug reported: Similar as https://bugs.launchpad.net/ubuntu/+bug/1975454 Cannot resume after suspend when using nvidia card in Performance Mode on x11 ``` Bluetooth hcio: Timed out waiting for suspend events Bluetooth hcio: Suspend timeout bit: 6 Bluetooth hcio: Suspend notifier action (3) failed: -110 ``` ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.4-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 Uname: Linux 5.15.0-50-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Oct 19 00:04:31 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-09-20 (28 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RelatedPackageVersions: mutter-common 42.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1993360 Title: [Dell XPS 15 9520] Cannot resume after suspend Status in gnome-shell package in Ubuntu: New Bug description: Similar as https://bugs.launchpad.net/ubuntu/+bug/1975454 Cannot resume after suspend when using nvidia card in Performance Mode on x11 ``` Bluetooth hcio: Timed out waiting for suspend events Bluetooth hcio: Suspend timeout bit: 6 Bluetooth hcio: Suspend notifier action (3) failed: -110 ``` ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.4-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 Uname: Linux 5.15.0-50-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Oct 19 00:04:31 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-09-20 (28 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RelatedPackageVersions: mutter-common 42.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1993360/+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 1962541] Re: PEAP wifi can't connect (ubuntu live/installer is also not working
logs with '-ddd' from ubuntu 22.04 beta ** Attachment added: "wpa_supplicant.log" https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1962541/+attachment/5577253/+files/wpa_supplicant.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1962541 Title: PEAP wifi can't connect (ubuntu live/installer is also not working Status in wpa package in Ubuntu: Triaged Status in wpa source package in Jammy: Triaged Bug description: WPA2 enterprise can't connect PEAP ubuntu 22.04 live/installer is not working too ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.6 Uname: Linux 5.16.0-kali1-amd64 x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Tue Mar 1 09:18:42 2022 PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.release-upgrades: 2022-02-27T21:07:16.553410 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1962541/+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 1962541] Re: PEAP wifi can't connect (ubuntu live/installer is also not working
I had edited the .service file but it was deleted when I reinstalled the ubuntu packages :-) The new log is attached. ** Attachment added: "wpa_supplicant.log" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1962541/+attachment/5569942/+files/wpa_supplicant.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1962541 Title: PEAP wifi can't connect (ubuntu live/installer is also not working Status in network-manager package in Ubuntu: Incomplete Bug description: WPA2 enterprise can't connect PEAP ubuntu 22.04 live/installer is not working too ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.6 Uname: Linux 5.16.0-kali1-amd64 x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Tue Mar 1 09:18:42 2022 PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.release-upgrades: 2022-02-27T21:07:16.553410 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1962541/+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 1962541] Re: PEAP wifi can't connect (ubuntu live/installer is also not working
I installed wpasupplicant_2.10-2_amd64.deb and libssl1.1_1.1.1m-1_amd64.deb from debian sid. It works. I attached the log from journalctl -b 0 with ubuntu's wpasupplicant package. ** Attachment added: "wpa_supplicant.log" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1962541/+attachment/5569503/+files/wpa_supplicant.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1962541 Title: PEAP wifi can't connect (ubuntu live/installer is also not working Status in network-manager package in Ubuntu: Incomplete Bug description: WPA2 enterprise can't connect PEAP ubuntu 22.04 live/installer is not working too ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.6 Uname: Linux 5.16.0-kali1-amd64 x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Tue Mar 1 09:18:42 2022 PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.release-upgrades: 2022-02-27T21:07:16.553410 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1962541/+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 1926153] [NEW] [hostname-M.2, Nvidia GPU 70 HDMI/DP, Digital Out, HDMI] Playback problem in terminal
Public bug reported: Hello, When in terminal, with my header on, if I press alternatively the "tab" key or the backspace key when there is no text, I get parasitic noise that come and go, in addition to the error sound. The parasitic noises are most often not loud, but they're here although they definitely shouldn't. Sometimes, it's quite loud too. The bug is not deterministic. Sometimes the tone is higher/lower. Sometimes it disappear on the first time I re-press one key among tab and suppress. Sometimes it requires more key pressing. I'm not sure whether the sound ends up by disapearing after a few retries, or if it just becomes too quiet for me to hear it. The bug doesn't occur when the sound is deactivated I feel like this has something to do with the error sound that is played when I delete and there is no character to delete It is not a big deal in itself. But maybe this very benign symptom hides a more serious issue idk. The sound comes out of my graphic card (nvidia gtx 980 ti) through a Samsung TV. I don't think the problem comes from either the graphic card or the TV, because it only happens in ubuntu, never in windows ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: guillaume 1669 F pulseaudio /dev/snd/pcmC1D0c: guillaume 1669 F...m pulseaudio /dev/snd/controlC2: guillaume 1669 F pulseaudio /dev/snd/controlC0: guillaume 1669 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Apr 26 14:04:04 2021 InstallationDate: Installed on 2021-01-06 (110 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia successful Symptom_Card: GM200 High Definition Audio - HDA NVidia Symptom_Jack: Digital Out, HDMI Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [hostname-M.2, Nvidia GPU 70 HDMI/DP, Digital Out, HDMI] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/17/2018 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F23d dmi.board.asset.tag: Default string dmi.board.name: A320MA-M.2-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF23d:bd04/17/2018:br5.13:svnGigabyteTechnologyCo.,Ltd.:pnA320MA-M.2:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320MA-M.2-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: A320MA-M.2 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1926153 Title: [hostname-M.2, Nvidia GPU 70 HDMI/DP, Digital Out, HDMI] Playback problem in terminal Status in alsa-driver package in Ubuntu: New Bug description: Hello, When in terminal, with my header on, if I press alternatively the "tab" key or the backspace key when there is no text, I get parasitic noise that come and go, in addition to the error sound. The parasitic noises are most often not loud, but they're here although they definitely shouldn't. Sometimes, it's quite loud too. The bug is not deterministic. Sometimes the tone is higher/lower. Sometimes it disappear on the first time I re-press one key among tab and suppress. Sometimes it requires more key pressing. I'm not sure whether the sound ends up by disapearing after a few retries, or if it just becomes too quiet for me to hear it. The bug doesn't occur when the sound is deactivated I feel like this has something to do with the error sound that is played when I delete and there is no character to delete It is not a big deal in itself. But maybe this very benign symptom hides a more serious issue idk. The sound comes out of my graphic card (nvidia gtx 980 ti) through a Samsung TV. I don't think the problem comes from either the graphic card or the TV, because it only happens in ubuntu, never in windows ProblemType: Bug DistroRelease: Ubu
[Desktop-packages] [Bug 402892] Re: Mouse cursor gets stuck in "drag and drop" mode
Happens very frequently for me also on a vanilla 18.04 (Thinkpad), but only on a small subset of applications. What's strange is that the bug appeared a few days ago after years without problem. I do not use any external peripheral (nothing connected to the laptop except the power supply). An easy solution to solve this without rebooting the whole system is to disable then enable the TouchScreen (disabling alone is not sufficient). Following Paul Müller's steps: - find your TouchScreen input ID with ``xinput`` (in my case ``Melfas LGDisplay Incell Touch id=9`` - ``xinput --disable 9`` - ``xinput --enable 9`` If you want to automate this in a script/alias, you can easily retrieve the ID once you know the name of the TouchScreen: - ``xinput list --id-only 'Melfas LGDisplay Incell Touch'`` -- 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/402892 Title: Mouse cursor gets stuck in "drag and drop" mode Status in OpenShot Video Editor: New Status in X.Org X server: New Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in rapidsvn package in Ubuntu: Confirmed Bug description: Binary package hint: rapidsvn When clicking on the Bookmark root or on one of the bookmarks below the mouse cursor gets stuck in "drag n drop" mode, blocking all keyboard entry and also mouse clicks for the the whole GUI (systemwide). Unfortunately I cannot provide any debug or other information, as I have to reboot everytime. I am running Ubuntu 9.04 with compiz enabled. Many thanks in advance for your help with this problem, /nxT To manage notifications about this bug go to: https://bugs.launchpad.net/openshot/+bug/402892/+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 1912668] [NEW] [Q1U dynamic microphone - AT2020 USB, recording] fails after a while
Public bug reported: Opening sound control panel, or Audacity, ATH2020-USB microphone will show signal for a few seconds, then cut off (the meter stays stuck in last updated position). Same behavior using other apps that use the microphone. Changed USB port, still the same result. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-40.45-generic 5.8.18 Uname: Linux 5.8.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: surefoot 1972 F pulseaudio /dev/snd/controlC2: surefoot 1972 F pulseaudio /dev/snd/controlC1: surefoot 1972 F pulseaudio /dev/snd/pcmC1D0c: surefoot 1972 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jan 21 18:00:16 2021 InstallationDate: Installed on 2020-10-31 (81 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: CMI8788 [Oxygen HD Audio] (Virtuoso 100 (Xonar Essence STX II)) - Xonar STX II Symptom_PulseAudioLog: janv. 21 14:34:39 STH10 dbus-daemon[1083]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.34' (uid=1000 pid=1972 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") Symptom_Type: Sound works for a while, then breaks Title: [Q1U dynamic microphone - AT2020 USB, recording] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/21/2018 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3902 dmi.board.asset.tag: Default string dmi.board.name: RAMPAGE V EXTREME dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3902:bd03/21/2018:br5.11:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnRAMPAGEVEXTREME:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- 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/1912668 Title: [Q1U dynamic microphone - AT2020 USB, recording] fails after a while Status in alsa-driver package in Ubuntu: New Bug description: Opening sound control panel, or Audacity, ATH2020-USB microphone will show signal for a few seconds, then cut off (the meter stays stuck in last updated position). Same behavior using other apps that use the microphone. Changed USB port, still the same result. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-40.45-generic 5.8.18 Uname: Linux 5.8.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: surefoot 1972 F pulseaudio /dev/snd/controlC2: surefoot 1972 F pulseaudio /dev/snd/controlC1: surefoot 1972 F pulseaudio /dev/snd/pcmC1D0c: surefoot 1972 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jan 21 18:00:16 2021 InstallationDate: Installed on 2020-10-31 (81 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: CMI8788 [Oxygen HD Audio] (Virtuoso 100 (Xonar Essence STX II)) - Xonar STX II Symptom_PulseAudioLog: janv. 21 14:34:39 STH10 dbus-daemon[1083]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.34' (uid=1000 pid=1972 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") Symptom_Type: Sound works for a while, then breaks Title: [Q1U dynamic microphone - AT2020 USB, recording] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/21/2018 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3902 dmi.board.asset.tag: Default string dmi.board.name: RAMPAGE V EXTREME dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string
[Desktop-packages] [Bug 1910598] Re: Ejecting a Blanc CD/DVD/BluRay-R disk writes to it.
Unfortunately, I don't have any crash report for udisk in /var/crash. -- 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/1910598 Title: Ejecting a Blanc CD/DVD/BluRay-R disk writes to it. Status in caja package in Ubuntu: New Status in udisks2 package in Ubuntu: Incomplete Bug description: I used the "eject" contextual menu on the icon of a blank Bluray-R on the caja desktop, and I got a message saying that I need to wait for data to be written on the disc before being able to remove it safely (same message as when trying to eject an usb stick, when some data syncing is left to be done). Afterwards, when I tried to burn data to it, the app (k3b) told that the disc was not empty thus not writeable. This bug cost me a brand new Bluray-R M-Disc of 100GB, which is a quite pricey medium. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: caja 1.20.2-4ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-129.132-generic 4.15.18 Uname: Linux 4.15.0-129-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.21 Architecture: amd64 CurrentDesktop: MATE Date: Thu Jan 7 22:42:25 2021 SourcePackage: caja UpgradeStatus: Upgraded to bionic on 2019-02-16 (691 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/caja/+bug/1910598/+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 1910598] Re: Ejecting a Blanc CD/DVD/BluRay-R disk writes to it.
Here it is ** Attachment added: "journalctl.log" https://bugs.launchpad.net/ubuntu/+source/caja/+bug/1910598/+attachment/5452757/+files/journalctl.log -- 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/1910598 Title: Ejecting a Blanc CD/DVD/BluRay-R disk writes to it. Status in caja package in Ubuntu: New Status in udisks2 package in Ubuntu: Incomplete Bug description: I used the "eject" contextual menu on the icon of a blank Bluray-R on the caja desktop, and I got a message saying that I need to wait for data to be written on the disc before being able to remove it safely (same message as when trying to eject an usb stick, when some data syncing is left to be done). Afterwards, when I tried to burn data to it, the app (k3b) told that the disc was not empty thus not writeable. This bug cost me a brand new Bluray-R M-Disc of 100GB, which is a quite pricey medium. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: caja 1.20.2-4ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-129.132-generic 4.15.18 Uname: Linux 4.15.0-129-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.21 Architecture: amd64 CurrentDesktop: MATE Date: Thu Jan 7 22:42:25 2021 SourcePackage: caja UpgradeStatus: Upgraded to bionic on 2019-02-16 (691 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/caja/+bug/1910598/+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 1867147] Re: Failed to add UUID: Busy (0x0a)
I have to same error with Ubuntu 20.10 ** Changed in: linux (Ubuntu) Status: Expired => Confirmed ** Package changed: linux (Ubuntu) => bluez (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1867147 Title: Failed to add UUID: Busy (0x0a) Status in bluez package in Ubuntu: Confirmed Bug description: dmesg Bluetooth: hci0: command 0x0c24 tx timeout rfkill list 0: hci0: Bluetooth Soft blocked: no Hard blocked: no 1: hci1: Bluetooth Soft blocked: no Hard blocked: no 2: phy0: Wireless LAN Soft blocked: yes Hard blocked: no bluetoothctl Failed to start discovery: org.bluez.Error.InProgress lsusb Bus 001 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) lshw *-usb descrição: USB controller produto: Cannon Lake PCH USB 3.1 xHCI Host Controller fabricante: Intel Corporation ID físico: 14 informações do barramento: pci@:00:14.0 versão: 10 largura: 64 bits clock: 33MHz capacidades: pm msi xhci bus_master cap_list configuração: driver=xhci_hcd latency=0 recursos: irq:124 memória:eb22-eb22 *-usbhost:0 produto: xHCI Host Controller fabricante: Linux 5.3.0-40-generic xhci-hcd ID físico: 0 informações do barramento: usb@1 nome lógico: usb1 versão: 5.03 capacidades: usb-2.00 configuração: driver=hub slots=16 speed=480Mbit/s *-usb:0 descrição: Interface sem fio bluetooth produto: JL AC69 A10 fabricante: Cambridge Silicon Radio, Ltd ID físico: 1 informações do barramento: usb@1:1 versão: 25.20 capacidades: bluetooth usb-2.00 configuração: driver=btusb maxpower=100mA speed=12Mbit/s ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.3 ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 12 09:18:43 2020 InstallationDate: Installed on 2019-06-19 (266 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) InterestingModules: rfcomm bnep btusb bluetooth MachineType: HP HP EliteDesk 800 G4 SFF ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=885446d9-2945-4958-a7f0-1eadecf23697 ro locale=pt_BR quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/15/2019 dmi.bios.vendor: HP dmi.bios.version: Q01 Ver. 02.06.03 dmi.board.name: 83E1 dmi.board.vendor: HP dmi.board.version: KBC Version 07.D2.00 dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ01Ver.02.06.03:bd02/15/2019:svnHP:pnHPEliteDesk800G4SFF:pvr:rvnHP:rn83E1:rvrKBCVersion07.D2.00:cvnHP:ct3:cvr: dmi.product.family: 103C_53307F HP EliteDesk dmi.product.name: HP EliteDesk 800 G4 SFF dmi.product.sku: 5ZA60LP#AC4 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1867147/+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 1894596] Re: Night Light stays on
Night Light is set to turn on at 10:00 pm and off at 6:00 am. At 7:25 am I noticed the icon had disappeared but the screen was still "orange". Please find as an attachment the results of: lspci -kv > lspci.txt journalctl -b0 > journal.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/1894596 Title: Night Light stays on Status in gnome-shell package in Ubuntu: Incomplete Bug description: I have "Night mode" set to turn on every day at 10pm and off at 6 am. However, at 6, the "Night mode" icon disappears but my screen remaine orangeish as when "Night mode" is on. Logging off and on again restores color temperature back to normal. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Sep 7 07:43:43 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-11 (148 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.4-0ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1894596/+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 1894596] Re: Night Light stays on
** Attachment added: "lspci.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1894596/+attachment/5409282/+files/lspci.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/1894596 Title: Night Light stays on Status in gnome-shell package in Ubuntu: Incomplete Bug description: I have "Night mode" set to turn on every day at 10pm and off at 6 am. However, at 6, the "Night mode" icon disappears but my screen remaine orangeish as when "Night mode" is on. Logging off and on again restores color temperature back to normal. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Sep 7 07:43:43 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-11 (148 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.4-0ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1894596/+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 1894596] Re: Night Light stays on
This may have something to do with using an external screen. I usually use only my external screen, with laptop screen/lid closed. I noticed right now that if I open the laptop lid, then color on the external screen goes back to "normal" and color on the laptop screen (defined as secondary, without Gnome shell panel) stays in "orange" mode. -- 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/1894596 Title: Night Light stays on Status in gnome-shell package in Ubuntu: Incomplete Bug description: I have "Night mode" set to turn on every day at 10pm and off at 6 am. However, at 6, the "Night mode" icon disappears but my screen remaine orangeish as when "Night mode" is on. Logging off and on again restores color temperature back to normal. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Sep 7 07:43:43 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-11 (148 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.4-0ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1894596/+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 1894596] Re: Night Light stays on
** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1894596/+attachment/5409281/+files/journal.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/1894596 Title: Night Light stays on Status in gnome-shell package in Ubuntu: Incomplete Bug description: I have "Night mode" set to turn on every day at 10pm and off at 6 am. However, at 6, the "Night mode" icon disappears but my screen remaine orangeish as when "Night mode" is on. Logging off and on again restores color temperature back to normal. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Sep 7 07:43:43 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-11 (148 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.4-0ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1894596/+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 1894596] Re: Night Light stays on
** Attachment added: "Extensions.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1894596/+attachment/5408400/+files/Extensions.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1894596 Title: Night Light stays on Status in gnome-shell package in Ubuntu: Incomplete Bug description: I have "Night mode" set to turn on every day at 10pm and off at 6 am. However, at 6, the "Night mode" icon disappears but my screen remaine orangeish as when "Night mode" is on. Logging off and on again restores color temperature back to normal. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Sep 7 07:43:43 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-11 (148 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.4-0ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1894596/+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 1894596] Re: Night Light stays on
I currently have no Gnome extension activated, apart from "Ubuntu appindicators" (see screenshot "Extensions.png") -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1894596 Title: Night Light stays on Status in gnome-shell package in Ubuntu: Incomplete Bug description: I have "Night mode" set to turn on every day at 10pm and off at 6 am. However, at 6, the "Night mode" icon disappears but my screen remaine orangeish as when "Night mode" is on. Logging off and on again restores color temperature back to normal. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Sep 7 07:43:43 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-11 (148 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.4-0ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1894596/+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 1894596] Re: Night Light stays on
Extension list (attachment) -- 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/1894596 Title: Night Light stays on Status in gnome-shell package in Ubuntu: Incomplete Bug description: I have "Night mode" set to turn on every day at 10pm and off at 6 am. However, at 6, the "Night mode" icon disappears but my screen remaine orangeish as when "Night mode" is on. Logging off and on again restores color temperature back to normal. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Sep 7 07:43:43 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-11 (148 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.4-0ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1894596/+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 1894596] [NEW] Night mode stays on
Public bug reported: I have "Night mode" set to turn on every day at 10pm and off at 6 am. However, at 6, the "Night mode" icon disappears but my screen remaine orangeish as when "Night mode" is on. Logging off and on again restores color temperature back to normal. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Sep 7 07:43:43 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-11 (148 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.4-0ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1894596 Title: Night mode stays on Status in gnome-shell package in Ubuntu: New Bug description: I have "Night mode" set to turn on every day at 10pm and off at 6 am. However, at 6, the "Night mode" icon disappears but my screen remaine orangeish as when "Night mode" is on. Logging off and on again restores color temperature back to normal. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Sep 7 07:43:43 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-11 (148 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.4-0ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1894596/+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 1873942] Re: [wayland] gnome-screenshot takes a screenshot of the wrong screen
I have upgraded to mutter 3.36.2-1ubuntu1~20.04.1 this morning and rebooted. I can confirm this new version fixes the problem for me. Thanks! Le mar. 12 mai 2020 à 22:36, Brian Murray a écrit : > Hello Guillaume, or anyone else affected, > > Accepted mutter into focal-proposed. The package will build now and be > available at > https://launchpad.net/ubuntu/+source/mutter/3.36.2-1ubuntu1~20.04.1 in a > few hours, and then in the -proposed repository. > > Please help us by testing this new package. See > https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how > to enable and use -proposed. Your feedback will aid us getting this > update out to other Ubuntu users. > > If this package fixes the bug for you, please add a comment to this bug, > mentioning the version of the package you tested, what testing has been > performed on the package and change the tag from verification-needed- > focal to verification-done-focal. If it does not fix the bug for you, > please add a comment stating that, and change the tag to verification- > failed-focal. In either case, without details of your testing we will > not be able to proceed. > > Further information regarding the verification process can be found at > https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in > advance for helping! > > N.B. The updated package will be released to -updates after the bug(s) > fixed by this package have been verified and the package has been in > -proposed for a minimum of 7 days. > > ** Tags added: verification-needed verification-needed-focal > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1873942 > > Title: > [wayland] gnome-screenshot takes a screenshot of the wrong screen > > Status in GNOME Shell: > Unknown > Status in mutter package in Ubuntu: > Fix Released > Status in mutter source package in Focal: > Fix Committed > Status in mutter source package in Groovy: > Fix Released > > Bug description: > I have a dual monitor setup, with the external monitor defined as the > "primary" one (and the laptop one secondary). > When using the Shift + PrtScr shortcut and choosing an area on the > external monitor, the screenshot saved in ~/Pictures shows this area but on > the _laptop_ screen. > (Choosing an area on the laptop screen works OK.) > > I use the vanilla Gnome session (with Wayland), installed with apt. > > [ Impact ] > > gnome-screenshot takes a screenshot of the wrong screen > > [ Test case ] > > In dual monitor setup, use Shift+PrtScr to take a screenshot in an > area in the external monitor. > > The saved area should respect the one you selected > > [ Regression potential ] > > Screenshot or screencasting may have not espected behavior > > > ProblemType: BugDistroRelease: Ubuntu 20.04 > Package: gnome-screenshot 3.36.0-1ubuntu1 > ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 > Uname: Linux 5.4.0-25-generic x86_64 > ApportVersion: 2.20.11-0ubuntu27 > Architecture: amd64 > CasperMD5CheckResult: skip > CurrentDesktop: GNOME > Date: Mon Apr 20 20:58:46 2020 > InstallationDate: Installed on 2020-04-11 (9 days ago) > InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=fr_FR.UTF-8 >SHELL=/bin/bashSourcePackage: gnome-screenshot > UpgradeStatus: No upgrade log present (probably fresh install) > --- > ProblemType: Bug > ApportVersion: 2.20.11-0ubuntu27 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' > CasperMD5CheckResult: skip > CompositorRunning: None > CurrentDesktop: GNOME > DistUpgraded: Fresh install > DistroCodename: focalDistroRelease: Ubuntu 20.04 > DistroVariant: ubuntu > DkmsStatus: >acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed >acpi-call, 1.1.0, 5.4.0-24-generic, x86_64: installed >acpi-call, 1.1.0, 5.4.0-25-generic, x86_64: installed > GraphicsCard: >Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA > controller]) > Subsystem: ASUSTeK Computer Inc. HD Graphics 620 [1043:16e0] > InstallationDate: Installed on 2020-04-11 (9 days ago) > InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) > Lsusb: >Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub >Bus 001 Device 004: ID 8087:0a2b Intel Corp. >Bus 001 Device 003: ID 0bda:58d2 Realtek Semiconductor Corp. USB
Re: [Desktop-packages] [Bug 1873942] Re: gnome-screenshot takes a screenshot of the wrong screen
Yes, I can confirm the bug happens only on Wayland. Everything works fine under the standard "Ubuntu" session, or the "Gnome on Xorg" session. (I also noticed something strange under the "Ubuntu on Wayland" session, wich might be related: I can screenshot the left dock and sometimes parts the dock and an unfocused window, but never the focused/current/selected window.) Le mar. 21 avr. 2020 à 11:26, Sebastien Bacher a écrit : > Thank you for your bug report. Is the issue specific to wayland? does it > work if you try under X? > > ** Changed in: gnome-shell (Ubuntu) >Status: Confirmed => Triaged > > ** Changed in: gnome-screenshot (Ubuntu) >Status: Confirmed => Invalid > > ** Changed in: gnome-shell (Ubuntu) >Importance: Undecided => Low > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1873942 > > Title: > gnome-screenshot takes a screenshot of the wrong screen > > Status in GNOME Shell: > Unknown > Status in gnome-screenshot package in Ubuntu: > Invalid > Status in gnome-shell package in Ubuntu: > Triaged > > Bug description: > I have a dual monitor setup, with the external monitor defined as the > "primary" one (and the laptop one secondary). > When using the Shift + PrtScr shortcut and choosing an area on the > external monitor, the screenshot saved in ~/Pictures shows this area but on > the _laptop_ screen. > (Choosing an area on the laptop screen works OK.) > > I use the vanilla Gnome session (with Wayland), installed with apt. > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: gnome-screenshot 3.36.0-1ubuntu1 > ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 > Uname: Linux 5.4.0-25-generic x86_64 > ApportVersion: 2.20.11-0ubuntu27 > Architecture: amd64 > CasperMD5CheckResult: skip > CurrentDesktop: GNOME > Date: Mon Apr 20 20:58:46 2020 > InstallationDate: Installed on 2020-04-11 (9 days ago) > InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=fr_FR.UTF-8 >SHELL=/bin/bash > SourcePackage: gnome-screenshot > UpgradeStatus: No upgrade log present (probably fresh install) > --- > ProblemType: Bug > ApportVersion: 2.20.11-0ubuntu27 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' > CasperMD5CheckResult: skip > CompositorRunning: None > CurrentDesktop: GNOME > DistUpgraded: Fresh install > DistroCodename: focal > DistroRelease: Ubuntu 20.04 > DistroVariant: ubuntu > DkmsStatus: >acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed >acpi-call, 1.1.0, 5.4.0-24-generic, x86_64: installed >acpi-call, 1.1.0, 5.4.0-25-generic, x86_64: installed > GraphicsCard: >Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA > controller]) > Subsystem: ASUSTeK Computer Inc. HD Graphics 620 [1043:16e0] > InstallationDate: Installed on 2020-04-11 (9 days ago) > InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) > Lsusb: >Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub >Bus 001 Device 004: ID 8087:0a2b Intel Corp. >Bus 001 Device 003: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD > UVC WebCam >Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver >Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > MachineType: ASUSTeK COMPUTER INC. UX410UAK > Package: wayland (not installed) > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=fr_FR.UTF-8 >SHELL=/bin/bash > ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-25-generic > root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 > ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 > Tags: focal wayland-session ubuntu > Uname: Linux 5.4.0-25-generic x86_64 > UpgradeStatus: No upgrade log present (probably fresh install) > UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo > _MarkForUpload: True > dmi.bios.date: 04/17/2019 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: UX410UAK.312 > dmi.board.asset.tag: ATN12345678901234567 > dmi.board.name: UX410UAK > dmi.board.vendor: ASUSTeK COMPUTER INC. > dmi.board.version: 1.0 > dmi.chassis.asset.tag: No Asset Tag > dmi.chassis.type: 10 > dmi.chassis.vendor: ASUSTeK COMPUTER INC. > dmi.chassis.version: 1.0 > dmi.modalias: > dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.312:bd04/17/2019:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: > dmi.product.family: ZenBook > dmi.product.name: UX410UAK > dmi.product.version: 1.0 > dmi.sys.vendor: ASUSTeK COMPUTER INC. > version.compiz: compiz N/A > version.libdrm2: libdrm2 2.4.101-2 >
[Desktop-packages] [Bug 1873942] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1873942/+attachment/5357329/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1873942 Title: gnome-screenshot takes a screenshot of the wrong screen Status in wayland package in Ubuntu: New Bug description: I have a dual monitor setup, with the external monitor defined as the "primary" one (and the laptop one secondary). When using the Shift + PrtScr shortcut and choosing an area on the external monitor, the screenshot saved in ~/Pictures shows this area but on the _laptop_ screen. (Choosing an area on the laptop screen works OK.) I use the vanilla Gnome session (with Wayland), installed with apt. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-screenshot 3.36.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Uname: Linux 5.4.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Apr 20 20:58:46 2020 InstallationDate: Installed on 2020-04-11 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-screenshot UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-24-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-25-generic, x86_64: installed GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 620 [1043:16e0] InstallationDate: Installed on 2020-04-11 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC WebCam Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK Package: wayland (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-25-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Tags: focal wayland-session ubuntu Uname: Linux 5.4.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/17/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.312 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.312:bd04/17/2019:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: UX410UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1873942/+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 1873942] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1873942/+attachment/5357324/+files/Lspci.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1873942 Title: gnome-screenshot takes a screenshot of the wrong screen Status in wayland package in Ubuntu: New Bug description: I have a dual monitor setup, with the external monitor defined as the "primary" one (and the laptop one secondary). When using the Shift + PrtScr shortcut and choosing an area on the external monitor, the screenshot saved in ~/Pictures shows this area but on the _laptop_ screen. (Choosing an area on the laptop screen works OK.) I use the vanilla Gnome session (with Wayland), installed with apt. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-screenshot 3.36.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Uname: Linux 5.4.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Apr 20 20:58:46 2020 InstallationDate: Installed on 2020-04-11 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-screenshot UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-24-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-25-generic, x86_64: installed GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 620 [1043:16e0] InstallationDate: Installed on 2020-04-11 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC WebCam Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK Package: wayland (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-25-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Tags: focal wayland-session ubuntu Uname: Linux 5.4.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/17/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.312 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.312:bd04/17/2019:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: UX410UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1873942/+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 1873942] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1873942/+attachment/5357332/+files/ProcModules.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1873942 Title: gnome-screenshot takes a screenshot of the wrong screen Status in wayland package in Ubuntu: New Bug description: I have a dual monitor setup, with the external monitor defined as the "primary" one (and the laptop one secondary). When using the Shift + PrtScr shortcut and choosing an area on the external monitor, the screenshot saved in ~/Pictures shows this area but on the _laptop_ screen. (Choosing an area on the laptop screen works OK.) I use the vanilla Gnome session (with Wayland), installed with apt. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-screenshot 3.36.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Uname: Linux 5.4.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Apr 20 20:58:46 2020 InstallationDate: Installed on 2020-04-11 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-screenshot UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-24-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-25-generic, x86_64: installed GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 620 [1043:16e0] InstallationDate: Installed on 2020-04-11 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC WebCam Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK Package: wayland (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-25-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Tags: focal wayland-session ubuntu Uname: Linux 5.4.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/17/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.312 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.312:bd04/17/2019:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: UX410UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1873942/+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 1873942] XorgLogOld.txt
apport information ** Attachment added: "XorgLogOld.txt" https://bugs.launchpad.net/bugs/1873942/+attachment/5357335/+files/XorgLogOld.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1873942 Title: gnome-screenshot takes a screenshot of the wrong screen Status in wayland package in Ubuntu: New Bug description: I have a dual monitor setup, with the external monitor defined as the "primary" one (and the laptop one secondary). When using the Shift + PrtScr shortcut and choosing an area on the external monitor, the screenshot saved in ~/Pictures shows this area but on the _laptop_ screen. (Choosing an area on the laptop screen works OK.) I use the vanilla Gnome session (with Wayland), installed with apt. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-screenshot 3.36.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Uname: Linux 5.4.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Apr 20 20:58:46 2020 InstallationDate: Installed on 2020-04-11 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-screenshot UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-24-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-25-generic, x86_64: installed GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 620 [1043:16e0] InstallationDate: Installed on 2020-04-11 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC WebCam Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK Package: wayland (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-25-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Tags: focal wayland-session ubuntu Uname: Linux 5.4.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/17/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.312 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.312:bd04/17/2019:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: UX410UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1873942/+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 1873942] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1873942/+attachment/5357333/+files/UdevDb.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1873942 Title: gnome-screenshot takes a screenshot of the wrong screen Status in wayland package in Ubuntu: New Bug description: I have a dual monitor setup, with the external monitor defined as the "primary" one (and the laptop one secondary). When using the Shift + PrtScr shortcut and choosing an area on the external monitor, the screenshot saved in ~/Pictures shows this area but on the _laptop_ screen. (Choosing an area on the laptop screen works OK.) I use the vanilla Gnome session (with Wayland), installed with apt. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-screenshot 3.36.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Uname: Linux 5.4.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Apr 20 20:58:46 2020 InstallationDate: Installed on 2020-04-11 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-screenshot UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-24-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-25-generic, x86_64: installed GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 620 [1043:16e0] InstallationDate: Installed on 2020-04-11 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC WebCam Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK Package: wayland (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-25-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Tags: focal wayland-session ubuntu Uname: Linux 5.4.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/17/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.312 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.312:bd04/17/2019:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: UX410UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1873942/+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 1873942] [NEW] gnome-screenshot takes a screenshot of the wrong screen
Public bug reported: I have a dual monitor setup, with the external monitor defined as the "primary" one (and the laptop one secondary). When using the Shift + PrtScr shortcut and choosing an area on the external monitor, the screenshot saved in ~/Pictures shows this area but on the _laptop_ screen. (Choosing an area on the laptop screen works OK.) I use the vanilla Gnome session (with Wayland), installed with apt. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-screenshot 3.36.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Uname: Linux 5.4.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Apr 20 20:58:46 2020 InstallationDate: Installed on 2020-04-11 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-screenshot UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-24-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-25-generic, x86_64: installed GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 620 [1043:16e0] InstallationDate: Installed on 2020-04-11 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC WebCam Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK Package: wayland (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-25-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Tags: focal wayland-session ubuntu Uname: Linux 5.4.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/17/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.312 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.312:bd04/17/2019:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: UX410UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: wayland (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug apport-collected focal ubuntu wayland-session ** Package changed: gnome-screenshot (Ubuntu) => wayland (Ubuntu) ** Tags added: apport-collected ubuntu ** Description changed: I have a dual monitor setup, with the external monitor defined as the "primary" one (and the laptop one secondary). When using the Shift + PrtScr shortcut and choosing an area on the external monitor, the screenshot saved in ~/Pictures shows this area but on the _laptop_ screen. (Choosing an area on the laptop screen works OK.) I use the vanilla Gnome session (with Wayland), installed with apt. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-screenshot 3.36.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Uname: Linux 5.4.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Apr 20 20:58:46 2020
[Desktop-packages] [Bug 1873942] xdpyinfo.txt
apport information ** Attachment added: "xdpyinfo.txt" https://bugs.launchpad.net/bugs/1873942/+attachment/5357337/+files/xdpyinfo.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1873942 Title: gnome-screenshot takes a screenshot of the wrong screen Status in wayland package in Ubuntu: New Bug description: I have a dual monitor setup, with the external monitor defined as the "primary" one (and the laptop one secondary). When using the Shift + PrtScr shortcut and choosing an area on the external monitor, the screenshot saved in ~/Pictures shows this area but on the _laptop_ screen. (Choosing an area on the laptop screen works OK.) I use the vanilla Gnome session (with Wayland), installed with apt. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-screenshot 3.36.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Uname: Linux 5.4.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Apr 20 20:58:46 2020 InstallationDate: Installed on 2020-04-11 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-screenshot UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-24-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-25-generic, x86_64: installed GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 620 [1043:16e0] InstallationDate: Installed on 2020-04-11 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC WebCam Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK Package: wayland (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-25-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Tags: focal wayland-session ubuntu Uname: Linux 5.4.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/17/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.312 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.312:bd04/17/2019:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: UX410UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1873942/+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 1873942] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1873942/+attachment/5357322/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1873942 Title: gnome-screenshot takes a screenshot of the wrong screen Status in wayland package in Ubuntu: New Bug description: I have a dual monitor setup, with the external monitor defined as the "primary" one (and the laptop one secondary). When using the Shift + PrtScr shortcut and choosing an area on the external monitor, the screenshot saved in ~/Pictures shows this area but on the _laptop_ screen. (Choosing an area on the laptop screen works OK.) I use the vanilla Gnome session (with Wayland), installed with apt. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-screenshot 3.36.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Uname: Linux 5.4.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Apr 20 20:58:46 2020 InstallationDate: Installed on 2020-04-11 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-screenshot UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-24-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-25-generic, x86_64: installed GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 620 [1043:16e0] InstallationDate: Installed on 2020-04-11 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC WebCam Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK Package: wayland (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-25-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Tags: focal wayland-session ubuntu Uname: Linux 5.4.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/17/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.312 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.312:bd04/17/2019:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: UX410UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1873942/+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 1873942] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1873942/+attachment/5357325/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1873942 Title: gnome-screenshot takes a screenshot of the wrong screen Status in wayland package in Ubuntu: New Bug description: I have a dual monitor setup, with the external monitor defined as the "primary" one (and the laptop one secondary). When using the Shift + PrtScr shortcut and choosing an area on the external monitor, the screenshot saved in ~/Pictures shows this area but on the _laptop_ screen. (Choosing an area on the laptop screen works OK.) I use the vanilla Gnome session (with Wayland), installed with apt. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-screenshot 3.36.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Uname: Linux 5.4.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Apr 20 20:58:46 2020 InstallationDate: Installed on 2020-04-11 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-screenshot UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-24-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-25-generic, x86_64: installed GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 620 [1043:16e0] InstallationDate: Installed on 2020-04-11 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC WebCam Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK Package: wayland (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-25-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Tags: focal wayland-session ubuntu Uname: Linux 5.4.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/17/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.312 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.312:bd04/17/2019:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: UX410UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1873942/+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 1873942] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1873942/+attachment/5357330/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1873942 Title: gnome-screenshot takes a screenshot of the wrong screen Status in wayland package in Ubuntu: New Bug description: I have a dual monitor setup, with the external monitor defined as the "primary" one (and the laptop one secondary). When using the Shift + PrtScr shortcut and choosing an area on the external monitor, the screenshot saved in ~/Pictures shows this area but on the _laptop_ screen. (Choosing an area on the laptop screen works OK.) I use the vanilla Gnome session (with Wayland), installed with apt. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-screenshot 3.36.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Uname: Linux 5.4.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Apr 20 20:58:46 2020 InstallationDate: Installed on 2020-04-11 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-screenshot UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-24-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-25-generic, x86_64: installed GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 620 [1043:16e0] InstallationDate: Installed on 2020-04-11 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC WebCam Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK Package: wayland (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-25-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Tags: focal wayland-session ubuntu Uname: Linux 5.4.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/17/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.312 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.312:bd04/17/2019:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: UX410UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1873942/+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 1873942] XorgLog.txt
apport information ** Attachment added: "XorgLog.txt" https://bugs.launchpad.net/bugs/1873942/+attachment/5357334/+files/XorgLog.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1873942 Title: gnome-screenshot takes a screenshot of the wrong screen Status in wayland package in Ubuntu: New Bug description: I have a dual monitor setup, with the external monitor defined as the "primary" one (and the laptop one secondary). When using the Shift + PrtScr shortcut and choosing an area on the external monitor, the screenshot saved in ~/Pictures shows this area but on the _laptop_ screen. (Choosing an area on the laptop screen works OK.) I use the vanilla Gnome session (with Wayland), installed with apt. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-screenshot 3.36.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Uname: Linux 5.4.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Apr 20 20:58:46 2020 InstallationDate: Installed on 2020-04-11 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-screenshot UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-24-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-25-generic, x86_64: installed GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 620 [1043:16e0] InstallationDate: Installed on 2020-04-11 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC WebCam Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK Package: wayland (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-25-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Tags: focal wayland-session ubuntu Uname: Linux 5.4.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/17/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.312 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.312:bd04/17/2019:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: UX410UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1873942/+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 1873942] MonitorsUser.xml.txt
apport information ** Attachment added: "MonitorsUser.xml.txt" https://bugs.launchpad.net/bugs/1873942/+attachment/5357328/+files/MonitorsUser.xml.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1873942 Title: gnome-screenshot takes a screenshot of the wrong screen Status in wayland package in Ubuntu: New Bug description: I have a dual monitor setup, with the external monitor defined as the "primary" one (and the laptop one secondary). When using the Shift + PrtScr shortcut and choosing an area on the external monitor, the screenshot saved in ~/Pictures shows this area but on the _laptop_ screen. (Choosing an area on the laptop screen works OK.) I use the vanilla Gnome session (with Wayland), installed with apt. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-screenshot 3.36.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Uname: Linux 5.4.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Apr 20 20:58:46 2020 InstallationDate: Installed on 2020-04-11 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-screenshot UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-24-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-25-generic, x86_64: installed GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 620 [1043:16e0] InstallationDate: Installed on 2020-04-11 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC WebCam Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK Package: wayland (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-25-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Tags: focal wayland-session ubuntu Uname: Linux 5.4.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/17/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.312 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.312:bd04/17/2019:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: UX410UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1873942/+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 1873942] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1873942/+attachment/5357331/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1873942 Title: gnome-screenshot takes a screenshot of the wrong screen Status in wayland package in Ubuntu: New Bug description: I have a dual monitor setup, with the external monitor defined as the "primary" one (and the laptop one secondary). When using the Shift + PrtScr shortcut and choosing an area on the external monitor, the screenshot saved in ~/Pictures shows this area but on the _laptop_ screen. (Choosing an area on the laptop screen works OK.) I use the vanilla Gnome session (with Wayland), installed with apt. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-screenshot 3.36.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Uname: Linux 5.4.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Apr 20 20:58:46 2020 InstallationDate: Installed on 2020-04-11 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-screenshot UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-24-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-25-generic, x86_64: installed GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 620 [1043:16e0] InstallationDate: Installed on 2020-04-11 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC WebCam Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK Package: wayland (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-25-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Tags: focal wayland-session ubuntu Uname: Linux 5.4.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/17/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.312 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.312:bd04/17/2019:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: UX410UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1873942/+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 1873942] DpkgLog.txt
apport information ** Attachment added: "DpkgLog.txt" https://bugs.launchpad.net/bugs/1873942/+attachment/5357323/+files/DpkgLog.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1873942 Title: gnome-screenshot takes a screenshot of the wrong screen Status in wayland package in Ubuntu: New Bug description: I have a dual monitor setup, with the external monitor defined as the "primary" one (and the laptop one secondary). When using the Shift + PrtScr shortcut and choosing an area on the external monitor, the screenshot saved in ~/Pictures shows this area but on the _laptop_ screen. (Choosing an area on the laptop screen works OK.) I use the vanilla Gnome session (with Wayland), installed with apt. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-screenshot 3.36.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Uname: Linux 5.4.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Apr 20 20:58:46 2020 InstallationDate: Installed on 2020-04-11 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-screenshot UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-24-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-25-generic, x86_64: installed GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 620 [1043:16e0] InstallationDate: Installed on 2020-04-11 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC WebCam Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK Package: wayland (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-25-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Tags: focal wayland-session ubuntu Uname: Linux 5.4.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/17/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.312 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.312:bd04/17/2019:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: UX410UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1873942/+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 1873942] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1873942/+attachment/5357326/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1873942 Title: gnome-screenshot takes a screenshot of the wrong screen Status in wayland package in Ubuntu: New Bug description: I have a dual monitor setup, with the external monitor defined as the "primary" one (and the laptop one secondary). When using the Shift + PrtScr shortcut and choosing an area on the external monitor, the screenshot saved in ~/Pictures shows this area but on the _laptop_ screen. (Choosing an area on the laptop screen works OK.) I use the vanilla Gnome session (with Wayland), installed with apt. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-screenshot 3.36.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Uname: Linux 5.4.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Apr 20 20:58:46 2020 InstallationDate: Installed on 2020-04-11 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-screenshot UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-24-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-25-generic, x86_64: installed GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 620 [1043:16e0] InstallationDate: Installed on 2020-04-11 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC WebCam Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK Package: wayland (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-25-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Tags: focal wayland-session ubuntu Uname: Linux 5.4.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/17/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.312 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.312:bd04/17/2019:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: UX410UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1873942/+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 1873942] Xrandr.txt
apport information ** Attachment added: "Xrandr.txt" https://bugs.launchpad.net/bugs/1873942/+attachment/5357336/+files/Xrandr.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1873942 Title: gnome-screenshot takes a screenshot of the wrong screen Status in wayland package in Ubuntu: New Bug description: I have a dual monitor setup, with the external monitor defined as the "primary" one (and the laptop one secondary). When using the Shift + PrtScr shortcut and choosing an area on the external monitor, the screenshot saved in ~/Pictures shows this area but on the _laptop_ screen. (Choosing an area on the laptop screen works OK.) I use the vanilla Gnome session (with Wayland), installed with apt. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-screenshot 3.36.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Uname: Linux 5.4.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Apr 20 20:58:46 2020 InstallationDate: Installed on 2020-04-11 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-screenshot UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-24-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-25-generic, x86_64: installed GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 620 [1043:16e0] InstallationDate: Installed on 2020-04-11 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC WebCam Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK Package: wayland (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-25-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Tags: focal wayland-session ubuntu Uname: Linux 5.4.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/17/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.312 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.312:bd04/17/2019:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: UX410UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1873942/+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 1873942] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1873942/+attachment/5357327/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1873942 Title: gnome-screenshot takes a screenshot of the wrong screen Status in wayland package in Ubuntu: New Bug description: I have a dual monitor setup, with the external monitor defined as the "primary" one (and the laptop one secondary). When using the Shift + PrtScr shortcut and choosing an area on the external monitor, the screenshot saved in ~/Pictures shows this area but on the _laptop_ screen. (Choosing an area on the laptop screen works OK.) I use the vanilla Gnome session (with Wayland), installed with apt. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-screenshot 3.36.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Uname: Linux 5.4.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Apr 20 20:58:46 2020 InstallationDate: Installed on 2020-04-11 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-screenshot UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-24-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-25-generic, x86_64: installed GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 620 [1043:16e0] InstallationDate: Installed on 2020-04-11 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC WebCam Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK Package: wayland (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-25-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Tags: focal wayland-session ubuntu Uname: Linux 5.4.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/17/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.312 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.312:bd04/17/2019:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: UX410UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1873942/+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 1858463] Re: Desktop freezing while SSD under heavy load
Still happening with 20.04 ** Package changed: ubuntu-meta (Ubuntu) => linux (Ubuntu) ** Tags added: apport-collected focal ** Description changed: Every time my SSD is under heavy writing load (e.g. copying large files from a USB stick, or downloading an ISO from a fast website), the entire Ubuntu (Gnome) desktop, including mouse pointer, freezes. My computer is an Asus UX410UAK with a Micron 1100 SSD. guillaume@massada:~$ sudo dmidecode | grep -i UX Version: UX410UAK.308 Product Name: UX410UAK Family: UX Product Name: UX410UAK guillaume@massada:~$ cat /proc/scsi/scsi Attached devices: Host: scsi2 Channel: 00 Id: 00 Lun: 00 Vendor: ATA Model: Micron_1100_MTFD Rev: A020 Type: Direct-AccessANSI SCSI revision: 05 This is a recurring problem, and has always been with this machine (including previous kernel and Ubuntu versions, at least for the past 2 years). ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-desktop (not installed) ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Jan 6 18:20:01 2020 InstallationDate: Installed on 2018-07-28 (526 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-meta UpgradeStatus: Upgraded to eoan on 2019-10-18 (80 days ago) + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: guillaume 1685 F pulseaudio + CasperMD5CheckResult: skip + CurrentDesktop: GNOME + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2020-04-11 (9 days ago) + InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) + Lsusb: + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 004: ID 8087:0a2b Intel Corp. + Bus 001 Device 003: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC WebCam + Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + MachineType: ASUSTeK COMPUTER INC. UX410UAK + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=fr_FR.UTF-8 + SHELL=/bin/bash + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-25-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 + RelatedPackageVersions: + linux-restricted-modules-5.4.0-25-generic N/A + linux-backports-modules-5.4.0-25-generic N/A + linux-firmware1.187 + Tags: focal wayland-session + Uname: Linux 5.4.0-25-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 04/17/2019 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: UX410UAK.312 + dmi.board.asset.tag: ATN12345678901234567 + dmi.board.name: UX410UAK + dmi.board.vendor: ASUSTeK COMPUTER INC. + dmi.board.version: 1.0 + dmi.chassis.asset.tag: No Asset Tag + dmi.chassis.type: 10 + dmi.chassis.vendor: ASUSTeK COMPUTER INC. + dmi.chassis.version: 1.0 + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.312:bd04/17/2019:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: + dmi.product.family: ZenBook + dmi.product.name: UX410UAK + dmi.product.version: 1.0 + dmi.sys.vendor: ASUSTeK COMPUTER INC. -- 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/1858463 Title: Desktop freezing while SSD under heavy load Status in linux package in Ubuntu: Confirmed Bug description: Every time my SSD is under heavy writing load (e.g. copying large files from a USB stick, or downloading an ISO from a fast website), the entire Ubuntu (Gnome) desktop, including mouse pointer, freezes. My computer is an Asus UX410UAK with a Micron 1100 SSD. guillaume@massada:~$ sudo dmidecode | grep -i UX Version: UX410UAK.308 Product Name: UX410UAK Family: UX Product Name: UX410UAK guillaume@massada:~$ cat /proc/scsi/scsi Attached devices: Host: scsi2 Channel: 00 Id: 00 Lun: 00 Vendor: ATA Model: Micron_1100_MTFD Rev: A020 Type: Direct-AccessANSI SCSI revision: 05 This is a recurring problem, and has always been with this machine (including previous kernel and Ubuntu versions, at least
[Desktop-packages] [Bug 1869225] [NEW] nm-applet should not attempt to create system-wide WiFi connections for regular users
Public bug reported: When a standard (non-administrator user) selects a WiFi network using the applet, the applet attempts to create a system connection, instead of a user connection, and thus it asks for an administrator user's password. On the other hand, if the same standard user opens the WiFi settings and selects a network there, no admin password is requested, as the connection is created for this user only, not system-wide. This is a workaround I discovered recently (see https://askubuntu.com/a/1163852/375543). This has bitten me several times, as I hand out laptops for new users; when they get home, they try to connect to their network and as I have no other way to help them (before I discovered the workaround), I ended up giving them the administrator password. The applet should not attempt to create a system-wide connection for users that are unable to do it. There is no security implication to implement this, as the users are able to create a connection anyway with the workaround mentioned above. But the improvement in terms of UX would be huge. ** Affects: network-manager-applet (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1869225 Title: nm-applet should not attempt to create system-wide WiFi connections for regular users Status in network-manager-applet package in Ubuntu: New Bug description: When a standard (non-administrator user) selects a WiFi network using the applet, the applet attempts to create a system connection, instead of a user connection, and thus it asks for an administrator user's password. On the other hand, if the same standard user opens the WiFi settings and selects a network there, no admin password is requested, as the connection is created for this user only, not system-wide. This is a workaround I discovered recently (see https://askubuntu.com/a/1163852/375543). This has bitten me several times, as I hand out laptops for new users; when they get home, they try to connect to their network and as I have no other way to help them (before I discovered the workaround), I ended up giving them the administrator password. The applet should not attempt to create a system-wide connection for users that are unable to do it. There is no security implication to implement this, as the users are able to create a connection anyway with the workaround mentioned above. But the improvement in terms of UX would be huge. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1869225/+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 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support.
Someone is working on adding wideband support to pulseaudio (this currently requires ofono): https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/254 -- 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/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support. Status in PulseAudio: New Status in bluez package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Triaged Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+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 1864274] Re: crunchy pixels
I've added instructions in the mesa bug on how to correctly set the environment variable to workaround the issue: https://gitlab.freedesktop.org/mesa/mesa/issues/2552#note_432595 -- 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/1864274 Title: crunchy pixels Status in Mesa: Unknown Status in mesa package in Ubuntu: Confirmed Bug description: Hello, after upgrading firefox (and many other packages) on focal today, I've got some video artifacts in firefox. When typing in text boxes and text fields, the new character is drawn very slowly, pixel-by-pixel, and isn't complete until the cursor has moved on. When larger portions of the screen are updated, it looks a lot like the entire window is being run through a video codec or you can see parts of the video memory from other processes. (But it looks more deliberate and predictable than either of these descriptions.) So far Firefox is the only application I've found that is affected. urxvt, libreoffice, xfontsel, glxgears all seem to work as expected. I did get cairo package update today, but the changelog is just: pango1.0 (1.44.7-1ubuntu2) focal; urgency=medium * No-change rebuild with fixed binutils on arm64. -- Matthias Klose Sat, 08 Feb 2020 11:15:23 + And an xorg update: xorg (1:7.7+19ubuntu14) focal; urgency=medium * No-change rebuild with fixed binutils on arm64. -- Matthias Klose Sat, 08 Feb 2020 11:21:28 + So I don't believe these are involved. 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620 (rev 07) Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 73.0.1+build1-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AddonCompatCheckDisabled: False AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-14-generic. ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sarnold3296 F pulseaudio /dev/snd/controlC0: sarnold3296 F pulseaudio BuildID: 20200217142647 Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0x2fe1028000 irq 144' Mixer name : 'Realtek ALC285' Components : 'HDA:10ec0285,17aa225c,0012 HDA:8086280b,80860101,0010' Controls : 53 Simple ctrls : 15 Card1.Amixer.info: Card hw:1 'Audio'/'Generic ThinkPad Dock USB Audio at usb-:00:14.0-4.2.4, high speed' Mixer name : 'USB Mixer' Components : 'USB17ef:306f' Controls : 9 Simple ctrls : 4 Channel: Unavailable Date: Sat Feb 22 05:41:10 2020 ForcedLayersAccel: False IncompatibleExtensions: Pentadactyl - pentadac...@dactyl.googlecode.com English (GB) Language Pack - langpack-en...@firefox.mozilla.org English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org Default - {972ce4c6-7e08-4474-a285-3208198ce6fd} IpRoute: default via 192.168.0.1 dev enp0s31f6 proto dhcp metric 100 10.23.231.0/24 dev lxdbr0 proto kernel scope link src 10.23.231.1 192.168.0.0/24 dev enp0s31f6 proto kernel scope link src 192.168.0.34 metric 100 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown MostRecentCrashID: bp-ea952d4d-f25a-4ced-893c-8cabb2160112 PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:737 PrefSources: prefs.js ProcEnviron: TERM=rxvt-unicode-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=73.0.1/20200217142647 (In use) RunningIncompatibleAddons: True SourcePackage: firefox UpgradeStatus: Upgraded to focal on 2020-01-24 (28 days ago) dmi.bios.date: 11/25/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET69W (1.44 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KHCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN23ET69W(1.44):bd11/25/2019:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KHCTO1WW dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1864274/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-packages] [Bug 1853762] Re: Headphones stop working until pairing again
This may have something to do with another user already being logged in another Gnome Session. -- 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/1853762 Title: Headphones stop working until pairing again Status in bluez package in Ubuntu: New Status in gnome-control-center package in Ubuntu: New Bug description: I'm using Marshall MID ANC headphones with Ubuntu 19.10. Every now and then, I won't be able to use them without re-pairing first (like today - see logs). After re-pairing, everything works again for a while : I can switch off and on the headphones, reboot... Until it breaks again. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Nov 24 19:13:40 2019 InstallationDate: Installed on 2018-07-28 (483 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC WebCam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-23-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to eoan on 2019-10-18 (37 days ago) dmi.bios.date: 11/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.308:bd11/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX410UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. hciconfig: hci0:Type: Primary Bus: USB BD Address: 14:AB:C5:7E:41:26 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:319948 acl:71 sco:0 events:45583 errors:0 TX bytes:37324973 acl:43061 sco:0 commands:2478 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1853762/+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 1847551] Re: Mutter 3.34.1 broke Night Light, screen color profiles in Wayland sessions
Apologies: it works. But it looks like that GNOME thinks that 8pm is not night here in western Europe, at this time of year! :-D -- 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/1847551 Title: Mutter 3.34.1 broke Night Light, screen color profiles in Wayland sessions Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Eoan: Fix Released Status in mutter source package in Focal: Fix Released Bug description: [ Impact ] Upgrading Mutter 3.34.0 to 3.34.1 has broken Night Light and screen color profile switching. The commit at fault is 104bdde746c9ceccd9e9ab09b22ef228b8f7026e “kms: Predict state changes when processing update” (which was intended to fix LP bug 1847044). [ Test case ] - From gnome-control-center display panel, enable the Night Light - Force it on, and ensure that the display color temperature increases [ Regression potential ] Display gamma value might be incorrect Upstream issue: https://gitlab.gnome.org/GNOME/mutter/issues/851 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1847551/+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 1847551] Re: Mutter 3.34.1 broke Night Light, screen color profiles in Wayland sessions
I don't know why... The fix worked until yesterday, but the problem has come back! guillaume@massada:~$ dpkg -l |grep -i mutter ii gir1.2-mutter-5:amd64 3.34.1+git20191107-1ubuntu1~19.10.1amd64GObject introspection data for Mutter ii libmutter-5-0:amd64 3.34.1+git20191107-1ubuntu1~19.10.1amd64window manager library from the Mutter window manager ii mutter 3.34.1+git20191107-1ubuntu1~19.10.1amd64Example window manager using GNOME's window manager library ii mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1all shared files for the Mutter window manager -- 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/1847551 Title: Mutter 3.34.1 broke Night Light, screen color profiles in Wayland sessions Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Eoan: Fix Released Status in mutter source package in Focal: Fix Released Bug description: [ Impact ] Upgrading Mutter 3.34.0 to 3.34.1 has broken Night Light and screen color profile switching. The commit at fault is 104bdde746c9ceccd9e9ab09b22ef228b8f7026e “kms: Predict state changes when processing update” (which was intended to fix LP bug 1847044). [ Test case ] - From gnome-control-center display panel, enable the Night Light - Force it on, and ensure that the display color temperature increases [ Regression potential ] Display gamma value might be incorrect Upstream issue: https://gitlab.gnome.org/GNOME/mutter/issues/851 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1847551/+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 1852694] Re: Night Light stuck on Wayland
I tried to file it against Wayland but Apport would'nt let me do it! Le ven. 15 nov. 2019 à 10:00, Timo Aaltonen a écrit : > not logical to file it against the xserver then > > ** Package changed: xorg-server (Ubuntu) => gnome-shell (Ubuntu) > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1852694 > > Title: > Night Light stuck on Wayland > > Status in gnome-shell package in Ubuntu: > New > > Bug description: > Gnome Night Light stopped working correctly in the Wayland session with > standard Ubuntu. > Night Light does not switch on automatically. I can't switch it on > manyally either (the toggle works well, but the screen doesn't change). > If I log off and log on to an X-Server session, Night Lights works again > normally. For example, it turns on at night - but then stays on all day > (even if the applet disappears as expected) when I go back to my Wayland > session. > > ProblemType: Bug > DistroRelease: Ubuntu 19.10 > Package: xwayland 2:1.20.5+git20191008-0ubuntu1 > ProcVersionSignature: Ubuntu 5.3.0-22.24-generic 5.3.7 > Uname: Linux 5.3.0-22-generic x86_64 > ApportVersion: 2.20.11-0ubuntu8.2 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' > CompositorRunning: None > CurrentDesktop: GNOME > Date: Fri Nov 15 07:43:01 2019 > DistUpgraded: 2019-10-18 07:16:36,734 DEBUG Running PostInstallScript: > './xorg_fix_proprietary.py' > DistroCodename: eoan > DistroVariant: ubuntu > ExtraDebuggingInterest: Yes > GraphicsCard: >Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA > controller]) > Subsystem: ASUSTeK Computer Inc. HD Graphics 620 [1043:16e0] > InstallationDate: Installed on 2018-07-28 (474 days ago) > InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 > (20180725) > Lsusb: >Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub >Bus 001 Device 004: ID 8087:0a2b Intel Corp. >Bus 001 Device 003: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD > UVC WebCam >Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver >Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > MachineType: ASUSTeK COMPUTER INC. UX410UAK > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=fr_FR.UTF-8 >SHELL=/bin/bash > ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-22-generic > root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 > SourcePackage: xorg-server > UpgradeStatus: Upgraded to eoan on 2019-10-18 (28 days ago) > dmi.bios.date: 11/08/2017 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: UX410UAK.308 > dmi.board.asset.tag: ATN12345678901234567 > dmi.board.name: UX410UAK > dmi.board.vendor: ASUSTeK COMPUTER INC. > dmi.board.version: 1.0 > dmi.chassis.asset.tag: No Asset Tag > dmi.chassis.type: 10 > dmi.chassis.vendor: ASUSTeK COMPUTER INC. > dmi.chassis.version: 1.0 > dmi.modalias: > dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.308:bd11/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: > dmi.product.family: UX > dmi.product.name: UX410UAK > dmi.product.version: 1.0 > dmi.sys.vendor: ASUSTeK COMPUTER INC. > version.compiz: compiz N/A > 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 N/A > 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 > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1852694/+subscriptions > -- 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/1852694 Title: Night Light stuck on Wayland Status in gnome-shell package in Ubuntu: New Bug description: Gnome Night Light stopped working correctly in the Wayland session with standard Ubuntu. Night Light does not switch on automatically. I can't switch it on manyally either (the toggle works well, but the screen doesn't change). If I log off and log on to an X-Server session, Night Lights works again normally. For example, it turns on at night - but then stays on all day (even if the applet disappears as expected) when I go back to my Wayland session. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xwayland 2:1.20.5+git20191008-0ubuntu1 ProcVersionSignature:
[Desktop-packages] [Bug 1852694] Re: Night Light stuck on Wayland
By "X-Server" I mean standard Xorg. Everything used to work fine a few weeks ago on the same computer (with 19.04, before the upgrade to 19.10... and maybe a bit afterwards). -- 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/1852694 Title: Night Light stuck on Wayland Status in xorg-server package in Ubuntu: New Bug description: Gnome Night Light stopped working correctly in the Wayland session with standard Ubuntu. Night Light does not switch on automatically. I can't switch it on manyally either (the toggle works well, but the screen doesn't change). If I log off and log on to an X-Server session, Night Lights works again normally. For example, it turns on at night - but then stays on all day (even if the applet disappears as expected) when I go back to my Wayland session. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xwayland 2:1.20.5+git20191008-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-22.24-generic 5.3.7 Uname: Linux 5.3.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: GNOME Date: Fri Nov 15 07:43:01 2019 DistUpgraded: 2019-10-18 07:16:36,734 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 620 [1043:16e0] InstallationDate: Installed on 2018-07-28 (474 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC WebCam Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-22-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg-server UpgradeStatus: Upgraded to eoan on 2019-10-18 (28 days ago) dmi.bios.date: 11/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.308:bd11/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX410UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A 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 N/A 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1852694/+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 1852694] [NEW] Night Light stuck on Wayland
Public bug reported: Gnome Night Light stopped working correctly in the Wayland session with standard Ubuntu. Night Light does not switch on automatically. I can't switch it on manyally either (the toggle works well, but the screen doesn't change). If I log off and log on to an X-Server session, Night Lights works again normally. For example, it turns on at night - but then stays on all day (even if the applet disappears as expected) when I go back to my Wayland session. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xwayland 2:1.20.5+git20191008-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-22.24-generic 5.3.7 Uname: Linux 5.3.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: GNOME Date: Fri Nov 15 07:43:01 2019 DistUpgraded: 2019-10-18 07:16:36,734 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 620 [1043:16e0] InstallationDate: Installed on 2018-07-28 (474 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC WebCam Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-22-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg-server UpgradeStatus: Upgraded to eoan on 2019-10-18 (28 days ago) dmi.bios.date: 11/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.308:bd11/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX410UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A 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 N/A 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 ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ubuntu wayland-session -- 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/1852694 Title: Night Light stuck on Wayland Status in xorg-server package in Ubuntu: New Bug description: Gnome Night Light stopped working correctly in the Wayland session with standard Ubuntu. Night Light does not switch on automatically. I can't switch it on manyally either (the toggle works well, but the screen doesn't change). If I log off and log on to an X-Server session, Night Lights works again normally. For example, it turns on at night - but then stays on all day (even if the applet disappears as expected) when I go back to my Wayland session. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xwayland 2:1.20.5+git20191008-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-22.24-generic 5.3.7 Uname: Linux 5.3.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: GNOME Date: Fri Nov 15 07:43:01 2019 DistUpgraded: 2019-10-18 07:16:36,734 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 620 [1043:16e0] InstallationDate: Installed on 2018-07-28 (474 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic
[Desktop-packages] [Bug 1838441] [NEW] Metric length units conversion malformed expression
Public bug reported: Version 3.22.1, in Advanced Mode Select Length > Feet and any metric unit that ends with 'metres' (Kilometres, Metres, etc.) Now press 'to' button. It says 'Malformed expression'. It's only a typo because 'Metres' becomes 'meter'. If I correct 'meter' to 'metre' manually, it works fine. Language and Region settings on Ubuntu : English(Canada), Canada ** Affects: gnome-calculator (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Calc_bug.gif" https://bugs.launchpad.net/bugs/1838441/+attachment/5280038/+files/Calc_bug.gif -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calculator in Ubuntu. https://bugs.launchpad.net/bugs/1838441 Title: Metric length units conversion malformed expression Status in gnome-calculator package in Ubuntu: New Bug description: Version 3.22.1, in Advanced Mode Select Length > Feet and any metric unit that ends with 'metres' (Kilometres, Metres, etc.) Now press 'to' button. It says 'Malformed expression'. It's only a typo because 'Metres' becomes 'meter'. If I correct 'meter' to 'metre' manually, it works fine. Language and Region settings on Ubuntu : English(Canada), Canada To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1838441/+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 1827727]
See Also: → https://webcompat.com/issues/30576, https://webcompat.com/issues/30578, https://webcompat.com/issues/30584, https://webcompat.com/issues/30588, https://webcompat.com/issues/30600, https://webcompat.com/issues/30603, https://webcompat.com/issues/30637, https://webcompat.com/issues/30638, https://webcompat.com/issues/30643, https://webcompat.com/issues/30645 -- 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/1827727 Title: All plugins disabled due to expired cert Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: In Progress Bug description: See https://bugzilla.mozilla.org/show_bug.cgi?id=1548973 Due to expiration of an intermediate cert, all plugins were disabled. Firefox pushed a fix via 'Studies' option, but this seems to be disabled by default in Ubuntu builds? When this is disabled, no update is getting pushed! Think we need to get a fix into repositories asap :) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1827727/+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 1827727]
See Also: → https://webcompat.com/issues/30556, https://webcompat.com/issues/30561, https://webcompat.com/issues/30562, https://webcompat.com/issues/30563, https://webcompat.com/issues/30564, https://webcompat.com/issues/30565, https://webcompat.com/issues/30566, https://webcompat.com/issues/30571, https://webcompat.com/issues/30572 -- 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/1827727 Title: All plugins disabled due to expired cert Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: In Progress Bug description: See https://bugzilla.mozilla.org/show_bug.cgi?id=1548973 Due to expiration of an intermediate cert, all plugins were disabled. Firefox pushed a fix via 'Studies' option, but this seems to be disabled by default in Ubuntu builds? When this is disabled, no update is getting pushed! Think we need to get a fix into repositories asap :) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1827727/+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 1827727]
See Also: → https://webcompat.com/issues/30522, https://webcompat.com/issues/30529, https://webcompat.com/issues/30530, https://webcompat.com/issues/30534, https://webcompat.com/issues/30536, https://webcompat.com/issues/30539 -- 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/1827727 Title: All plugins disabled due to expired cert Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: In Progress Bug description: See https://bugzilla.mozilla.org/show_bug.cgi?id=1548973 Due to expiration of an intermediate cert, all plugins were disabled. Firefox pushed a fix via 'Studies' option, but this seems to be disabled by default in Ubuntu builds? When this is disabled, no update is getting pushed! Think we need to get a fix into repositories asap :) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1827727/+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 1767740] Re: gnome-shell crashes at startup - segfault in nouveau_dri.so
** Summary changed: - gnome-shell crashes at startup - segfault in nouveau_dri.sn + gnome-shell crashes at startup - segfault in nouveau_dri.so -- 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/1767740 Title: gnome-shell crashes at startup - segfault in nouveau_dri.so Status in mesa package in Ubuntu: New Bug description: With a live USB stick or a freshly installed version of 18.04, gnome- shell crashes at startup. I get this error in dmesg: gnome-shell[]: segfault at xx ip xx sp xx error 4 in nouveau_dri.so[] The computer is a MacBook Pro with a GeForce 320M GPU. Using the proprietary driver listed in the "additional drivers" tab doesn't work either (I get a black screen at startup with no access to a virtual terminal). Everything was fine on 16.04, with nouveau or nvidia drivers. The only workaround is to blacklist the nouveau driver. I have of course very poor performance then. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Apr 29 01:34:38 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation MCP89 [GeForce 320M] [10de:08a0] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. MCP89 [GeForce 320M] [106b:00c2] InstallationDate: Installed on 2018-04-28 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Apple Inc. MacBookPro7,1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=8a41bdcd-9c0e-41b3-8111-94661a72e400 ro quiet splash vt.handoff=1 SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/01/10 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP71.88Z.0039.B0B.1006012305 dmi.board.name: Mac-F222BEC8 dmi.board.vendor: Apple Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F222BEC8 dmi.modalias: dmi:bvnAppleInc.:bvrMBP71.88Z.0039.B0B.1006012305:bd06/01/10:svnAppleInc.:pnMacBookPro7,1:pvr1.0:rvnAppleInc.:rnMac-F222BEC8:rvr:cvnAppleInc.:ct10:cvrMac-F222BEC8: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro7,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1767740/+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 1767740] [NEW] gnome-shell crashes at startup - segfault in nouveau_dri.sn
Public bug reported: With a live USB stick or a freshly installed version of 18.04, gnome- shell crashes at startup. I get this error in dmesg: gnome-shell[]: segfault at xx ip xx sp xx error 4 in nouveau_dri.so[] The computer is a MacBook Pro with a GeForce 320M GPU. Using the proprietary driver listed in the "additional drivers" tab doesn't work either (I get a black screen at startup with no access to a virtual terminal). Everything was fine on 16.04, with nouveau or nvidia drivers. The only workaround is to blacklist the nouveau driver. I have of course very poor performance then. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Apr 29 01:34:38 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation MCP89 [GeForce 320M] [10de:08a0] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. MCP89 [GeForce 320M] [106b:00c2] InstallationDate: Installed on 2018-04-28 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Apple Inc. MacBookPro7,1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=8a41bdcd-9c0e-41b3-8111-94661a72e400 ro quiet splash vt.handoff=1 SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/01/10 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP71.88Z.0039.B0B.1006012305 dmi.board.name: Mac-F222BEC8 dmi.board.vendor: Apple Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F222BEC8 dmi.modalias: dmi:bvnAppleInc.:bvrMBP71.88Z.0039.B0B.1006012305:bd06/01/10:svnAppleInc.:pnMacBookPro7,1:pvr1.0:rvnAppleInc.:rnMac-F222BEC8:rvr:cvnAppleInc.:ct10:cvrMac-F222BEC8: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro7,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 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: mesa (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- 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/1767740 Title: gnome-shell crashes at startup - segfault in nouveau_dri.sn Status in mesa package in Ubuntu: New Bug description: With a live USB stick or a freshly installed version of 18.04, gnome- shell crashes at startup. I get this error in dmesg: gnome-shell[]: segfault at xx ip xx sp xx error 4 in nouveau_dri.so[] The computer is a MacBook Pro with a GeForce 320M GPU. Using the proprietary driver listed in the "additional drivers" tab doesn't work either (I get a black screen at startup with no access to a virtual terminal). Everything was fine on 16.04, with nouveau or nvidia drivers. The only workaround is to blacklist the nouveau driver. I have of course very poor performance then. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Apr 29 01:34:38 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation MCP89 [GeForce 320M] [10de:08a0] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. MCP89 [GeForce 320M] [106b:00c2] InstallationDate: Installed on 2018-04-28 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType:
[Desktop-packages] [Bug 1390709] Re: Wifi doesn't reconnect after waking from sleep
For me it happens on Ubuntu 18.04. I'm on a surfacebook. Directly if my pc go sleep, i lost the wifi connection. I've to restart to have wifi connection. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1390709 Title: Wifi doesn't reconnect after waking from sleep Status in network-manager package in Ubuntu: Confirmed Bug description: Upgraded from 14.04 to 14.10. Before Wifi would reconnect after waking up from sleep mode. After Update reconnect fails with wlan0: aborting authentication with 1c:c6:3c:95:e7:74 by local choice (Reason: 3=DEAUTH_LEAVING). I worked around this by killing wpa_supplicant with a script in /etc/pm/sleep.d #!/bin/sh case "$1" in thaw|resume) { killall wpa_supplicant ; } 2>/dev/null ;; *) ;; esac exit $? ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: network-manager 0.9.8.8-0ubuntu28 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: KDE Date: Sat Nov 8 11:43:15 2014 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-04-19 (567 days ago) InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130402.1) IpRoute: default via 192.168.138.251 dev wlan0 proto static 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 192.168.138.0/24 dev wlan0 proto kernel scope link src 192.168.138.143 metric 9 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to utopic on 2014-11-07 (0 days ago) nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.8connected enabled enabled enabledenabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1390709/+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 1377653] Re: HDMI sound output not detected / NVIDIA optimus laptop
Same! #19 with #24 works! Ubuntu 16.04 ASUS - ROG G502VS laptop nvidia 1070 / driver 390.25 Intel(R) Core(TM) i7-6700HQ CPU Thanks a lot! -- 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/1377653 Title: HDMI sound output not detected / NVIDIA optimus laptop Status in alsa-driver package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: Hi, not sure if this is an alsa or nvidia/nouveau bug. HDMI audio output doesn't appear in sound settings output panel. Audio works well on internal speakers, but it seems there is no way to make it output to hdmi... The laptop has optimus NVIDIA+Intel. The behaviour is the same with nouveau or nvidia proprietary driver. Please let me know if further testing is required ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sam2295 F pulseaudio CurrentDesktop: Unity CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied Date: Sun Oct 5 17:05:35 2014 InstallationDate: Installed on 2014-04-21 (166 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/02/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N56VZ.215 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N56VZ dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN56VZ.215:bd11/02/2012:svnASUSTeKCOMPUTERINC.:pnN56VZ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN56VZ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: N56VZ dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1377653/+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 1636282] Re: network-manager after suspend showing arrow icon instead of wifi icon and showing no wifi networks
After one week, I have not seen this issue anymore. Looks like solved for me. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1636282 Title: network-manager after suspend showing arrow icon instead of wifi icon and showing no wifi networks Status in network-manager package in Ubuntu: Confirmed Bug description: As requested by Mathieu Trudel-Lapierre (cyphermox) in bug #1589401 I'm creating my own bug report. 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu $ lsb_release -rd Description: Ubuntu 16.04.1 LTS Release: 16.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center $ apt-cache policy network-manager network-manager: Installiert: 1.2.2-0ubuntu0.16.04.3 Installationskandidat: 1.2.2-0ubuntu0.16.04.3 Versionstabelle: *** 1.2.2-0ubuntu0.16.04.3 500 500 http://ch.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.1.93-0ubuntu4 500 500 http://ch.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 3) What you expected to happen I'm connected by WiFi only, not by a wired connection. I expect to see the WiFi icon anytime while being connected to my WiFi network. Also, I expect to see all the WiFi networks around me (at least one other network with good reception and about 3 with bad reception). 4) What happened instead After waking up the laptop from suspend, there appears the ethernet icon (arrow symbols) instead of the WiFi icon. Also, in this state there are no other WiFi networks visible in the network-manager. However, the laptop is still connected with my WiFi and the connection works as usual. Using "service network-manager restart" in the console I can get the wireless icon back and all the other networks around me are visible again. This can be reproduced anytime and with 100% "success rate". The problem appeared with Ubuntu 16.10 and was persistent since. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.2-0ubuntu0.16.04.3 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Oct 24 20:06:09 2016 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-05-15 (161 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IpRoute: default via 192.168.1.1 dev wlo1 proto static metric 600 169.254.0.0/16 dev wlo1 scope link metric 1000 192.168.1.0/24 dev wlo1 proto kernel scope link src 192.168.1.244 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlo1wifi connected/org/freedesktop/NetworkManager/Devices/2 WiNet 2 162de978-4466-46b0-957b-5f9c141d702a /org/freedesktop/NetworkManager/ActiveConnection/1 eno1ethernet unavailable /org/freedesktop/NetworkManager/Devices/0 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.2connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1636282/+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 1636282] Re: network-manager after suspend showing arrow icon instead of wifi icon and showing no wifi networks
I have removed docker (docker.io) and ubuntu-fan and since then I can resume with working wifi. (so far so good) will kee you updated if it fails again. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1636282 Title: network-manager after suspend showing arrow icon instead of wifi icon and showing no wifi networks Status in network-manager package in Ubuntu: Confirmed Bug description: As requested by Mathieu Trudel-Lapierre (cyphermox) in bug #1589401 I'm creating my own bug report. 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu $ lsb_release -rd Description: Ubuntu 16.04.1 LTS Release: 16.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center $ apt-cache policy network-manager network-manager: Installiert: 1.2.2-0ubuntu0.16.04.3 Installationskandidat: 1.2.2-0ubuntu0.16.04.3 Versionstabelle: *** 1.2.2-0ubuntu0.16.04.3 500 500 http://ch.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.1.93-0ubuntu4 500 500 http://ch.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 3) What you expected to happen I'm connected by WiFi only, not by a wired connection. I expect to see the WiFi icon anytime while being connected to my WiFi network. Also, I expect to see all the WiFi networks around me (at least one other network with good reception and about 3 with bad reception). 4) What happened instead After waking up the laptop from suspend, there appears the ethernet icon (arrow symbols) instead of the WiFi icon. Also, in this state there are no other WiFi networks visible in the network-manager. However, the laptop is still connected with my WiFi and the connection works as usual. Using "service network-manager restart" in the console I can get the wireless icon back and all the other networks around me are visible again. This can be reproduced anytime and with 100% "success rate". The problem appeared with Ubuntu 16.10 and was persistent since. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.2-0ubuntu0.16.04.3 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Oct 24 20:06:09 2016 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-05-15 (161 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IpRoute: default via 192.168.1.1 dev wlo1 proto static metric 600 169.254.0.0/16 dev wlo1 scope link metric 1000 192.168.1.0/24 dev wlo1 proto kernel scope link src 192.168.1.244 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlo1wifi connected/org/freedesktop/NetworkManager/Devices/2 WiNet 2 162de978-4466-46b0-957b-5f9c141d702a /org/freedesktop/NetworkManager/ActiveConnection/1 eno1ethernet unavailable /org/freedesktop/NetworkManager/Devices/0 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.2connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1636282/+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 1636282] Re: network-manager after suspend showing arrow icon instead of wifi icon and showing no wifi networks
I still have the problem and I have maybe identified a culprit. in journalctl -xe, I have seen : ● wifi-resume.service loaded failed failed Restart networkmanager at resume -- L'unité (unit) NetworkManager.service a commencé à démarrer. janv. 26 19:43:09 XPS kernel: nfs: server newnas not responding, timed out janv. 26 19:43:15 XPS kernel: nfs: server newnas not responding, timed out janv. 26 19:43:39 XPS kernel: nfs: server newnas not responding, timed out Looks like a timeout on my NAS Synology. NFS shares are mounted using autofs. Looks like at resume it tries to reconnect before having the connection ? Don't know how to fix it. But it may ring a bell for you. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1636282 Title: network-manager after suspend showing arrow icon instead of wifi icon and showing no wifi networks Status in network-manager package in Ubuntu: Confirmed Bug description: As requested by Mathieu Trudel-Lapierre (cyphermox) in bug #1589401 I'm creating my own bug report. 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu $ lsb_release -rd Description: Ubuntu 16.04.1 LTS Release: 16.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center $ apt-cache policy network-manager network-manager: Installiert: 1.2.2-0ubuntu0.16.04.3 Installationskandidat: 1.2.2-0ubuntu0.16.04.3 Versionstabelle: *** 1.2.2-0ubuntu0.16.04.3 500 500 http://ch.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.1.93-0ubuntu4 500 500 http://ch.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 3) What you expected to happen I'm connected by WiFi only, not by a wired connection. I expect to see the WiFi icon anytime while being connected to my WiFi network. Also, I expect to see all the WiFi networks around me (at least one other network with good reception and about 3 with bad reception). 4) What happened instead After waking up the laptop from suspend, there appears the ethernet icon (arrow symbols) instead of the WiFi icon. Also, in this state there are no other WiFi networks visible in the network-manager. However, the laptop is still connected with my WiFi and the connection works as usual. Using "service network-manager restart" in the console I can get the wireless icon back and all the other networks around me are visible again. This can be reproduced anytime and with 100% "success rate". The problem appeared with Ubuntu 16.10 and was persistent since. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.2-0ubuntu0.16.04.3 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Oct 24 20:06:09 2016 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-05-15 (161 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IpRoute: default via 192.168.1.1 dev wlo1 proto static metric 600 169.254.0.0/16 dev wlo1 scope link metric 1000 192.168.1.0/24 dev wlo1 proto kernel scope link src 192.168.1.244 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlo1wifi connected/org/freedesktop/NetworkManager/Devices/2 WiNet 2 162de978-4466-46b0-957b-5f9c141d702a /org/freedesktop/NetworkManager/ActiveConnection/1 eno1ethernet unavailable /org/freedesktop/NetworkManager/Devices/0 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.2connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1636282/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-packages] [Bug 1635715] Re: failed to connect to device: Failed to connect to missing device /org/freedesktop/ColorManager/devices/cups_HP_LaserJet_1020
I confirm the same bug on own PC : Fresh install ubuntu-gnome 16.04.1 updated with Gnome 3.20 from ppa:gnome3-team/gnome3-staging Jan 4 16:09:08 PC systemd[1]: Started CUPS Scheduler. Jan 4 16:09:08 PC colord[1309]: (colord:1309): Cd-WARNING **: failed to get session [pid 8407]: Aucun périphérique ou adresse Jan 4 16:15:09 PC gnome-settings-daemon.desktop[2008]: (gnome-settings-daemon:2008): color-plugin-WARNING **: failed to connect to device: Failed to connect to missing device /org/freedesktop/ColorManager/devices/cups_HP_Color_LaserJet_MFP_M476dn Jan 4 16:43:23 PC systemd[1]: Started CUPS Scheduler. Jan 4 16:43:23 PC colord[1309]: (colord:1309): Cd-WARNING **: failed to get session [pid 8945]: Aucun périphérique ou adresse Jan 4 16:49:25 PC gnome-settings-daemon.desktop[2008]: (gnome-settings-daemon:2008): color-plugin-WARNING **: failed to connect to device: Failed to connect to missing device /org/freedesktop/ColorManager/devices/cups_HP_Color_LaserJet_MFP_M476dn -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1635715 Title: failed to connect to device: Failed to connect to missing device /org/freedesktop/ColorManager/devices/cups_HP_LaserJet_1020 Status in gnome-settings-daemon package in Ubuntu: New Bug description: The complete errors that are shown together are: Oct 18 08:20:51 localhost systemd[1]: Started CUPS Scheduler. Oct 18 08:20:51 localhost gnome-session[1504]: (gnome-settings-daemon:1533): color-plugin-WARNING **: failed to connect to device: Failed to connect to missing device /org/freedesktop/ColorManager/devices/cups_HP_LaserJet_1020 Oct 18 08:20:51 localhost gnome-session[1504]: (gnome-settings-daemon:1533): color-plugin-WARNING **: failed to connect to device: Failed to connect to missing device /org/freedesktop/ColorManager/devices/cups_PDF Distributor ID: Ubuntu Description: Ubuntu 16.04.1 LTS Release: 16.04 Codename: xenial gnome-settings-daemon: Installed: 3.18.2-0ubuntu3.1 Candidate: 3.18.2-0ubuntu3.1 Version table: *** 3.18.2-0ubuntu3.1 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages 100 /var/lib/dpkg/status 3.18.2-0ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages This happens quite frequently and I'm not sure of the cause. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1635715/+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 1636282] Re: network-manager after suspend showing arrow icon instead of wifi icon and showing no wifi networks
Unfortunately my workaround doesn't work anymore since 10 days. Looks like the script is not executed anymore when resuming from sleep. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1636282 Title: network-manager after suspend showing arrow icon instead of wifi icon and showing no wifi networks Status in network-manager package in Ubuntu: Confirmed Bug description: As requested by Mathieu Trudel-Lapierre (cyphermox) in bug #1589401 I'm creating my own bug report. 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu $ lsb_release -rd Description: Ubuntu 16.04.1 LTS Release: 16.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center $ apt-cache policy network-manager network-manager: Installiert: 1.2.2-0ubuntu0.16.04.3 Installationskandidat: 1.2.2-0ubuntu0.16.04.3 Versionstabelle: *** 1.2.2-0ubuntu0.16.04.3 500 500 http://ch.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.1.93-0ubuntu4 500 500 http://ch.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 3) What you expected to happen I'm connected by WiFi only, not by a wired connection. I expect to see the WiFi icon anytime while being connected to my WiFi network. Also, I expect to see all the WiFi networks around me (at least one other network with good reception and about 3 with bad reception). 4) What happened instead After waking up the laptop from suspend, there appears the ethernet icon (arrow symbols) instead of the WiFi icon. Also, in this state there are no other WiFi networks visible in the network-manager. However, the laptop is still connected with my WiFi and the connection works as usual. Using "service network-manager restart" in the console I can get the wireless icon back and all the other networks around me are visible again. This can be reproduced anytime and with 100% "success rate". The problem appeared with Ubuntu 16.10 and was persistent since. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.2-0ubuntu0.16.04.3 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Oct 24 20:06:09 2016 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-05-15 (161 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IpRoute: default via 192.168.1.1 dev wlo1 proto static metric 600 169.254.0.0/16 dev wlo1 scope link metric 1000 192.168.1.0/24 dev wlo1 proto kernel scope link src 192.168.1.244 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlo1wifi connected/org/freedesktop/NetworkManager/Devices/2 WiNet 2 162de978-4466-46b0-957b-5f9c141d702a /org/freedesktop/NetworkManager/ActiveConnection/1 eno1ethernet unavailable /org/freedesktop/NetworkManager/Devices/0 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.2connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1636282/+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 1636282] Re: network-manager after suspend showing arrow icon instead of wifi icon and showing no wifi networks
I confirm the same with yakkey on DELL XPS 13 developer edition (2015) lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.10 Release:16.10 Codename: yakkety LANG=C apt-cache policy network-manager network-manager: Installed: 1.2.4-0ubuntu1 Candidate: 1.2.4-0ubuntu1 Version table: *** 1.2.4-0ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu yakkety/main amd64 Packages 100 /var/lib/dpkg/status as a temporary work around I put a script here: /etc/pm/sleep.d/99_restart_network_manager That contains: #! /bin/sh case $1 in suspend|suspend_hybrid|hibernate) service network-manager restart ;; resume|thaw) # No need to do anything here : ;; esac As said before, it works only once after a suspend. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1636282 Title: network-manager after suspend showing arrow icon instead of wifi icon and showing no wifi networks Status in network-manager package in Ubuntu: Confirmed Bug description: As requested by Mathieu Trudel-Lapierre (cyphermox) in bug #1589401 I'm creating my own bug report. 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu $ lsb_release -rd Description: Ubuntu 16.04.1 LTS Release: 16.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center $ apt-cache policy network-manager network-manager: Installiert: 1.2.2-0ubuntu0.16.04.3 Installationskandidat: 1.2.2-0ubuntu0.16.04.3 Versionstabelle: *** 1.2.2-0ubuntu0.16.04.3 500 500 http://ch.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.1.93-0ubuntu4 500 500 http://ch.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 3) What you expected to happen I'm connected by WiFi only, not by a wired connection. I expect to see the WiFi icon anytime while being connected to my WiFi network. Also, I expect to see all the WiFi networks around me (at least one other network with good reception and about 3 with bad reception). 4) What happened instead After waking up the laptop from suspend, there appears the ethernet icon (arrow symbols) instead of the WiFi icon. Also, in this state there are no other WiFi networks visible in the network-manager. However, the laptop is still connected with my WiFi and the connection works as usual. Using "service network-manager restart" in the console I can get the wireless icon back and all the other networks around me are visible again. This can be reproduced anytime and with 100% "success rate". The problem appeared with Ubuntu 16.10 and was persistent since. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.2-0ubuntu0.16.04.3 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Oct 24 20:06:09 2016 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-05-15 (161 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IpRoute: default via 192.168.1.1 dev wlo1 proto static metric 600 169.254.0.0/16 dev wlo1 scope link metric 1000 192.168.1.0/24 dev wlo1 proto kernel scope link src 192.168.1.244 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlo1wifi connected/org/freedesktop/NetworkManager/Devices/2 WiNet 2 162de978-4466-46b0-957b-5f9c141d702a /org/freedesktop/NetworkManager/ActiveConnection/1 eno1ethernet unavailable /org/freedesktop/NetworkManager/Devices/0 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.2connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to:
[Desktop-packages] [Bug 1634412] Re: Unity8 session fails to start due to unity-system-compositor
Also, I don't know if there is an overlay-ppa for 16.10, but if there is, I did not install it on my machine, so I should be using pure 16.10 repos. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1634412 Title: Unity8 session fails to start due to unity-system-compositor Status in Light Display Manager: Incomplete Status in Unity System Compositor: Incomplete Status in lightdm package in Ubuntu: Incomplete Bug description: Hi, I've upgraded to 16.10 to try out the latest and the greatest. Unfortunately, the Unity8 session does not work anymore. It was working as expected on 16.04 with the overlay PPA. When I select "Unity8" in lightdm and enter my password, the password box disappears, and nothing else happens. I can still access all the indicators, so lightdm is not completely frozen. I then have to reboot or restart lightdm in tty1 to log in Unity 7. I do have a "system problem detected" warning and I did send the report, but I can't find it on Launchpad, that's why I'm filing this bug manually. I'm using Ubuntu 16.10 64bits, with the opensource radeon driver. Further info from the automatic bug report: Title : unity-system-compositor crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler() I'm attaching some logs that might be useful. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1634412/+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 1634412] Re: Unity8 session fails to start due to unity-system-compositor
Here is a copy of my unity-system-compositor.sleep. A failed upgrade is possible: before I upgraded to 16.10, I tried purging a few PPAs because they are often problematic and purging the overlay-ppa proved very difficult (ended up chasing the word "overlay" in Synaptic to completely remove any trace). Currently, my version of unity-system-compositor is 0.7.1+16.10.20160909.1-0ubuntu1 and Synaptic marks it as the latest version. ** Attachment added: "unity-system-compositor.sleep" https://bugs.launchpad.net/unity-system-compositor/+bug/1634412/+attachment/4768090/+files/unity-system-compositor.sleep -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1634412 Title: Unity8 session fails to start due to unity-system-compositor Status in Light Display Manager: Incomplete Status in Unity System Compositor: Incomplete Status in lightdm package in Ubuntu: Incomplete Bug description: Hi, I've upgraded to 16.10 to try out the latest and the greatest. Unfortunately, the Unity8 session does not work anymore. It was working as expected on 16.04 with the overlay PPA. When I select "Unity8" in lightdm and enter my password, the password box disappears, and nothing else happens. I can still access all the indicators, so lightdm is not completely frozen. I then have to reboot or restart lightdm in tty1 to log in Unity 7. I do have a "system problem detected" warning and I did send the report, but I can't find it on Launchpad, that's why I'm filing this bug manually. I'm using Ubuntu 16.10 64bits, with the opensource radeon driver. Further info from the automatic bug report: Title : unity-system-compositor crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler() I'm attaching some logs that might be useful. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1634412/+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 1568604] Re: Mouse cursor lost when unlocking with Intel graphics
I'm with ElementaryOS Freya. Bug is still there Is it because the fix is only available on xenial-updates, and still not present in trusty-updates? The package currently installed on my laptop is xserver-xorg-video- intel-lts-xenial 2:2.99.917+git20160325-1ubuntu1 -- 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/1568604 Title: Mouse cursor lost when unlocking with Intel graphics Status in elementary OS: Fix Released Status in xf86-video-intel: Confirmed Status in xserver-xorg-video-intel package in Ubuntu: Fix Released Status in xserver-xorg-video-intel-lts-xenial package in Ubuntu: Confirmed Status in xserver-xorg-video-intel source package in Xenial: Fix Released Status in xserver-xorg-video-intel package in Debian: Fix Released Bug description: [Relevant details] This bug also affects Trusty and all distributions based on it, like Elementary OS Freya. [Impact] Mouse cursor is no longer visible after VT-switch for systems with Intel graphics. Switching VTs again may cause the cursor to become visible again. - Changing to vt1 then back to vt7 (ctrl+alt+f1 then ctrl+alt+f7) This is often observed in systems that lock the session and return to the greeter (including at least Xubuntu, Ubuntu Mate, and elementary OS). [Test Case] (Requires a lightdm-based screen locking solution) 1. Start a new session. 2. Lock your screen. 2a. You are redirected to the lightdm greeter. 3. Login/Unlock your session. 4. Cursor is no longer visible. [Regression Potential] remains to be seen === [Original Report] Cursor is visible at unlock screen either after returning from suspend or just locking. After unlocking screen cursor is invisible. Changing to vt1 then back to vt7 (ctrl+alt+f1 then ctrl+alt+f7) cursor returns no matter if you suspend or sleep, to swap or disk when you return from it, the mouse cursor is missing.you can still move the mouse and you can see (because it highlights the window) as you move it around. But the cursor is not displayed on the screen. i am using a lenovo W540 laptop. I downloaded the latest beta on april 8 2016. this is xubuntu using the xfce window manager. the cursor does return if i log off and log back in, but that actually defeats the purpose of going to sleep. --- ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2016-04-08 (2 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia Package: light-locker 1.7.0-2ubuntu1 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Tags: xenial Uname: Linux 4.4.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/elementaryos/+bug/1568604/+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 1634412] Re: Unity8 session fails to start due to unity-system-compositor
Is there any more log I can provide that could shed a light on this? This bug is very easily reproducible on my computer, so I should be able to provide relevant logs! My computer is not a fresh install and has been upgraded every step of the way since 14.10. I'll try a LiveUSB of 16.10 to see if the problem persists. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1634412 Title: Unity8 session fails to start due to unity-system-compositor Status in Light Display Manager: New Status in Unity System Compositor: New Status in lightdm package in Ubuntu: New Bug description: Hi, I've upgraded to 16.10 to try out the latest and the greatest. Unfortunately, the Unity8 session does not work anymore. It was working as expected on 16.04 with the overlay PPA. When I select "Unity8" in lightdm and enter my password, the password box disappears, and nothing else happens. I can still access all the indicators, so lightdm is not completely frozen. I then have to reboot or restart lightdm in tty1 to log in Unity 7. I do have a "system problem detected" warning and I did send the report, but I can't find it on Launchpad, that's why I'm filing this bug manually. I'm using Ubuntu 16.10 64bits, with the opensource radeon driver. Further info from the automatic bug report: Title : unity-system-compositor crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler() I'm attaching some logs that might be useful. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1634412/+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 1633775] [NEW] No network when waking up from sleep
Public bug reported: When returning from sleep, everything works except for network. Here is what I see in /var/log/syslog : Oct 15 12:40:16 XPS systemd[1]: Starting Network Manager Script Dispatcher Service... Oct 15 12:40:16 XPS dbus[946]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Oct 15 12:40:16 XPS systemd[1]: Started Network Manager Script Dispatcher Service. Oct 15 12:40:16 XPS nm-dispatcher: req:1 'down' [wlan0]: new request (2 scripts) Oct 15 12:40:16 XPS nm-dispatcher: req:1 'down' [wlan0]: start running ordered scripts... Oct 15 12:40:16 XPS nm-dispatcher[5639]: /etc/network/if-post-down.d/ubuntu-fan: 29: /etc/network/if-post-down.d/ubuntu-fan: /usr/sbin/fanctl: not found Oct 15 12:40:16 XPS nm-dispatcher[5639]: run-parts: /etc/network/if-post-down.d/ubuntu-fan exited with return code 127 Oct 15 12:40:16 XPS nm-dispatcher: req:1 'down' [wlan0], "/etc/NetworkManager/dispatcher.d/01ifupdown": complete: failed with Script '/etc/NetworkManager/dispatcher.d/01ifupdown' exited with error status 1. Oct 15 12:40:16 XPS NetworkManager[954]: [1476528016.5196] device (wlan0): state change: disconnected -> unmanaged (reason 'sleeping') [30 10 37] Oct 15 12:40:16 XPS wpa_supplicant[1147]: nl80211: deinit ifname=wlan0 disabled_11b_rates=0 Oct 15 12:40:16 XPS NetworkManager[954]: [1476528016.6003] dispatcher: (5) 01ifupdown failed (failed): Script '/etc/NetworkManager/dispatcher.d/01ifupdown' exited with error status 1. Perhaps this error : /usr/sbin/fanctl: not found is fatal to resume network ? Have you experienced the same ? Only solution for the moment is to reboot. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: network-manager 1.2.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-25.27-generic 4.8.1 Uname: Linux 4.8.0-25-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Sat Oct 15 23:22:22 2016 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-06-25 (478 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 IpRoute: NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2016-10-13T06:48:12.364564 nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- wlan0 wifi unmanaged /org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.4disconnected started none enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1633775 Title: No network when waking up from sleep Status in network-manager package in Ubuntu: New Bug description: When returning from sleep, everything works except for network. Here is what I see in /var/log/syslog : Oct 15 12:40:16 XPS systemd[1]: Starting Network Manager Script Dispatcher Service... Oct 15 12:40:16 XPS dbus[946]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Oct 15 12:40:16 XPS systemd[1]: Started Network Manager Script Dispatcher Service. Oct 15 12:40:16 XPS nm-dispatcher: req:1 'down' [wlan0]: new request (2 scripts) Oct 15 12:40:16 XPS nm-dispatcher: req:1 'down' [wlan0]: start running ordered scripts... Oct 15 12:40:16 XPS nm-dispatcher[5639]: /etc/network/if-post-down.d/ubuntu-fan: 29: /etc/network/if-post-down.d/ubuntu-fan: /usr/sbin/fanctl: not found Oct 15 12:40:16 XPS nm-dispatcher[5639]: run-parts: /etc/network/if-post-down.d/ubuntu-fan exited with return code 127 Oct 15 12:40:16 XPS nm-dispatcher: req:1 'down' [wlan0], "/etc/NetworkManager/dispatcher.d/01ifupdown": complete: failed with Script '/etc/NetworkManager/dispatcher.d/01ifupdown' exited with error status 1. Oct 15 12:40:16 XPS NetworkManager[954]: [1476528016.5196] device (wlan0): state change: disconnected -> unmanaged (reason 'sleeping') [30 10 37] Oct 15 12:40:16 XPS wpa_supplicant[1147]: nl80211: deinit ifname=wlan0 disabled_11b_rates=0 Oct 15 12:40:16 XPS
[Desktop-packages] [Bug 1577376] Re: Network Manager convert static IPv6 DNS to IPv4 address
I have reported the bug upstream here is the number #766575. https://bugzilla.gnome.org/show_bug.cgi?id=766575 ** Bug watch added: GNOME Bug Tracker #766575 https://bugzilla.gnome.org/show_bug.cgi?id=766575 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1577376 Title: Network Manager convert static IPv6 DNS to IPv4 address Status in network-manager package in Ubuntu: New Bug description: Network Manager seems to convert statically configured IPv6 DNS to IPv4 addresses for some reason. Here at some screenshots (side by side) before applying the setting and after. As you can see in the screenshots the IPv4 address corresponds to the first 32 bits of the IPv6 address which was entered. network-manager/xenial 1.1.93-0ubuntu4 amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1577376/+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 1577376] [NEW] Network Manager convert static IPv6 DNS to IPv4 address
Public bug reported: Network Manager seems to convert statically configured IPv6 DNS to IPv4 addresses for some reason. Here at some screenshots (side by side) before applying the setting and after. As you can see in the screenshots the IPv4 address corresponds to the first 32 bits of the IPv6 address which was entered. network-manager/xenial 1.1.93-0ubuntu4 amd64 ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Attachment added: "nm-ipv6-dns.png" https://bugs.launchpad.net/bugs/1577376/+attachment/4653582/+files/nm-ipv6-dns.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1577376 Title: Network Manager convert static IPv6 DNS to IPv4 address Status in network-manager package in Ubuntu: New Bug description: Network Manager seems to convert statically configured IPv6 DNS to IPv4 addresses for some reason. Here at some screenshots (side by side) before applying the setting and after. As you can see in the screenshots the IPv4 address corresponds to the first 32 bits of the IPv6 address which was entered. network-manager/xenial 1.1.93-0ubuntu4 amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1577376/+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 1318040] Re: bbswitch prevents suspend and taints kernel
Still facing the issue with kernel 4.2.0-23-generic, gcc version 5.2.1 20151010 (Ubuntu 5.2.1-22ubuntu2), bbswitch-dkms 0.7-2ubuntu1, no bumblebee package installed. I attach a full dmesg (from kern.log) from the boot to the freeze. After booting, I logged into tty1 and entered the following commands: sudo service sdsm stop sudo rmmod nouveau sudo modprobe bbswitch load_state=0 sudo service sdsm start Ctrl-Alt-F7 and closed the lid ** Attachment added: "dmesg" https://bugs.launchpad.net/ubuntu/+source/bbswitch/+bug/1318040/+attachment/4551571/+files/extract-kern.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bbswitch in Ubuntu. https://bugs.launchpad.net/bugs/1318040 Title: bbswitch prevents suspend and taints kernel Status in bbswitch package in Ubuntu: New Bug description: When initiating suspend (to RAM), the kernel gets tainted. This is a regression that appeared after upgrading from Kubuntu 13.10 to 14.04. My computer has a discrete nVidia G210M card (hybrid SLI system, on ASUS UL80VT). Here is an extract from dmesg: PM: Preparing system for mem sleep BUG: unable to handle kernel NULL pointer dereference at 00b8 IP: [] pci_bus_read_config_dword+0x4b/0x90 --- ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2010-01-19 (1571 days ago) InstallationMedia: Kubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) Package: bbswitch-dkms 0.7-2ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.13.0-26.48-generic 3.13.11 Tags: trusty Uname: Linux 3.13.0-26-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-05-07 (2 days ago) UserGroups: adm admin audio bumblebee cdrom dialout fuse lpadmin plugdev sambashare src users vboxusers _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bbswitch/+bug/1318040/+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 1383184] Re: Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] is not supported
Sorry, it says "willy should work" but it doesn't for me . lspci --n 03:00.0 Ethernet controller [0200]: Qualcomm Atheros Killer E220x Gigabit Ethernet Controller [1969:e091] (rev 13) 04:00.0 Network controller [0280]: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter [168c:003e] (rev 20) uname -a Linux guigolum-GT72-2QE 4.2.0-22-generic #27-Ubuntu SMP Thu Dec 17 22:57:08 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux I have a netgear X4 R7500 802.1 g/n/ac router with two access points (one ac and one n) network-manager can SEE all the wifi AP (both n and ac) BUT can only connect to the n. When I try to connect to ac, it asks me for password, then after some time request the password again. At this moment I can't connect to any AP unless I enter sudo network-manager restart . Basically I am stuck with 802.11n now.I also bought other WIFI USB dongles with 802.11ac but none were working correctly. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1383184 Title: Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] is not supported Status in HWE Next: Fix Released Status in HWE Next wily series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Fix Released Status in network-manager package in Ubuntu: Invalid Status in linux source package in Wily: Fix Released Status in linux-firmware source package in Wily: Fix Released Status in network-manager source package in Wily: Confirmed Bug description: = CURRENT STATUS: Wily(15.10) could not work with and don't need Adam's dkms package 1.0 or 1.1 Wily(15.10) has already fixed the driver part, and the firmware part is in progress. For now, you guys could use 15.10(purge the ath10k-dkms if you tried installing it), and make a copy of https://git.kernel.org/cgit/linux/kernel/git/firmware/linux- firmware.git/plain/ath10k/QCA6174 into /lib/firmware/ath10k/ 15.10 will work in a week by a simple `apt upgrade` Distros before 15.10(lower than 4.2 kernel) please keep using the dkms(which will be relocated soon) = Card detail: Qualcomm Atheros Device [168c:003e] (rev 20) Subsystem: Bigfoot Networks, Inc. Device [1a56:1525] This is on a fully updated Ubuntu Server 14.04 installation, with the ubuntu-desktop environment installed. This happened in order to get the md raid drivers for raid0 on my system, as the desktop version doesn't support them. --- ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: matanis2333 F pulseaudio /dev/snd/controlC0: matanis2333 F pulseaudio CRDA: Error: [Errno 2] No such file or directory CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=1b192ee3-f592-43e9-bdcf-08b91c0aa9b6 InstallationDate: Installed on 2014-10-16 (3 days ago) InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.3) IwConfig: p2p1 no wireless extensions. lono wireless extensions. MachineType: Micro-Star International Co., Ltd. GT72 2QE NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic.efi.signed root=UUID=80998dbb-1f89-4eda-be90-25e35e1c0a90 ro ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 RelatedPackageVersions: linux-restricted-modules-3.13.0-37-generic N/A linux-backports-modules-3.13.0-37-generic N/A linux-firmware 1.127.7 RfKill: Tags: trusty Uname: Linux 3.13.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E1781IMS.10D dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-1781 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.C 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:bvnAmericanMegatrendsInc.:bvrE1781IMS.10D:bd09/15/2014:svnMicro-StarInternationalCo.,Ltd.:pnGT722QE:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1781:rvrREV0.C:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: GT72 2QE dmi.product.version: REV:0.C dmi.sys.vendor: Micro-Star International Co., Ltd. Qualcomm Atheros Device [168c:003e] (rev 20) mainline commit d63955b33b3bee45d784ffdfafeb93076c765660 [6.221281] ath10k_pci :02:00.0: pci irq msi interrupts 1
[Desktop-packages] [Bug 210468] Re: try to access a .Trash-$USER directory on autofs mounts
Hi, I know this is an old bug and that it's marked as fixed, but I've been having exactly the same problem lately on Wily. Is there something i can do? -- 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/210468 Title: try to access a .Trash-$USER directory on autofs mounts Status in gvfs: Fix Released Status in gvfs package in Ubuntu: Fix Released Status in gvfs source package in Hardy: Fix Released Status in gvfs source package in Intrepid: Fix Released Bug description: Binary package hint: nautilus root@guapuraT61:~# /etc/init.d/autofs start Starting automounter: done. ==> syslog <== Apr 1 14:50:15 guapuraT61 kernel: [18916.265351] SELinux: initialized (dev autofs, type autofs), uses genfs_contexts Apr 1 14:50:16 guapuraT61 automount[10582]: >> /sbin/showmount: can't get address for .Trash Apr 1 14:50:16 guapuraT61 automount[10582]: lookup(program): lookup for .Trash failed Apr 1 14:50:16 guapuraT61 automount[10582]: failed to mount /net/.Trash Apr 1 14:50:16 guapuraT61 automount[10589]: >> /sbin/showmount: can't get address for .Trash-500 Apr 1 14:50:16 guapuraT61 automount[10589]: lookup(program): lookup for .Trash-500 failed Apr 1 14:50:16 guapuraT61 automount[10589]: failed to mount /net/.Trash-500 Apr 1 14:50:16 guapuraT61 automount[10597]: >> /sbin/showmount: can't get address for .Trash Apr 1 14:50:16 guapuraT61 automount[10597]: lookup(program): lookup for .Trash failed Apr 1 14:50:16 guapuraT61 automount[10597]: failed to mount /net/.Trash Apr 1 14:50:16 guapuraT61 automount[10603]: >> /sbin/showmount: can't get address for .Trash-500 Apr 1 14:50:16 guapuraT61 automount[10603]: lookup(program): lookup for .Trash-500 failed Apr 1 14:50:16 guapuraT61 automount[10603]: failed to mount /net/.Trash-500 Nautilus attempts to mount and access a .Trash-$USER directory under the autofs mount "/net" and consequently fails and reports a bunch of errors to /var/log/syslog. There should be an ignore statement somewhere so that nautilus will ignore/not create the .Trash-$USER directory on read-only directories such as nfs shares that have been exported read-only and consequently *not* attempt to use the directory. Additional information: root@guapuraT61:~# lsb_release -rd Description: Ubuntu hardy (development branch) Release: 8.04 root@guapuraT61:~# apt-cache policy nautilus nautilus: Installed: 1:2.22.1-0ubuntu1 Candidate: 1:2.22.1-0ubuntu1 Version table: *** 1:2.22.1-0ubuntu1 0 500 http://us.archive.ubuntu.com hardy/main Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/210468/+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 1520168] [NEW] package gimp-data 2.8.10-0ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuratio
Public bug reported: i don't know ProblemType: Package DistroRelease: Ubuntu 14.04 Package: gimp-data 2.8.10-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-68.111-generic 3.13.11-ckt27 Uname: Linux 3.13.0-68-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 Date: Wed Nov 25 15:24:58 2015 DuplicateSignature: package:gimp-data:2.8.10-0ubuntu1:package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2015-11-09 (17 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageArchitecture: all RelatedPackageVersions: dpkg 1.17.5ubuntu5.4 apt 1.0.1ubuntu2.10 SourcePackage: gimp Title: package gimp-data 2.8.10-0ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.gimp.2.0.controllerrc: [deleted] modified.conffile..etc.gimp.2.0.gimprc: [deleted] modified.conffile..etc.gimp.2.0.gtkrc: [deleted] modified.conffile..etc.gimp.2.0.menurc: [deleted] modified.conffile..etc.gimp.2.0.sessionrc: [deleted] modified.conffile..etc.gimp.2.0.templaterc: [deleted] modified.conffile..etc.gimp.2.0.unitrc: [deleted] ** Affects: gimp (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/1520168 Title: package gimp-data 2.8.10-0ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in gimp package in Ubuntu: New Bug description: i don't know ProblemType: Package DistroRelease: Ubuntu 14.04 Package: gimp-data 2.8.10-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-68.111-generic 3.13.11-ckt27 Uname: Linux 3.13.0-68-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 Date: Wed Nov 25 15:24:58 2015 DuplicateSignature: package:gimp-data:2.8.10-0ubuntu1:package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2015-11-09 (17 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageArchitecture: all RelatedPackageVersions: dpkg 1.17.5ubuntu5.4 apt 1.0.1ubuntu2.10 SourcePackage: gimp Title: package gimp-data 2.8.10-0ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.gimp.2.0.controllerrc: [deleted] modified.conffile..etc.gimp.2.0.gimprc: [deleted] modified.conffile..etc.gimp.2.0.gtkrc: [deleted] modified.conffile..etc.gimp.2.0.menurc: [deleted] modified.conffile..etc.gimp.2.0.sessionrc: [deleted] modified.conffile..etc.gimp.2.0.templaterc: [deleted] modified.conffile..etc.gimp.2.0.unitrc: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1520168/+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 1467609] Re: vibrations on MSI gt72 2qe scren
Just posting here to close it : The bug is no more present. Maybe last versions of kernel did correct it ? ** Changed in: xorg (Ubuntu) Status: Expired => Fix Released -- 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/1467609 Title: vibrations on MSI gt72 2qe scren Status in xorg package in Ubuntu: Fix Released Bug description: With the nvidia proprietary drivers (ex. nvidia 352 from their site) it works good for the external screen I have, but now the integrated screen is vibrating as per the attached screenshot. As you can notice, lines are shifted to left/right on several positions of the screen. It makes the use of the screen very unpleasant. So I usually switch it off. WORKAROUND: Use nouveau. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8 Uname: Linux 3.19.0-21-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 352.21 Tue Jun 9 21:53:31 PDT 2015 GCC version: gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu13) ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Jun 22 18:40:33 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.19.0-15-generic, x86_64: installed bbswitch, 0.7, 3.19.0-21-generic, x86_64: installed nvidia-352, 352.21, 3.19.0-21-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GM204M [GeForce GTX 980M] [10de:13d7] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:1129] InstallationDate: Installed on 2015-06-19 (2 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Micro-Star International Co., Ltd. GT72 2QE ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-21-generic root=UUID=4fabaada-02c5-4230-a634-0b88cf228b5f ro quiet splash SourcePackage: xorg Symptom: display UdevLog: Error: [Errno 2] Aucun fichier ou dossier de ce type: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/21/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E1781IMS.10H dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-1781 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.C dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1781IMS.10H:bd11/21/2014:svnMicro-StarInternationalCo.,Ltd.:pnGT722QE:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1781:rvrREV0.C:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrToBeFilledByO.E.M.: dmi.product.name: GT72 2QE dmi.product.version: REV:0.C dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.61+git20150614.97be70b4-0ubuntu0ricotz~vivid version.libgl1-mesa-dri: libgl1-mesa-dri 10.6.0~git20150616+10.6.5d327b37-0ubuntu0ricotz~vivid version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.6.0~git20150616+10.6.5d327b37-0ubuntu0ricotz~vivid version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.99+git20150521.d64a13eb-0ubuntu0ricotz~vivid version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150528.fb1643f0-0ubuntu0sarvatt~vivid version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11+git20150528.27234dbe-0ubuntu0sarvatt~vivid xserver.bootTime: Mon Jun 22 18:11:59 2015 xserver.configfile: default xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.17.1-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1467609/+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 1498090] Re: [0319A13, Realtek ALC269, Speaker, Internal] Pulseaudio fails to detect card
so I only see "dummy output" -- 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/1498090 Title: [0319A13, Realtek ALC269, Speaker, Internal] Pulseaudio fails to detect card Status in pulseaudio package in Ubuntu: New Bug description: I have lost ALC269 sound between ubuntu 14.04.1 and 14.04.3 and probably switch from kernel 3.13 and (3.16-3.19) Sound (speakers) was working fine since 2011 with Ubuntu. Knoppix 7.4.2 (32bit), the sound is working fine. lsmod/lspci give (almost) the same output (more kernel mod for ubuntu/intel hda) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu11.1 ProcVersionSignature: Ubuntu 3.19.0-29.31~14.04.1-generic 3.19.8-ckt6 Uname: Linux 3.19.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.13 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D3', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/controlC29', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Mon Sep 21 18:31:41 2015 SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel MID Symptom_Jack: Speaker, Internal Title: [0319A13, Realtek ALC269, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 80ET65WW (2.05 ) dmi.board.name: 0319A13 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr80ET65WW(2.05):bd03/25/2013:svnLENOVO:pn0319A13:pvrThinkPadEdge:rvnLENOVO:rn0319A13:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 0319A13 dmi.product.version: ThinkPad Edge dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1498090/+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