Thank you for reporting this bug to Ubuntu.
Ubuntu 19.10 (eoan) reached end-of-life on July 17, 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. But
Hi,
i also have the X1 and i had the same problem today.
When my X1 didnt have an external monitor attached, everything was fine.
When an external monitor in, everything went black (but mouse cursor
visible). I had PhpStorm open.. so i closed it and tried again and it
worked. Afterwards i could o
** Changed in: linux
Status: Confirmed => Unknown
** Bug watch added: gitlab.freedesktop.org/drm/intel/issues #91
https://gitlab.freedesktop.org/drm/intel/issues/91
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu
-- GitLab Migration Automatic Message --
This bug has been migrated to freedesktop.org's GitLab instance and has
been closed from further activity.
You can subscribe and participate further through the new bug through
this link to our GitLab instance:
https://gitlab.freedesktop.org/drm/intel/issu
You are reporter of the issue currently having low priority. Do you
still see issue. If so, please spesify clearly what is impact to you.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1849
The folks over at
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849484 are saying
they think that bug is the same as this one, but I don't think it is.
What do you think?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubu
I ordered a brand new, "premium" Roswell HDMI cable from Newegg and the
problem occurs with that cable as well.
Now that the problem has occurred with three different cables, two of
them new, with no adapters in the middle, I hope we can agree that it is
unlikely that this is a cable issue.
--
Y
Because in my experience the probability of encountering a low quality
cable or bad connection is quite high. Cheap cables are often the norm,
not the exception. Sometimes you need to try a few till you find one
that works reliably, depending on the resolution and depending on the
devices involved.
I am somewhat surprised that you think the most likely explanation is a
cable issue. The likelihood of a bad cable being the issue when the
problem occurs with two different cables and is triggered by specific
apps seems, to me, vanishingly low.
Can you elaborate on why you consider that the most
Launchpad has imported 16 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=105601.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://he
Thanks. I still feel the first solution we should be aiming for is
(another) new HDMI cable. If you've tried a few (without any adapters!)
and none work then I would treat this as a proper kernel bug. The
closest existing one I have found is:
https://bugs.freedesktop.org/show_bug.cgi?id=105601
**
[72227.300557] [drm:drm_dp_dual_mode_detect [drm_kms_helper]] *ERROR*
Unexpected DP dual mode adaptor ID 50
[72228.173908] [drm:drm_dp_dual_mode_detect [drm_kms_helper]] *ERROR*
Unexpected DP dual mode adaptor ID 50
[72229.956316] [drm:drm_dp_dual_mode_detect [drm_kms_helper]] *ERROR*
Unexpected
I mean if your monitor shows any faults at all while using it then each
time open a Terminal window and run:
dmesg
Then please copy and paste the most recent messages (probably mentioning
"kernel: i915" or "kernel: drm") to here.
--
You received this bug notification because you are a member
"If you see changes like that after boot then please attach output from
'dmesg' showing the period of time when the change occurred."
I'm sorry, I'm not sure what you're asking me to watch for here. Can you
clarify?
--
You received this bug notification because you are a member of Kernel
Package
If you see changes like that after boot then please attach output from
'dmesg' showing the period of time when the change occurred.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1849484
T
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1849484/+attachment/5300905/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
FYI: While apport-collect was running, my screens went blank briefly and
then when they came back my monitor configuration was wrong: the ultra-
wide monitor was at a lower resolution than it's supposed to be and the
two monitors' relative positions were not configured correctly.
Unplugging the ult
apport information
** Attachment added: "xdpyinfo.txt"
https://bugs.launchpad.net/bugs/1849484/+attachment/5300918/+files/xdpyinfo.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => New
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notif
apport information
** Attachment added: "Xrandr.txt"
https://bugs.launchpad.net/bugs/1849484/+attachment/5300917/+files/Xrandr.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1849484
apport information
** Attachment added: "XorgLogOld.txt"
https://bugs.launchpad.net/bugs/1849484/+attachment/5300916/+files/XorgLogOld.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bug
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1849484/+attachment/5300909/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "XorgLog.txt"
https://bugs.launchpad.net/bugs/1849484/+attachment/5300915/+files/XorgLog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1849
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1849484/+attachment/5300908/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1849484/+attachment/5300906/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.l
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1849484/+attachment/5300907/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1849484/+attachment/5300914/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bug
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1849484/+attachment/5300910/+files/PulseList.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1849484/+attachment/5300911/+files/RfKill.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1849484
apport information
** Attachment added: "UnitySupportTest.txt"
https://bugs.launchpad.net/bugs/1849484/+attachment/5300913/+files/UnitySupportTest.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launc
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1849484/+attachment/5300912/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1849484
apport information
** Attachment added: "MonitorsUser.xml.txt"
https://bugs.launchpad.net/bugs/1849484/+attachment/5300904/+files/MonitorsUser.xml.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launc
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1849484/+attachment/5300903/+files/Lsusb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1849484
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1849484/+attachment/5300901/+files/IwConfig.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/18
apport information
** Attachment added: "DpkgLog.txt"
https://bugs.launchpad.net/bugs/1849484/+attachment/5300900/+files/DpkgLog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1849
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1849484/+attachment/5300902/+files/Lspci.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1849484
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1849484/+attachment/5300899/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
apport information
** Tags added: apport-collected ubuntu
** Description changed:
I have an LG ultra-wide (2560x1080) monitor.
Sometimes when I plug it into my laptop, whose screen was working fine
before I plugged it in, both screens go black but nothing else happens.
I can still see
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1849484/+attachment/5300898/+files/CRDA.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1849484
Ti
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1849484
and then change the status of the bug to 'Confirmed'.
If, due to the nature
> Synology Drive does kernel stuff -- I believe it uses inotify to
monitor directories for changes -- so I'm suspecting that there's
something misbehaving in the kernel and something that Synology Drive
does is banging up against it.
I think you might be right.
** Changed in: linux (Ubuntu)
I tried a different cable. It didn't help.
Also, I can trigger my monitors freaking out as described above merely
by launching the Synology Drive Client when the ultra-wide monitor is
connected.
Also, the issue seems to be triggered even if the applet isn't visible
in my top bar, i.e., even if th
It's not clear to me how this can be a cable or monitor issue when it
only happens in Xorg and it happens much more frequently when one
particular app is running (see comment #4). Having said that, I will try
to find a spare HDMI cable and test.
I am not using an adapter, I'm plugging an HDMI cabl
** No longer affects: mutter (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1849484
Title:
[X1 Carbon 7, i915, HDMI] Ultra-wide monitor recognized properly when
plugged in onl
Are you using some kind of adaptor between HDMI and DisplayPort? I
wonder if this monitor needs proper DisplayPort for multi-stream.
** Changed in: mutter (Ubuntu)
Status: New => Incomplete
** Changed in: xorg-server (Ubuntu)
Status: New => Incomplete
** Also affects: linux (Ubuntu
Hmm, it shouldn't be a multi-stream problem. It looks like you only need
HDMI v1.3 to drive that resolution and your laptop supports HDMI 1.4b
already.
So mainly I suspect a bad HDMI cable, bad HDMI adaptor, or just faulty
EDID data coming from the monitor.
--
You received this bug notification
45 matches
Mail list logo