[Desktop-packages] [Bug 1809407] Re: [nvidia] Corrupted wallpaper after resuming from suspend or hibernation

2020-07-27 Thread mistr
This bug is still present in a fresh install of Ubuntu 20.04.1 LTS on a
Lenovo T510.

Nvidia driver is 340.108

The work-around mentioned in #73 is working.

-- 
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
  

[Desktop-packages] [Bug 1756201] Re: xsane not aquiring images from Lide 30

2018-03-17 Thread mistr
see 2nd entry

** Package changed: xsane (Ubuntu) => sane-backends (Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to sane-backends in Ubuntu.
https://bugs.launchpad.net/bugs/1756201

Title:
  xsane not aquiring images from Lide 30

Status in sane-backends package in Ubuntu:
  New

Bug description:
  Ubuntu 17.10, xsane 0.999

  
  During the "searching for devices" phase I can hear the "usual" tick from the 
scanner.

  When I try to scan the error "Failed to start scanner: Error during
  device I/O" occurs.

  I can dual-boot my machine into Ubuntu 14.04 LTS with xsane 0.998.
  There it works perfectly (same computer, same port, same cable).

  I don't see any messages on the console or in /var/log/messages.

  I've tried running it as root - same problem.

  Any hints?

  Thanks

  Mike

  
  $ uname -a
  Linux quadro 4.13.0-37-generic #42-Ubuntu SMP Wed Mar 7 14:13:23 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  
  $ lsusb
  ...
  Bus 001 Device 003: ID 04a9:220e Canon, Inc. CanoScan N1240U/LiDE 30

  $ sane-find-scanner 
  ...
  found USB scanner (vendor=0x04a9 [Canon], product=0x220e [CanoScan], 
chip=LM9830) at libusb:001:003

  $ scanimage -L
  device `plustek:libusb:001:003' is a Canon CanoScan N1240U/LiDE30 flatbed 
scanner

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1756201/+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 1756201] Re: xsane not aquiring images from Lide 30

2018-03-17 Thread mistr
I got xsane running by copying the content of /usr/lib/x86_64-linux-
gnu/sane from the old Ubuntu 14.04 (64 bit) installation to the same
location in my Ubuntu 17.10 (64 bit) install.

According to

  sane-config --version

the "old" libraries are from the release 1.0.23. (And the naming of the
files also suggests that.)

I then tried to compile sane from source according to
https://help.ubuntu.com/community/CompileSaneFromSource in the hope to
bisect the commit where this change happend:

sudo apt-get install libusb-dev build-essential libsane-dev
sudo apt-get install libavahi-client-dev libavahi-glib-dev

git clone git://git.debian.org/sane/sane-backends.git

./configure --prefix=/usr --libdir=/usr/lib/x86_64-linux-gnu --sysconfdir=/etc 
--localstatedir=/var  --enable-avahi
make
sudo make install

After each install I rebooted the machine in order to flush any cached
libraries from memory.

This first attempt did not work. (Same error as described above).

I then tried the various newer releases and one older one (1.0.22):

git checkout RELEASE_1_0_xx

configure, make, make install, reboot, test.

However, all of those fail.

The only version that works every time is the one I've copied from
Ubuntu 14.04.

At this point I don't know how to proceed.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to sane-backends in Ubuntu.
https://bugs.launchpad.net/bugs/1756201

Title:
  xsane not aquiring images from Lide 30

Status in sane-backends package in Ubuntu:
  New

Bug description:
  Ubuntu 17.10, xsane 0.999

  
  During the "searching for devices" phase I can hear the "usual" tick from the 
scanner.

  When I try to scan the error "Failed to start scanner: Error during
  device I/O" occurs.

  I can dual-boot my machine into Ubuntu 14.04 LTS with xsane 0.998.
  There it works perfectly (same computer, same port, same cable).

  I don't see any messages on the console or in /var/log/messages.

  I've tried running it as root - same problem.

  Any hints?

  Thanks

  Mike

  
  $ uname -a
  Linux quadro 4.13.0-37-generic #42-Ubuntu SMP Wed Mar 7 14:13:23 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  
  $ lsusb
  ...
  Bus 001 Device 003: ID 04a9:220e Canon, Inc. CanoScan N1240U/LiDE 30

  $ sane-find-scanner 
  ...
  found USB scanner (vendor=0x04a9 [Canon], product=0x220e [CanoScan], 
chip=LM9830) at libusb:001:003

  $ scanimage -L
  device `plustek:libusb:001:003' is a Canon CanoScan N1240U/LiDE30 flatbed 
scanner

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1756201/+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