[Desktop-packages] [Bug 1809407] Re: [nvidia] Corrupted wallpaper after resuming from suspend or hibernation
Also workaround is to restart gnome, Alt+F2, "r" and it seems to refresh the wallpaper. -- 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/1809407 Title: [nvidia] Corrupted wallpaper after resuming from suspend or hibernation Status in GNOME Shell: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Disco: Won't Fix Status in mutter source package in Eoan: Fix Released Bug description: [Impact] The Nvidia (Xorg) driver corrupts the desktop wallpaper (by design (1)) upon resuming from suspend. This creates a poor user experience and gives the impression of severe memory corruption. (1) https://www.khronos.org/registry/OpenGL/extensions/NV/NV_robustness_video_memory_purge.txt [Test Case] 0. Set up an Nvidia-only system using the proprietary Nvidia Xorg driver. 1. Suspend and resume the machine. Expect: The wallpaper still looks like it did before suspending. [Regression Potential] Low. The exact same patch is in Gnome 3.34 (Ubuntu 19.10) already and has been used for a couple of months without issue. [Original Report] https://trello.com/c/i5hENxSO Every other wake from sleep presents a corrupted screen with no unlock app. There's a dock and system menu on a black background with pixel garbage. Some personal information in the dock's large window thumbnails. Bitmap garbage flashes on the screen when interacting with anything. Only workaround is doing another sleep-wake cycle. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Uname: Linux 4.18.0-12-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..4b.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:4b:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.87 Tue Aug 21 12:33:05 PDT 2018 GCC version: gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1) ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Dec 20 22:19:29 2018 DistUpgraded: 2018-12-01 23:07:50,385 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: nvidia, 390.87, 4.18.0-11-generic, x86_64: installed nvidia, 390.87, 4.18.0-12-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-11-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-12-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GP106 [GeForce GTX 1060 3GB] [3842:6162] InstallationDate: Installed on 2018-10-28 (54 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Gigabyte Technology Co., Ltd. Default string ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-12-generic root=UUID=a8c839e7-c579-4699-999a-748f804ff9e0 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to cosmic on 2018-12-02 (18 days ago) dmi.bios.date: 06/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F24 dmi.board.asset.tag: Default string dmi.board.name: X99P-SLI-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.:bvrF24:bd06/08/2017:svnGigabyteTechnologyCo.,Ltd.:pnDefaultstring:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX99P-SLI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Default string dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
[Desktop-packages] [Bug 1809407] Re: [nvidia] Corrupted wallpaper after resuming from suspend or hibernation
Nvidia Version 340.107 No LSB modules are available. Distributor ID: Ubuntu Description:Pop!_OS 19.10 Release:19.10 Codename: eoan mutter 3.34.1+git20191107-1ubuntu1~19.10.1pop0~1573683812~19.10~50e928a Linux ## 5.3.0-22-generic #24+system76~1573659475~19.10~26b2022-Ubuntu SMP Wed Nov 13 20:0 x86_64 x86_64 x86_64 GNU/Linux ** Attachment added: "Screenshot from 2019-12-02 09-20-59.png" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1809407/+attachment/5309271/+files/Screenshot%20from%202019-12-02%2009-20-59.png -- 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/1809407 Title: [nvidia] Corrupted wallpaper after resuming from suspend or hibernation Status in GNOME Shell: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Disco: Won't Fix Status in mutter source package in Eoan: Fix Released Bug description: [Impact] The Nvidia (Xorg) driver corrupts the desktop wallpaper (by design (1)) upon resuming from suspend. This creates a poor user experience and gives the impression of severe memory corruption. (1) https://www.khronos.org/registry/OpenGL/extensions/NV/NV_robustness_video_memory_purge.txt [Test Case] 0. Set up an Nvidia-only system using the proprietary Nvidia Xorg driver. 1. Suspend and resume the machine. Expect: The wallpaper still looks like it did before suspending. [Regression Potential] Low. The exact same patch is in Gnome 3.34 (Ubuntu 19.10) already and has been used for a couple of months without issue. [Original Report] https://trello.com/c/i5hENxSO Every other wake from sleep presents a corrupted screen with no unlock app. There's a dock and system menu on a black background with pixel garbage. Some personal information in the dock's large window thumbnails. Bitmap garbage flashes on the screen when interacting with anything. Only workaround is doing another sleep-wake cycle. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Uname: Linux 4.18.0-12-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..4b.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:4b:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.87 Tue Aug 21 12:33:05 PDT 2018 GCC version: gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1) ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Dec 20 22:19:29 2018 DistUpgraded: 2018-12-01 23:07:50,385 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: nvidia, 390.87, 4.18.0-11-generic, x86_64: installed nvidia, 390.87, 4.18.0-12-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-11-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-12-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GP106 [GeForce GTX 1060 3GB] [3842:6162] InstallationDate: Installed on 2018-10-28 (54 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Gigabyte Technology Co., Ltd. Default string ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-12-generic root=UUID=a8c839e7-c579-4699-999a-748f804ff9e0 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to cosmic on 2018-12-02 (18 days ago) dmi.bios.date: 06/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F24 dmi.board.asset.tag: Default string dmi.board.name: X99P-SLI-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.:bvrF24:bd06/08/2017:svnGigabyteTechnologyCo.,Ltd.:pnDefaultstring:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX99P-SLI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Default string dmi.product.sku: Default string
[Desktop-packages] [Bug 550856] Re: page size setting is broken, use it as default crop or fix it by other means
Sorry I should add this problem is still apparent only when scanning Front and Back of a page. Doest not exist when I scan Front's only or Back's only. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/550856 Title: page size setting is broken, use it as default crop or fix it by other means Status in Simple Scan: Fix Released Status in Simple Scan 3.10 series: Fix Released Status in Simple Scan 3.11 series: Fix Released Status in “simple-scan” package in Ubuntu: Fix Released Status in “simple-scan” source package in Saucy: Fix Released Status in “simple-scan” source package in Trusty: Fix Released Bug description: For some SANE drivers simple scan always scans the largest scan area ignoring the Page Size setting in the preferences. To reproduce: 1. Open Simple Scan 2. Set page size in Document Prefrences Page Size, e.g. to 4x6 3. Scan a document Expected result: The document is scanned at the requested size Observed result: The document is scanned at the maximum size Regression potential: Low. The fix was to set the page size using an alternative method for drivers that do not support the page-width, page-height options. There is a small chance that these settings might change behaviour / expose bugs on drivers that were previously working. To manage notifications about this bug go to: https://bugs.launchpad.net/simple-scan/+bug/550856/+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 550856] Re: page size setting is broken, use it as default crop or fix it by other means
This is still broken on my HP Scanjet 5590. The Pages start bleeding on the next page, and it by the time it gets page number 10 or so the offset is almost half a page. I have to set my page height to 28.3 cm (Letter) in XSane and it works perfectly. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/550856 Title: page size setting is broken, use it as default crop or fix it by other means Status in Simple Scan: Fix Released Status in Simple Scan 3.10 series: Fix Released Status in Simple Scan 3.11 series: Fix Released Status in “simple-scan” package in Ubuntu: Fix Released Status in “simple-scan” source package in Saucy: Fix Released Status in “simple-scan” source package in Trusty: Fix Released Bug description: For some SANE drivers simple scan always scans the largest scan area ignoring the Page Size setting in the preferences. To reproduce: 1. Open Simple Scan 2. Set page size in Document Prefrences Page Size, e.g. to 4x6 3. Scan a document Expected result: The document is scanned at the requested size Observed result: The document is scanned at the maximum size Regression potential: Low. The fix was to set the page size using an alternative method for drivers that do not support the page-width, page-height options. There is a small chance that these settings might change behaviour / expose bugs on drivers that were previously working. To manage notifications about this bug go to: https://bugs.launchpad.net/simple-scan/+bug/550856/+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 550856] Re: page size setting is broken, use it as default crop or fix it by other means
This was performed on 3.11.1.1 on Ubuntu 13.10. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/550856 Title: page size setting is broken, use it as default crop or fix it by other means Status in Simple Scan: Fix Released Status in Simple Scan 3.10 series: Fix Released Status in Simple Scan 3.11 series: Fix Released Status in “simple-scan” package in Ubuntu: Fix Released Status in “simple-scan” source package in Saucy: Fix Released Status in “simple-scan” source package in Trusty: Fix Released Bug description: For some SANE drivers simple scan always scans the largest scan area ignoring the Page Size setting in the preferences. To reproduce: 1. Open Simple Scan 2. Set page size in Document Prefrences Page Size, e.g. to 4x6 3. Scan a document Expected result: The document is scanned at the requested size Observed result: The document is scanned at the maximum size Regression potential: Low. The fix was to set the page size using an alternative method for drivers that do not support the page-width, page-height options. There is a small chance that these settings might change behaviour / expose bugs on drivers that were previously working. To manage notifications about this bug go to: https://bugs.launchpad.net/simple-scan/+bug/550856/+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 550856] Re: page size setting is broken, use it as default crop or fix it by other means
Attached is a sample of the page bleed on a duplex (front/back scan) . Again the same duplex scan works on XSane with page length set to 28.3. Maybe add the ability to provide a custom page length instead of hard coding it Letter size would be nice. I know it goes against the simple scan principles but that could be a quick fix. ** Attachment added: PageBleed.pdf https://bugs.launchpad.net/simple-scan/+bug/550856/+attachment/3960924/+files/PageBleed.pdf -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/550856 Title: page size setting is broken, use it as default crop or fix it by other means Status in Simple Scan: Fix Released Status in Simple Scan 3.10 series: Fix Released Status in Simple Scan 3.11 series: Fix Released Status in “simple-scan” package in Ubuntu: Fix Released Status in “simple-scan” source package in Saucy: Fix Released Status in “simple-scan” source package in Trusty: Fix Released Bug description: For some SANE drivers simple scan always scans the largest scan area ignoring the Page Size setting in the preferences. To reproduce: 1. Open Simple Scan 2. Set page size in Document Prefrences Page Size, e.g. to 4x6 3. Scan a document Expected result: The document is scanned at the requested size Observed result: The document is scanned at the maximum size Regression potential: Low. The fix was to set the page size using an alternative method for drivers that do not support the page-width, page-height options. There is a small chance that these settings might change behaviour / expose bugs on drivers that were previously working. To manage notifications about this bug go to: https://bugs.launchpad.net/simple-scan/+bug/550856/+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 550856] Re: page size setting is broken, use it as default crop or fix it by other means
Sorry for the many comments, but this occurs during a duplex scan on ADF. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/550856 Title: page size setting is broken, use it as default crop or fix it by other means Status in Simple Scan: Fix Released Status in Simple Scan 3.10 series: Fix Released Status in Simple Scan 3.11 series: Fix Released Status in “simple-scan” package in Ubuntu: Fix Released Status in “simple-scan” source package in Saucy: Fix Released Status in “simple-scan” source package in Trusty: Fix Released Bug description: For some SANE drivers simple scan always scans the largest scan area ignoring the Page Size setting in the preferences. To reproduce: 1. Open Simple Scan 2. Set page size in Document Prefrences Page Size, e.g. to 4x6 3. Scan a document Expected result: The document is scanned at the requested size Observed result: The document is scanned at the maximum size Regression potential: Low. The fix was to set the page size using an alternative method for drivers that do not support the page-width, page-height options. There is a small chance that these settings might change behaviour / expose bugs on drivers that were previously working. To manage notifications about this bug go to: https://bugs.launchpad.net/simple-scan/+bug/550856/+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
