[Ubuntu-x-swat] [Bug 2006370] Re: Terribly flicking and blicking HDMI-port display

2023-02-06 Thread Daniel van Vugt
Thanks for the bug report.

It looks like this is probably a bug in the nouveau graphics driver, and
most likely the HDMI port is connected to your Nvidia GPU. The nouveau
driver is also logging errors which may or may not be related to this
bug.

Please open the 'Additional Drivers' app and use it to install an
official Nvidia driver instead.


** Tags added: amdgpu dualgpu hybrid nouveau

** Package changed: xorg (Ubuntu) => linux (Ubuntu)

** Summary changed:

- Terribly flicking and blicking HDMI-port display
+ [nouveau] Terribly flicking and blicking HDMI-port display

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2006370

Title:
  [nouveau] Terribly flicking and blicking HDMI-port display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2006370/+subscriptions


___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 2006408] Re: nvidia-uvm module does not exist, making CUDA unusable with the 390 driver

2023-02-06 Thread Aaron Rainbolt
** Description changed:

  Notice: I have not reproduced this bug myself, nor do I have the needed
  setup to reproduce this bug. This is a bug report based on info provided
  to me over IRC.
  
- In order for CUDA compute to work, a kernel module "nvidia-uvm" is
- necessary. This module *should* exist in the headless NVIDIA 390 driver.
- However, it apparently does not exist - it does not show up in the
- output of "lsmod", attempting to modprobe it fails, doing a recursive
- grep on /lib/modules/$(uname -r) does not reveal it, and it appears that
- the Installable Client Driver is not loading correctly.
+ In order for CUDA or OpenCL compute to work, a kernel module "nvidia-
+ uvm" is necessary. This module *should* exist in the headless NVIDIA 390
+ driver. However, it apparently does not exist - it does not show up in
+ the output of "lsmod", attempting to modprobe it fails, doing a
+ recursive grep on /lib/modules/$(uname -r) does not reveal it, and it
+ appears that the Installable Client Driver is not loading correctly.
  
  From my own personal experience, I know that nvidia-uvm *does* exist in
  recommended driver for an NVIDIA 1050 Ti card, however the 390 driver
  used with the GTX 570 card does not appear to have the driver, even
  though the card supports CUDA.

** Summary changed:

- nvidia-uvm module does not exist, making CUDA unusable with the 390 driver
+ nvidia-uvm module does not exist, making CUDA and OpenCL unusable with the 
390 driver

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bugs/2006408

Title:
  nvidia-uvm module does not exist, making CUDA and OpenCL unusable with
  the 390 driver

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2006408/+subscriptions


___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 2006408] Re: nvidia-uvm module does not exist, making CUDA unusable with the 390 driver

2023-02-06 Thread Aaron Rainbolt
strace of "clinfo -l" from the machine of the affected user.

** Attachment added: "clinfo_strace.log"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2006408/+attachment/5645158/+files/clinfo_strace.log

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bugs/2006408

Title:
  nvidia-uvm module does not exist, making CUDA unusable with the 390
  driver

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2006408/+subscriptions


___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 2006408] [NEW] nvidia-uvm module does not exist, making CUDA unusable with the 390 driver

2023-02-06 Thread Aaron Rainbolt
Public bug reported:

Notice: I have not reproduced this bug myself, nor do I have the needed
setup to reproduce this bug. This is a bug report based on info provided
to me over IRC.

In order for CUDA compute to work, a kernel module "nvidia-uvm" is
necessary. This module *should* exist in the headless NVIDIA 390 driver.
However, it apparently does not exist - it does not show up in the
output of "lsmod", attempting to modprobe it fails, doing a recursive
grep on /lib/modules/$(uname -r) does not reveal it, and it appears that
the Installable Client Driver is not loading correctly.

>From my own personal experience, I know that nvidia-uvm *does* exist in
recommended driver for an NVIDIA 1050 Ti card, however the 390 driver
used with the GTX 570 card does not appear to have the driver, even
though the card supports CUDA.

** Affects: nvidia-graphics-drivers-390 (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bugs/2006408

Title:
  nvidia-uvm module does not exist, making CUDA unusable with the 390
  driver

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2006408/+subscriptions


___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 2006370] Re: Terribly flicking and blicking HDMI-port display

2023-02-06 Thread Alex
PPS: I have Ubuntu 22.04 (the same version) on my Acer Aspire 3 A315-21G-63YM 
[very old notebook of about 5-6 years old]; I tried several times to connect 
this notebook to the same monitor with the same scheme - it works perfectly (I 
did not try screenshots, because the picture there is perfect). But I still am 
a rare user of Ubuntu, because I need powerful computers (like this HP Gaming 
Pavilion) for my operations, and I can't do them on just one monitor in quite 
OK computers, and I can't do this on two monitors with a relatively slow 
computer like Acer Aspire 3.  
It means, it is some driver issue [that Ubuntu has problems with the inbuilt 
drivers, but not 100% sure in this].

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2006370

