I was having the same fail/mistake but in Ubuntu 18.04 (Gnome and
vanilla desktop), I don't know why but since 2 weeks ago (since an
update of gnome-control-center I think, but I'm not sure) the lock
screen just doesn't work and neither the settings, it's like zhiwei
said, it doesn't allow any
Talked about this topic on
https://forums.developer.nvidia.com/t/ubuntu-20-04-second-monitor-
doesnt-work-ubuntu-and-nvidia-settings-detects-it/124380/13
generix said maybe's a problem with the Intel GPU Firmware.
** Also affects: xserver-xorg-video-intel (Ubuntu)
Importance: Undecided
Update: If I adjust the minimum resolution, sometimes appears the second
desktop, but instantly disappear then.
--
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/1871721
Update: Nope, it's still without working. :(
--
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/1871721
Title:
Second Monitor on HDMI blank screen with Nvidia & Ubuntu
Hi there, IT's not a bug in X apparently, because I tried with Intel GPU
on the laptop with Wayland and nothing works. Don't know if it's because
it's working with XWayland (maybe? and how can I try with Wayland
native?)
I tried with the last kernel (4.16), but nothing works. I'll try with
4.17.
Tried with Lightdm and 435 driver. Tried with Nvidia only and setting as
"maximum performance".
Nothing.
Also I tried with only Intel and Wayland and it doesn't work neither.
Seems a problem with Intel, I'm not sure. Nvidia detects the second
monitor, it's just in blank screen.
I reinstalled
Same result Kai-Heng. :(
--
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/1871721
Title:
Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel &
** Description changed:
I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary
drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use
it, but I saw that I cannot use it, I just see a blank screen. I tried with a
TV of my room and same. The funny
I'm sure around 99% it's Intel.
--
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/1871721
Title:
Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel &
apport information
** Attachment added: "NvidiaBugReportLog.txt"
https://bugs.launchpad.net/bugs/1871721/+attachment/5391349/+files/NvidiaBugReportLog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1871721/+attachment/5391352/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1871721/+attachment/5391348/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1871721/+attachment/5391351/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1871721/+attachment/5391347/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1871721/+attachment/5391350/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1871721/+attachment/5391353/+files/ProcModules.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1871721/+attachment/5391354/+files/UdevDb.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
apport information
** Attachment added: "XorgLogOld.txt"
https://bugs.launchpad.net/bugs/1871721/+attachment/5391356/+files/XorgLogOld.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
apport information
** Attachment added: "XorgLog.txt"
https://bugs.launchpad.net/bugs/1871721/+attachment/5391355/+files/XorgLog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1871721/+attachment/5391346/+files/Lsusb.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
apport information
** Attachment added: "BootLog.txt"
https://bugs.launchpad.net/bugs/1871721/+attachment/5391340/+files/BootLog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1871721/+attachment/5391345/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
apport information
** Attachment added: "DpkgLog.txt"
https://bugs.launchpad.net/bugs/1871721/+attachment/5391343/+files/DpkgLog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1871721/+attachment/5391342/+files/Dependencies.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1871721/+attachment/5391341/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1871721/+attachment/5391344/+files/Lspci.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
I tried with Wayland but only with Intel (there's no option with
Nvidia), same result. Maybe 'cause's working under XWayland?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
apport information
** Tags added: apport-collected third-party-packages ubuntu
** Description changed:
I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary
drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use
it, but I saw that I cannot use
apport information
** Attachment added: "nvidia-settings.txt"
https://bugs.launchpad.net/bugs/1871721/+attachment/5391358/+files/nvidia-settings.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
apport information
** Attachment added: "xdpyinfo.txt"
https://bugs.launchpad.net/bugs/1871721/+attachment/5391359/+files/xdpyinfo.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
apport information
** Attachment added: "Xrandr.txt"
https://bugs.launchpad.net/bugs/1871721/+attachment/5391357/+files/Xrandr.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
PD: The mesa driver of intel's working with the same version of git,
just trying to make it work. But with the stable version doesn't work
neither. Just in case you wanted to know.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
On W10 it's setted as 1920x1080 - 59Hz. It works perfectly.
I tried with this resolution on Ubuntu 20.04. Still doesn't works.
** Attachment added: "Resolution and refresh second monitor on W10.PNG"
I think it means 59,94Hz, which's available on Linux too.
And okey, I'll do it, thank you Kai-Heng!
--
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/1871721
Title:
Just to let you know, if I adjust the resolution to 800x600 it works,
but "blinks" every 10-15 seconds. It's so strange.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
Done. Here's the file.
PD: I was thinking the same when I read the "LSPCON" Intel's
funcionality
** Attachment added: "dmesg"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1871721/+attachment/5391375/+files/dmesg
--
You received this bug notification because
Hi slovic.
If you see the nvidia-settings you probably can see the second monitor
is detected by the Nvidia card. I think this is a problem of Intel,
'cause the second monitor's connected via HDMI, which is connected to
Intel GPU.
Please click on "this bug affects me too" so we can make see it
** Tags added: focal
** Tags added: amd64
** Tags added: asus intel nvidia
--
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/1871721
Title:
Second Monitor on HDMI
** Also affects: focal (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: focal (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/1871721
Title:
Second
** Description changed:
I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary
drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use
it, but I saw that I cannot use it, I just see a blank screen. I tried with a
TV of my room and same. The funny
Apparently this happens to Ubuntu 18.04.4 and 19.10 (and obviously on
20.04). But on 18.04.1 the second monitor works perfectly. Windows 10
too.
This seems like a mistake or bug on the Mesa/Kernel.
At the moment, I'll be on 18.04.1 but updated.
--
You received this bug notification because you
** Summary changed:
- Second Monitor on HDMI blank screen with Nvidia & Ubuntu 20.04? (ASUS Laptop)
+ Second Monitor on HDMI blank screen with Nvidia+Intel & Ubuntu 20.04? (ASUS
Laptop)
** No longer affects: mesa-utils (Ubuntu)
** Summary changed:
- Second Monitor on HDMI blank screen with
I have the same bug here. You can activate or turn it off but the
bluetooth is always "off", for me happens sometimes when I reboot.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
Public bug reported:
OS: Ubuntu 23.10
The version of the package: gnome-shell 45.0-1ubuntu2
What you expected to happen: Should work with no glitches or crashes
when you are dealing with multiple windows like Nautilus, Steam,
Telegram and/or Firefox.
What happened instead: Apparently
New info: I realised this is something related to my integrated graphic
in my laptop (AMD Radeon graphic integrated). So, if I launch Firefox,
Steam etc. with my dedicated graphic (AMD Radeon RX 5600m), works
perfectly, no issues.
--
You received this bug notification because you are a member of
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7062
Seems it's closed. However, I'm still seeing this in 23.10. I see it
when I open Steam. Definitely it has something to do with XWayland.
--
You received this bug notification because you are a member of Desktop
Packages, which is
I just realised it happens when I'm change from 60hz to 120hz. Doesn't
mean in 120hz my monitor crash, just when I make a change in my display,
sometimes the desktop makes that strange glitch.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
Public bug reported:
Few days ago it was working perfectly, but today I saw in gdm the button
to change the session wayland/xorg isn't there. Ubuntu only loads Xorg
by default.
Laptop: MSI Alpha 17 A4DEK
CPU: AMD Ryzen 7 4800
GPU: AMD Radeon RX 5600m
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Public bug reported:
When I connect from my laptop an external monitor with different
refresh, instantly crash the session and get me back to the gdm. After
connect the monitor from the restart the session, I can use it without
any issues, but if I disconnect it and I connect it again, the
Confirmed. This fixed the issue.
Thanks!
--
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/1969422
Title:
gnome-shell crashed with SIGSEGV in gbm_surface_release_buffer() from
** No longer affects: linux (Ubuntu)
** Also affects: linux (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/2039570
Title:
Bug fixed with kernel 6.6.x, more info, please see here:
https://gitlab.gnome.org/GNOME/mutter/-/issues/3036
--
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/2039570
Title:
[amdgpu]
No, this was an issue happening in monitors connected via HDMI.
--
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/2039570
Title:
[amdgpu] Fullscreen in any Wayland / Xwayland window
Public bug reported:
When I connect the laptop to the sound bar hdmi and the sound bar to the
monitor, it tries to connect and Ubuntu detects it, but nothing appears
on the screen.
My HDMI works as it should, tested directly when it's connected to the
monitor. I have tried on a laptop other than
6.5.13 > "Test amd64/build failed (rc=2, on=amd64, time=0:07:36,
log=amd64/log)".
@superm1
In 6.6.6 this issue seems fixed FYI.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
How much do we have to wait if this fix is already released but not in
Ubuntu 23.10?
--
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/2038998
Title:
[amdgpu] Screen artifacts/UI oddities
I opened a report here in freedesktop:
https://gitlab.freedesktop.org/drm/amd/-/issues/2993#note_2172154
And as Michel Dänzer says, it's possible this is an issue related to
Mutter. Here in these logs from journalctl gnome-shell I attach here,
you can see the messages that appear just when, upon
Thanks for the clarification, Daniel.
Could makes sense if it's related to Mesa. I have the feeling that these
strange artifacts, appear especially when I launch windows and apps from
the integrated graphics, instead of the dedicated.
--
You received this bug notification because you are a
Tested with COGL_DEBUG parameter added and at the moment, I can't
reproduce these artifacts. I will keep trying it today.
--
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/2038998
Title:
Here, there's an issue opened in Gitlab Gnome about mutter that could be
related to this issue (thanks again to Michel Dänzer):
https://gitlab.gnome.org/GNOME/mutter/-/issues/3036
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #3036
I tested it again, and at the moment I reproduce this issue with a
xwayland window (in this case, Discord app), but all gnome was stable,
which is strange (but good). See screenshot attached.
** Attachment added: "Captura desde 2023-11-21 00-42-42.png"
61 matches
Mail list logo
