*** This bug is a duplicate of bug 1869750 ***
https://bugs.launchpad.net/bugs/1869750
** This bug is no longer a duplicate of bug 1870758
[nvidia] Display scaling results in a blank screen (power save state)
** This bug has been marked a duplicate of bug 1869750
[nvidia] Screens turn of
*** This bug is a duplicate of bug 1869750 ***
https://bugs.launchpad.net/bugs/1869750
** This bug is no longer a duplicate of bug 1870758
[nvidia] Display scaling results in a blank screen (power save state)
** This bug has been marked a duplicate of bug 1869750
[nvidia] Screens turn of
It looks like a bug in an old driver, possibly relating only to old
video cards. So a fix is unlikely to arrive in that particular driver
version.
You might want to try uninstalling the Nvidia driver version 390 and
then either:
* Do nothing -- the built-in open source driver should work; or
Thank you have locating the error for me.
What should I do?
Ken
On Wed, Apr 8, 2020 at 6:01 AM Daniel van Vugt <
daniel.van.v...@canonical.com> wrote:
> Thanks. The problem indeed looks like it's confined to the Nvidia
> driver:
>
> Apr 07 13:05:05 Kens-computer /usr/lib/gdm3/gdm-x-session[3091
The attached Xorg log files seem to show that it knows about both GPUs
and it claims to be using both...
1. Are you able to work around the problem by logging into "Ubuntu on
Wayland" instead?
2. Does the same problem also occur in Ubuntu 20.04 (to be released
soon)? http://cdimage.ubuntu.com/dai
*** This bug is a duplicate of bug 1870758 ***
https://bugs.launchpad.net/bugs/1870758
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xorg-server (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 1870758 ***
https://bugs.launchpad.net/bugs/1870758
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nvidia-graphics-drivers-440 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you
*** This bug is a duplicate of bug 1870758 ***
https://bugs.launchpad.net/bugs/1870758
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1870758, so it is being marked as such. Please look
*** This bug is a duplicate of bug 1870758 ***
https://bugs.launchpad.net/bugs/1870758
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1870758, so it is being marked as such. Please look
Please try logging into "Ubuntu on Wayland" from the login screen and
tell us if that avoids the problem.
** Tags added: amdgpu
** Package changed: xorg (Ubuntu) => mutter (Ubuntu)
** Summary changed:
- Black screen after screen lock
+ [amdgpu] Black screen after screen lock
--
You received t
Thank you for reporting this bug to Ubuntu.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
** Tags added: focal
--
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/1733083
Title:
trackpoint slow and hard to move
To manage notifications about this bug go to:
https://bugs.launchpad.net/
*** This bug is a duplicate of bug 1733083 ***
https://bugs.launchpad.net/bugs/1733083
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1733083, so it is being marked as such. Please look
Thanks. The problem indeed looks like it's confined to the Nvidia
driver:
Apr 07 13:05:05 Kens-computer /usr/lib/gdm3/gdm-x-session[3091]: (EE)
NVIDIA(0): Failed to allocate software rendering cache surface: out of
Apr 07 13:05:05 Kens-computer /usr/lib/gdm3/gdm-x-session[3091]: (EE)
NVIDIA(0):
** Summary changed:
- wifi won't connect
+ wifi won't connect, but kernel 5.6 fixes it
** Package changed: xorg (Ubuntu) => linux (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/1871403
I forgot to mention; if the Nvidia driver is in a mode that will support
Wayland we still hide the Wayland option. To unhide it you need to
comment out the last line of:
/usr/lib/udev/rules.d/61-gdm.rules
Although that will reintroduce bug 1705369 so you might need to also use
one of the other
I forgot to mention; if the Nvidia driver is in a mode that will support
Wayland we still hide the Wayland option. To unhide it you need to
uncomment the last line of:
/usr/lib/udev/rules.d/61-gdm.rules
Although that will reintroduce bug 1705369 so you might need to also use
one of the other wo
*** This bug is a duplicate of bug 1870637 ***
https://bugs.launchpad.net/bugs/1870637
Thanks for the bug report. This does indeed look like a duplicate of bug
1870637:
[10.855] (--) modeset(0): HDMI max TMDS frequency 30KHz
[10.855] (II) modeset(0): Not using default mode "3840x2
** Package changed: ubuntu => xorg (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/1871403
Title:
wifi won't connect
To manage notifications about this bug go to:
https://bugs.launchpad
** Package changed: ubuntu => xorg (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/1871422
Title:
Unable to get 4K 60Hz on nvidia GT 1030 on AMD Ryzen 5 2600
To manage notifications abo
** Package changed: gnome-control-center (Ubuntu) => libinput (Ubuntu)
--
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/1871470
Title:
Synaptics Trackpoint on Thinkpad T495 not precisely as in
** Package changed: ubuntu => xorg (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/1871475
Title:
Black screen after screen lock
To manage notifications about this bug go to:
https://bu
You have been subscribed to a public bug:
My wifi adapter won't connect under Kubuntu. It works fine when I boot
the same laptop under Ubuntu 18.04, but when I boot under Kubuntu 20.04,
I get "Configuring Interface" followed by "Wireless interface (wlp1s0)
The wifi network could not be found."
I
You have been subscribed to a public bug:
This is a duplicate of https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/1870637
The only difference is that i switched from a Ryzen 2200G CPU to a Ryzen 5 2600.
Still running a zotac nvidia GT1030 graphics card.
I was not sure how to get the sy
You have been subscribed to a public bug:
When I lock the screen with "Windows" + "L" key combination the screen
gets locked, but I expect it to stay on and be locked. In Ubuntu 20.04.
when I do it the screen gets locked but get immediately black a sit
would be in standby. The screen should stay o
You have been subscribed to a public bug:
I have a Thinkpad T495 and run on it Windows 10 and Ubuntu 20.04. When I
use the trackpoint in Windows it is working very smooth. It responses to
the finger touch in a "lighter and smoother way". When I use the
Trackpoint in Ubuntu 20.04 (or even 18.04) it
** Attachment added: "The monitors.xml with 100% scaling"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1870779/+attachment/5348985/+files/monitors.xml
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https:
Now, I switched back to Nvidia 440, scale 100% and I'm able to use the
system again. (Of course, I can hardly read anything, because it is so
small)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net
I did some additional testing. If I set the scale in .config/monitors.xml back
to 1, I am able to login again. So the problem is caused by the scaling. If I
set the scaling is set to 200% everything works well until the next reboot.
It tried the nvidia driver 435 and had the same effect.
I switc
Public bug reported:
I recently installed Ubuntu 20.04 (20200402) with LVM encryption and automatic
logon.
So I enter my encryption password and after the motherboards boot logo it will
login automatically to desktop. I also chose the additional drivers and so
nvidia-driver-440.
Everything seem
I found the wayland option on the login screen and i enabled it,
than i selected the nvidia 440 driver, rebooted and i was back to full hd, not
being able to get 4K @60
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https
intel-opencl-clang got a patch to work around the linking issue, it
builds now
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to intel-graphics-compiler in Ubuntu.
https://bugs.launchpad.net/bugs/1871345
Title:
FFE: Update Intel OpenCL stack, bu
I don't see an option at the login screen to switch to wayland, how do i
do this?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1870637
Title:
Nvidia+modeset: Can't set 4K@60Hz: HDMI max
The first time i was able to install third party propietary software
through the ubuntu installation process. (So nvidia was enabled after
the ubuntu installation process if i remeber correctly.
Today I installed the nvidia driver through Updatemanagement console, because
currently the ubuntu inst
I find nvidia optimus also can`t be poweroff. Note only when "lspci |
grep VGA" return (rev ff) means nvidia card has been shutdown. This
problem may come from Debian , most of(may be all of) Debian based
distribution have this problem. Fedora and Arch with bumblebee work fine
on my laptop.
** Al
*** This bug is a duplicate of bug 1745345 ***
https://bugs.launchpad.net/bugs/1745345
Just to add, I also get an error message sporadically popping up saying
"System program problem detected". Strange thing is that Budgie Desktop
Settings is accessible via right-click on desktop and selecting
*** This bug is a duplicate of bug 1745345 ***
https://bugs.launchpad.net/bugs/1745345
** Also affects: xorg-server (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: ubuntubudgie
** This bug has been marked a duplicate of bug 1745345
Xorg assert failure: Xorg: /us
Public bug reported:
I am creating a new computer platforms. It provides two video sources:
an Intel i915 DisplayPort and an AST2500 VGA. The i915 also provides
HDMI, but it is disconnected/disabled.
EXPECTED BEHAVIOR: Video is presented through the AST2500 to VGA and the
i915 to DisplayPort, m
Hi Phuc Minh Cai,
Please remove the old kernel and test this one:
https://people.canonical.com/~khfeng/lp1860754-3/
--
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/1860754
Title:
ASUS T100HAN bo
I don't know if this will help find the solution to this problem, but for what
it's worth, here's a solution that worked in my instance & I would very much
like to know why it worked.
System; Lenovo V155-15API (V155 Series)
Processor; AMD Ryzen 5 3500U
Graphics adapter; AMD Radeon RX Vega 8
Memor
I've got some new findings here. I tried to use the HDMI cable instead of
Display Port. With HDMI I was able to login and see the desktop. I was able to
reboot several times and it worked well.
Then I switched the scaling to 200% (I'm an old man ;-)) and everything looked
good. However after th
I've added systemd to the bug because that seems to be involved in
device permissions, as well as proving useful in the above comments.
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received t
Thank you, Hans.
The difference is CONFIG_GPIO_CRYSTAL_COVE=m, so we need to make it
builtin or make it load before i915 in initramfs.
I'll build another kernel for testing.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https:
** Attachment added: "config-5.6.0-8-generic"
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1860754/+attachment/5348572/+files/config-5.6.0-8-generic
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad
How did you install the NVIDIA driver? While I can see the kernel
modules being loaded, I don't see the NVIDIA libraries in the X log.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1870637
Thanks for the response.
Here is the file.
Ken
On Tue, Apr 7, 2020 at 11:50 AM Daniel van Vugt <
daniel.van.v...@canonical.com> wrote:
> Please:
>
> 1. Reproduce the hang again so the system creates new log files of the
> problem.
>
> 2. On the very next boot (in recovery mode now) run:
>
>
Public bug reported:
This is a request for a pre-ack to allow updating the Intel OpenCL
stack to versions that work with the default llvm release in focal,
which is 10.
The problem right now is that a bug in llvm-10 prevents builds against
it in some packages like intel-opencl-clang, which in tu
Thank you for reporting this bug to Ubuntu.
Ubuntu 14.10 (utopic) reached end-of-life on July 23, 2015.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more. Bu
Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more. Bu
gdm isn't involved in graphics directly so we can probably remove that
here...
** No longer affects: gdm3 (Ubuntu)
** Summary changed:
- GDM displays black screen for a few seconds after resuming from suspend while
using Nvidia proprietary drivers
+ black screen for a few seconds after resuming
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nvidia-graphics-drivers-430 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-430 in Ubuntu.
http
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gdm3 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-430 in Ubuntu.
https://bugs.launchpad.net/
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mutter (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-430 in Ubuntu.
https://bugs.launchpad.ne
I have a T100HAN in my personal hw collection, so I just booted up a
nightly build of the Fedora 32 workstation livecd on it and that works
fine for me. This nightly build is using a 5.6 kernel.
So the 5.6 kernel can work on this hardware. AFAIK Ubuntu, like Fedora
puts the i915 driver in the init
p.s.
There is another issue with 5.5.y and 5.6 kernels on Cherry Trail
hardware, at least with Fedora I'm seeing regular GPU freezes; and
specifically on the T100HAN also spontaneous reboots. I've seen the GPU
freezes on multiple Cherry Trail devices (these require ssh-ing in and
killing gnome-she
Since you seem to have working DRM support on the card you wish to use,
please try selecting "Ubuntu on Wayland" on the login screen.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1870637
** Also affects: nvidia-graphics-drivers-440 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: nvidia-graphics-drivers-440 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xorg-server (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1870
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nvidia-graphics-drivers-435 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchp
*** This bug is a duplicate of bug 1870637 ***
https://bugs.launchpad.net/bugs/1870637
Let's use bug 1870637. This is looking too familiar.
** This bug has been marked a duplicate of bug 1870637
Nvidia+modeset: Can't set 4K@60Hz: HDMI max TMDS frequency 30KHz
--
You received this bug
Unless the nvidia kernel driver is in drm modesetting mode, and I can't
see where that was turned on?...
** Summary changed:
- Nvidia driver installed but Xorg uses modeset on the Nvidia card.
+ Nvidia+modeset: Can't set 4K@60Hz: HDMI max TMDS frequency 30KHz
--
You received this bug notifi
Thanks.
Certainly sounds like a software bug if 'modeset' is being used while
the nvidia driver is installed.
** Summary changed:
- 20.04beta: Cannot set 3840x2160
+ Nvidia driver installed but Xorg uses modeset on the Nvidia card.
** Changed in: nvidia-graphics-drivers-435 (Ubuntu)
Please:
1. Reproduce the hang again so the system creates new log files or the
problem.
2. On the very next boot (in recovery mode now) run:
journalctl -b-1 > prevboot.txt
and then attach the resulting file here.
** Tags added: nvidia
** Summary changed:
- Problem Initiating Graphics C
Please:
1. Reproduce the hang again so the system creates new log files of the
problem.
2. On the very next boot (in recovery mode now) run:
journalctl -b-1 > prevboot.txt
and then attach the resulting file here.
--
You received this bug notification because you are a member of Ubuntu-X
> Does your computer not have multiple HDMI ports? If not then it looks
like there's a problem with how the Nvidia driver is installed here.
Yes it does have multiple hdmi ports, i currently use a ryzen 2200g cpu
and yes the problem is only there with the nvidia drivers (all three of
'm).
Nouveau
Oh, it's a desktop.
** Tags removed: hybrid
** Summary changed:
- [nvidia] Ubuntu 20.04 beta: Blank/black screen after login
+ [nvidia] Ubuntu 20.04 beta: Blank/black screen after login on an Nvidia-only
desktop (GeForce GTX 1060)
** Changed in: nvidia-graphics-drivers-440 (Ubuntu)
Stat
It sounds like this laptop has a hardware mux and it's trying to drive
the internal LCD directly from Nvidia. I wonder if that's correct or
some switching is missing?...
[ 7.875] (--) NVIDIA(GPU-0): Ancor Communications Inc ASUS MG28U (DFP-6):
connected
[ 7.875] (--) NVIDIA(GPU-0): Ancor
my nVidia Zotac grahpics card GT1030 has only one hdmi2.0 port.
I do not use onboard graphics!
** Attachment added: "0.jpg"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1870637/+attachment/5348475/+files/0.jpg
--
You received this bug notification because you are a member of Ub
I bought the 1030GT just because of the hdmi2.0 4K res @60hz
** Attachment added: "19.10.png"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1870637/+attachment/5348476/+files/19.10.png
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribe
** Package changed: ubuntu => xorg (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/1871303
Title:
Problem Initiating Graphics Card
To manage notifications about this bug go to:
https://
I'm sorry, there is not xorg directory under .local/share. It doesn't
exist in Ubuntu 19.10 either!
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1870779
Title:
[nvidia] Ubuntu 20.04 bet
You have been subscribed to a public bug:
Boot hangs up on initiating graphics. I can only finish the boot if I
use the recovery mode.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-91.92-generic 4.15.18
Uname: Linux 4.15.0-91-gene
** Summary changed:
- [vboxvideo] Ubuntu Login Screen Loop
+ [vboxvideo] Xorg crashes on startup using modeset with vboxvideo kernel driver
** Changed in: xorg-server (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
whic
*** This bug is a duplicate of bug 1870726 ***
https://bugs.launchpad.net/bugs/1870726
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1870726, so it is being marked as such. Please look
Please don't reopen old bugs. Open new bugs for any problems you might
have.
** Changed in: xorg (Ubuntu)
Status: New => Invalid
--
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/433231
Title
sudo apt-get install xfonts-cyrillic fixed it on ubuntu 18.04
** Changed in: xorg (Ubuntu)
Status: Invalid => New
--
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/433231
Title:
xorg: direc
The log file is attached. The issue result is like describe in bug 1871112.
But, only after changing the Graphics Controller to VMSVGA it takes me to
desktop properly.
** Attachment added: "xorg"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1871112/+attachment/5348444/+files/Xor
no need to get this in the xserver, if someone forces i965 dri driver
they can also live with the brief ugliness after login
** Changed in: xorg-server (Ubuntu Focal)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed t
78 matches
Mail list logo