Title:
  Terribly flicking and blicking HDMI-port display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2006370/+subscriptions


___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 2006370] [NEW] Terribly flicking and blicking HDMI-port display

2023-02-06 Thread Alex
Public bug reported:

Hi,
I have HP15 Gaming Pavilion bought 2-3 years ago. 
I had Windows 10 before (not it is the second OS due to this bug [I can't use 
Ubuntu with this bug]), and Win 10 has no problems. 
No solution [that I found over the internet] worked. 
I have to have at least two displays. 
My connection technology:
PC HDMI output -> HDMI-VGA(+audio) transmitter -> LED 20' Display (external 
monitor)
Win 10 have never had any problems with it (it has good drivers). 
When I add any input to the second screen - it blinks and flickers so terrible 
that I can see nothing - a white screen problem. If I do nothing - it will turn 
to some picture in some time, but if I make any action at the second monitor - 
flickering and the white screen problem appears again. 
I think these are drivers. I tested the equipment in Win 10 after I found this 
bug - and it works perfectly (so, the hardware is good). 
It is a typical notebook and this bug is crucial. I use two monitors to type 
codes and work on PC. I can't survive with just one monitor. 
Right now when I am typing you this message the second monitor became white 
again for quite a long time (I did nothing there). 
I hope you will be able to fix this bug :)
Best wishes,
Alex,
Prague, Czech Republic, EU


PS: When typing this message I found another bug compared to MS Windows. 
When making screenshots (Alt/Shift + Print Screen) - it makes perfect picture 
even when you actually have the second monitor white all the time (so the 
screenshot is not how it is).
I made an actual photo (and deleted some parts of the background not related to 
the monitors/computer). You can see a white screen, but the screenshot shows a 
"perfect world" with a perfect picture which is not how it is on the screen. 
Windows, on the contrary, makes actual screenshots. And Win 10 test of this 
monitor never have this white screen or any other monitor problems. 
Moreover, when the monitors stops to be white for a second it depicts different 
picture (more terrible image; it is disproportional, with font heavily 
readable, but the screenshot functions shows an "ideal world" a user can never 
see :)

I made this detailed description to help Ubuntu. I think the project is
great in concept, but poor in realization. Such bugs make it impossible
for users to use Ubuntu (who can work on just one monitor? Who do not
wish to make screenshots with what he/she actually sees on the monitor
[rather than modified images with the pictures users do not actually
see]?).

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74
Uname: Linux 5.15.0-58-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Feb  6 19:45:32 2023
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation TU117M [10de:1f99] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company TU117M [103c:87b1]
 Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c6) (prog-if 00 
[VGA controller])
   Subsystem: Hewlett-Packard Company Renoir [103c:87b1]
InstallationDate: Installed on 2023-02-04 (2 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
MachineType: HP HP Pavilion Gaming Laptop 15-ec1xxx
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic 
root=UUID=30f188c5-d67f-4f68-ba6d-6995864ff95e ro quiet splash loglevel=3 
vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/18/2021
dmi.bios.release: 15.25
dmi.bios.vendor: AMI
dmi.bios.version: F.25
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 87B1
dmi.board.vendor: HP
dmi.board.version: 31.23
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 31.23
dmi.modalias: 
dmi:bvnAMI:bvrF.25:bd08/18/2021:br15.25:efr31.23:svnHP:pnHPPavilionGamingLaptop15-ec1xxx:pvr:rvnHP:rn87B1:rvr31.23:cvnHP:ct10:cvrChassisVersion:sku1N3L2EA#ACB:
dmi.product.family: 103C_5335KV HP Pavilion
dmi.product.name: HP Pavilion Gaming Laptop 15-ec1xxx
dmi.product.sku: 1N3L2EA#ACB
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.6
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

** Affects: xorg (Ubuntu)
 

[Ubuntu-x-swat] [Bug 2004649] Re: Regression bug with mesa backport and ogre rendering

2023-02-06 Thread Brian Murray
** Changed in: mesa (Ubuntu)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2004649

Title:
  Regression bug with mesa backport and ogre rendering

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2004649/+subscriptions


___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 2003339] Re: kwin_x11: The X11 connection broke: I/O error (code 1)

2023-02-06 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: mesa (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2003339

Title:
  kwin_x11: The X11 connection broke: I/O error (code 1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/kdebase-workspace/+bug/2003339/+subscriptions


___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 2003339] Re: kwin_x11: The X11 connection broke: I/O error (code 1)

2023-02-06 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: kwin (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2003339

Title:
  kwin_x11: The X11 connection broke: I/O error (code 1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/kdebase-workspace/+bug/2003339/+subscriptions


___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1969130] Re: [Feature requrest] nvidia offloading doesn't work on Wayland

2023-02-06 Thread Daniel van Vugt
That would be a feature request for nautilus.

More generally I think whatever launches it just needs to set
environment:

  __NV_PRIME_RENDER_OFFLOAD=1

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xwayland in Ubuntu.
https://bugs.launchpad.net/bugs/1969130

Title:
  [Feature requrest] nvidia offloading doesn't work on Wayland

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1969130/+subscriptions


___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1969130] Re: [Feature requrest] nvidia offloading doesn't work on Wayland

2023-02-06 Thread Islam
How would you use 'Launch using Discrete Graphics Card' if you are
trying to run an app from nautilus? it doesn't show that option.

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xwayland in Ubuntu.
https://bugs.launchpad.net/bugs/1969130

Title:
  [Feature requrest] nvidia offloading doesn't work on Wayland

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1969130/+subscriptions


___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 2006070] Re: incredibly high memory usage

2023-02-06 Thread Daniel van Vugt
The attached information looks like memory mapped files. So that's
virtual address space, not real memory.

Please run:

  ps auxw > psall.txt

and attach the resulting text file here.

** Project changed: xorg-server => gnome-software

** Package changed: xorg (Ubuntu) => gnome-software (Ubuntu)

** Changed in: gnome-software (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2006070

Title:
  incredibly high memory usage

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-software/+bug/2006070/+subscriptions


___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 2006043] Re: Volume keys repeat with K400+ keyboard when used through a KVM switch

2023-02-06 Thread Daniel van Vugt
** Summary changed:

- Volume keys repeat with K400+ keyboard
+ Volume keys repeat with K400+ keyboard when used through a KVM switch

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libinput in Ubuntu.
https://bugs.launchpad.net/bugs/2006043

Title:
  Volume keys repeat with K400+ keyboard when used through a KVM switch

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/2006043/+subscriptions


___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 2006038] Re: can't restart when screen sleeps and power adapter plugged in

2023-02-06 Thread Daniel van Vugt
Thanks for the bug report.

Next time the problem happens, please:

1. Wait 10 seconds.

2. Reboot.

3. Run:

   journalctl -b-1 > prevboot.txt

4. Attach the resulting text file here.


** Summary changed:

- can't restart when screen sleeps and power adapter plugged in
+ [Asus ZenBook UX325EA] can't restart when screen sleeps and power adapter 
plugged in

** Package changed: xorg (Ubuntu) => ubuntu

** Changed in: ubuntu
   Status: New => Incomplete

** Tags added: resume suspend-resume

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2006038

Title:
  [Asus ZenBook UX325EA] can't restart when screen sleeps and power
  adapter plugged in

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2006038/+subscriptions


___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 2006042] Re: Laptop often freezes after waking up from suspend to ram

2023-02-06 Thread Daniel van Vugt
Thanks for the bug report.

Next time the problem happens, please:

1. Wait 10 seconds.

2. Reboot.

3. Run:

   journalctl -b-1 > prevboot.txt

4. Attach the resulting text file here.


** Summary changed:

- Laptop often freezes after waking up from suspend to ram
+ [Asus ZenBook UX430UAR] Laptop often freezes after waking up from suspend to 
ram

** Package changed: xorg (Ubuntu) => ubuntu

** Changed in: ubuntu
   Status: New => Incomplete

** Tags added: resume suspend-resume

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2006042

Title:
  [Asus ZenBook UX430UAR] Laptop often freezes after waking up from
  suspend to ram

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2006042/+subscriptions


___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 2005128] Re: mouse issues

2023-02-06 Thread Daniel van Vugt
Thanks for the bug report. I can see it happening in:

[   870.506] (II) modeset(0): Modeline "1366x768"x0.0   76.30  1366 1404 1426 
1592  768 771 777 798 -hsync -vsync (47.9 kHz eP)
[  1932.032] (II) config/udev: removing device PixArt USB Optical Mouse
[  1932.033] (**) Option "fd" "29"
[  1932.033] (II) event5  - PixArt USB Optical Mouse: device removed
[  1932.036] (II) UnloadModule: "libinput"
[  1932.036] (II) systemd-logind: releasing fd for 13:69
[  3180.712] (II) modeset(0): EDID vendor "AUO", prod id 11836

The problem is probably a hardware failure so you should try a different
mouse. But if it is a software bug then it should be assigned to the
kernel.

** Package changed: xorg (Ubuntu) => linux-hwe-5.4 (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2005128

Title:
  mouse issues

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.4/+bug/2005128/+subscriptions


___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp