I was able to get something working on my win 11 i9-13900H discrete
RTX2000 laptop.
I used:
mks.enable3d = "TRUE"
mks.enableDX12Renderer = "TRUE"
mks.enableDX11Renderer = "FALSE"
mks.dx12.vendorID = "0x17AA"
and I also had to do:
settings->system->dislay->graphics
entries for both vmware.exe
Also tried virtualbox this morning on a different win 11 machine with an
nvidia laptop gpu and same thing.
No 3D acceleration is not stable on vmware (crashes after a while)
With 3D acceleration black screens really fast on vmware and virtualbox (which
uses the vmware driver by default)
--
You
Microsoft Windows [Version 10.0.22631.3447]
Processor AMD Ryzen 7 3700X 8-Core Processor, 3600 Mhz, 8 Core(s), 16
Logical Processor(s)
System ModelX570 AORUS PRO WIFI
RTX 2070
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in
vmware 17.5 win 11
not fixed with todays iso. mesa is 24.0.5.
Can see gui without enable 3d acceleration, but black screen and have to task
manager kill with 3d acceleration.
rtx 2070
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in
Public bug reported:
Upgrading from 23.04 to 23.10 resulted in corrupt screen when switching
to lower resolutions. Only maximum resolution works.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
Uname: Linux
need update to Ubuntu 23.10
** Changed in: xwayland (Ubuntu)
Status: New => Fix Released
--
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/2036422
Title:
XWayland cannot click
This bug is fully resolved by update to Ubuntu 23.10
--
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/2036422
Title:
XWayland cannot click fullscreen window beyond 1024x768
To manage
Public bug reported:
Computer unresponsive after closing laptop screen and reopening. GDM
screen does not appear to login, just see contents of the X session
before i closed the lid. mouse moves and hardware buttons (mute, caps
lock etc) are responsive with LEDs. Have to hard reboot to login and
Additional information:
This bug only manifests when using Ubuntu in Virtualbox.
This bug manifests when Virtualbox Virtual screen is set to scale mode
Workaround: When I set Virtualbox Virtual screen to fixed resolution the
problem goes away in some apps.
In other apps the workaround doesn't
Public bug reported:
When I click in any xwayland window beyond the top-left 1024x768
rectangle, the window below is clicked.
Expected result: The xwayland window registers the click
Actual result: The xwayland window registers the click correctly only in the
top left 1024x768 pixels rectangle.
Public bug reported:
all kinds of graphic issues, cannot scale desktop properly, icons vanish
but reappear temporarily when hovering over missing icon then text
vanishes again.
ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu
I don't see this happening anymore as of the release of linux-
image-5.19.0-28-generic. Neither the -28 nor the -29 kernel seem to
cause this to happen anymore, so I suspect this can probably be closed.
--
You received this bug notification because you are a member of Ubuntu-X,
which is
Since there appears to be upstream patches in kernel 6.0 and Mesa 22.3.1
which fix this, perhaps it would be possible to backport those to the
versions in Ubuntu 22.10? If not, would it at least be possible to
upload such packages to Lunar so that there's an option which doesn't
involve
Public bug reported:
I see frequent (multiple times per day) hangs on my Lenovo ThinkPad X1
Carbon Gen 10. When this occurs, part of the image tears away and X
becomes unusable. Sometimes the cursor continues to move for a short
time after the fact. In order to recover, I must SSH into the
Steve, please open a new report.
Thanks!
--
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/1493921
Title:
X server fails to set correct mode on resume from sleep (NVIDIA:
Setting a mode on head
Public bug reported:
Ubuntu 21.04, mesa 21.0.1-2 amd64
Upstream MR:
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9568
Graphical glitches can be seen occasionally on screen with the RX 6700
XT graphics card.
This is fixed upstream with the above merged MR, so please backport
it...
Public bug reported:
Your system is providing 3D via software rendering rather than hardware
rendering. This is a compatibility mode which should display 3D
graphics properly but the performance may be very poor. If the problem
you're reporting is related to graphics performance, your real
** Description changed:
* Kubuntu version 20.04
When the keyboard is attached, running `xinput` produces:
-
⎡ Virtual core pointer id=2[master pointer (3)]
⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)]
...
⎜ ↳ NXP
Public bug reported:
* Kubuntu version 20.04
When the keyboard is attached, running `xinput` produces:
⎡ Virtual core pointer id=2[master pointer (3)]
⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)]
...
⎜ ↳ NXP Semiconductors LPC
Public bug reported:
Nvidia laptop support is basically nonexistent for linux. I've had
nothing but problems with Ubuntu
ProblemType: Package
DistroRelease: Ubuntu 19.10
Package: xserver-xorg-video-nvidia-430 (not installed)
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux
Hi Dexuan,
Sorry for delay in answer - I have installed fresh Server 19.10
(installation is of course different - EFI partition setup by installer,
etc. etc.) and after kernel boot messages I've got immediately login
prompt.
After that I've done "sudo apt-get install ubuntu-desktop" and issue is
Dear Ubuntu devs,
issue was reported on 17.10 and still - Ubuntu 19.04 starts fast, Ubuntu
19.10 upgraded from 19.04 / installed from scratch starts very slow.
ANY IDEAS?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
Hi,
If possible, please try 19.04 or LTS 18.04 and compare startup time - my
guess is that it will start almost immediately and you will see, that
you already reproduced it :)
I'm sure let's say in 90% :) -> 28 seconds is looonnnggg (like I said,
I've got about 2 seconds for older Ubuntu).
--
Hi,
Thanks for comments #25 and #26,
I don't know how fast is your machine, but on mine earlier (before
19.10) I had startup in just few seconds, now have this delay. Yes, this
is maybe not critical, but should be fixed, because can go into Ubuntu
20.04 ;)
Anyway, I'm using stock kernel 5.3 +
I've tried to (1) boot the same machine with kernel 5.0.0.32 (2) create
new machine without upgrading from 19.04
Results were the same, anybody?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
apport information
** Attachment added: "xdpyinfo.txt"
https://bugs.launchpad.net/bugs/1848534/+attachment/5298231/+files/xdpyinfo.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1848534/+attachment/5298226/+files/UdevDb.txt
--
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/1848534
apport information
** Attachment added: "XorgLog.txt"
https://bugs.launchpad.net/bugs/1848534/+attachment/5298228/+files/XorgLog.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
apport information
** Attachment added: "XorgLogOld.txt"
https://bugs.launchpad.net/bugs/1848534/+attachment/5298229/+files/XorgLogOld.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
apport information
** Attachment added: "Xrandr.txt"
https://bugs.launchpad.net/bugs/1848534/+attachment/5298230/+files/Xrandr.txt
--
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/1848534
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1848534/+attachment/5298227/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1848534/+attachment/5298224/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1848534/+attachment/5298217/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1848534/+attachment/5298221/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1848534/+attachment/5298220/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
apport information
** Attachment added: "DpkgLog.txt"
https://bugs.launchpad.net/bugs/1848534/+attachment/5298218/+files/DpkgLog.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1848534/+attachment/5298225/+files/PulseList.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1848534/+attachment/5298223/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1848534/+attachment/5298216/+files/CRDA.txt
--
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/1848534
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1848534/+attachment/5298222/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
apport information
** Attachment added: "MonitorsUser.xml.txt"
https://bugs.launchpad.net/bugs/1848534/+attachment/5298219/+files/MonitorsUser.xml.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
apport information
** Tags added: apport-collected ubuntu
** Description changed:
AFter upgrade system shows graphic artefacts for a moment and then text
cursor for about minute (it looks like hanged) and then starts.
In 19.04 startup required 1 or 2 seconds.
ProblemType: Bug
One thing, which I didn't mentioned earlier:
there is graphic artifact (color on half of screen), then "Ubuntu
loading" dots, then text cursor with delay, then login screen.
I forgotten about "Ubuntu loading" dots.
lspci -k output is empty (even with sudo), the rest is attached.
** Attachment
And one more log
** Attachment added: "xorglogs.tar.gz"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1848534/+attachment/5298158/+files/xorglogs.tar.gz
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
sordna, regarding your specific problem, please file a bug against apport via a
terminal:
ubuntu-bug apport
In this new report, please copy/paste the reproduction steps, and result
as per terminal command.
--
You received this bug notification because you are a member of Ubuntu-X,
which is
** No longer affects: mesa (Ubuntu)
** Project changed: mesa => mesa (Ubuntu)
** Changed in: mesa (Ubuntu)
Status: Unknown => New
** Changed in: mesa (Ubuntu)
Remote watch: freedesktop.org Bugzilla #72877 => None
** Changed in: mesa (Ubuntu)
Status: New => Triaged
**
I can describe that on latest Ubutnu 18.04.3 LTS (Linux local 5.0.0-29-generic
#31~18.04.1-Ubuntu SMP Thu Sep 12 18:29:21 UTC 2019 x86_64 x86_64 x86_64
GNU/Linux) that there is following behavior for suspend (on HP Spectre x360
15").
- For Nvidia GPU Prime profile, the reliability of wake-up
COMMAND
/dev/snd/controlC0: m 1199 F pulseaudio
CurrentDesktop: Unity
Date: Thu Feb 18 22:40:06 2016
HibernationDevice: RESUME=UUID=1a9cc3e7-ec1c-4f67-95c9-f96d010b2a7a
InstallationDate: Installed on 2016-02-10 (8 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial
Stephan Fabel, this report is being closed due to your last comment
https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/1724307/comments/28 regarding you no longer use the
hardware. For future reference you can manage the status of your own
bugs by clicking on the current status in the
Quoc Khanh Le (qkle), it will help immensely if you use Ubuntu with the
computer the problem is reproducible with and file a new report via a terminal
to provide necessary debugging logs:
ubuntu-bug linux
Please feel free to subscribe me to it.
--
You received this bug notification because
Stephan Fabel, could you please advise to all of the following:
1) Has the issue been tested with using the latest DisplayLink driver
(now 5.2.14)?
2) To see if this is already resolved in Ubuntu, could you please test
http://cdimage.ubuntu.com/daily-live/current/ and advise to the results?
3)
Hi,
I have switched from Gnome to i3, this fixed the issue for me.
The underlying issue might have been fixed by
https://cgit.freedesktop.org/drm-
tip/commit/?id=3cf71bc9904d7ee4a25a822c5dcb54c7804ea388, but I didn't
check.
--
You received this bug notification because you are a member of
Michael Neuffer, this report has been missing key information since 2014
->
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1268151/comments/33
.
Hence, could you please test http://cdimage.ubuntu.com/daily-live/current/ and
if reproducible please run the following command once from a
Hark:
1) For one who is using 16.04, an upgrade for the X stack is available
following instructions from
https://wiki.ubuntu.com/Kernel/LTSEnablementStack . Could you please
advise to the results?
2) Regarding the package xserver-xorg-video-ati, this is fixed as per
Hark, thank you for reporting this and helping make Ubuntu better.
1) To confirm a regression, has this always been an issue since you
installed "Ubuntu-Server 10.04 LTS" or is this something that started to
happen after an update?
2) To clarify, did you personally test the WORKAROUNDs noted in
Hark (cab902), it will help immensely if you filed a new report with Ubuntu by
ensuring you have the package xdiagnose installed, and that you click the Yes
button for attaching additional debugging information running the following
from a terminal:
ubuntu-bug xorg
Also, please feel free to
yoshiki2, it will help immensely if you use Ubuntu with the computer the
problem is reproducible with and file a new report via a terminal to provide
necessary debugging logs:
ubuntu-bug linux
Please feel free to subscribe me to it.
--
You received this bug notification because you are a
opensas:
1)
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1816947/comments/43
>"Then I tried with several versions from the upstream kernels..."
Which upstream kernels did you test precisely?
2)
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1816947/comments/46
>"Any idea about
** Tags added: needs-bisect- needs-upstream-testing
--
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/1816947
Title:
[Dell XPS L321X] Touchpad not working after last apt-get upgrade
To manage
opensas, the next step is to fully commit bisect from 4.13.13 to 4.15.
This will allow for a direct review of the offending commit for either
reverting, or further improvements. Could you please do this following
https://wiki.ubuntu.com/Kernel/KernelBisection ? This article was
written for folks
opensas:
To further narrow the regression, in Ubuntu 18.04 or higher, if you
install kernel 4.13.3 from https://wiki.ubuntu.com/Kernel/MainlineBuilds
does the touchpad work again?
** Tags removed: regression-potential
** Tags added: regression-release
--
You received this bug notification
opensas:
To confirm the regression point, could you please test a live
environment of https://wiki.ubuntu.com/ArtfulAardvark/ReleaseNotes and
advise to the results?
** Description changed:
- The touchpad doesn't work.
+ The touchpad doesn't work unless the cursor is moved slowly.
opensas:
1) To advise, you don't have to apport-collect any further unless
specifically requested to do so.
2) Does the touchpad work in the live environment of 18.04 without using
any WORKAROUND?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed
opensas, please advise to all of the following:
1) When discussing this issue, please keep it to only one machine (the
Dell XPS 13 L321X, not multiple) and Ubuntu (not popos! or some other
unsupported distro, unofficial flavor, etc.).
2) Regarding this issue with the Dell XPS 13 L321X, is this
** Description changed:
+ The touchpad doesn't work.
- already filed at:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1096046
-
- check: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-
- synaptics/+bug/1096046/comments/33
-
- affects:
** Summary changed:
- Touchpad not working after last apt-get upgrade
+ [HP Folio 13 Notebook PC] Touchpad not working after last apt-get upgrade in
Precise
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in
Closing as upstream issue, not using Xenial, not using older version of
VLC or xserver-xorg-video-intel, and issue may already be addressed in
later versions of Ubuntu with later version of xserver-xorg-video-intel
and VLC.
** No longer affects: vlc
** No longer affects: xserver-xorg-video-intel
** Tags removed: bios-outdated-2.34
** Tags added: bios-outdated-2.50 cosmic
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1492639
Title:
external monitor doesnt wake up
** Tags removed: bios-outdated-2.49
** Tags added: bios-outdated-2.50
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1552040
Title:
[Lenovo ThinkPad T440s] Laptop sometimes
As per
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1554471/comments/9 .
** Changed in: xorg (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
Just hit me, kernel 4.19.8-liquorix-amd64, Ubuntu 18.10. I was running
with modesetting, but decided to change to intel driver (freshly
compiled from git) to see if I run into it again (it seems pretty rare
though so will probably be tough to hit). Has anyone definitely hit it
on
Hi,
For some reason apport-collect just exit at the end, and doesn't send anything
to launchpad...
No error, no crash -- just exit to shell when being instructed to send the
report.
$ apport-collect -p xserver-xorg-core 1799920
The authorization page:
Just got the external screen in the same state again (ie, blank) after
leaving the desk for 5-10 minutes.
While in that state, the external screens tells that it doesn't receive any
signal.
Switching it's input from it's usual DP input to another one, and switching
back again does restore the
Public bug reported:
Hi,
Since upgrading to 18.10, my Dell P2715Q external screen (connected to a
Dell XPS 13 9343 laptop) fails to wakeup after a period of inactivity:
- leave the laptop idle for a while, gnome screen lock will take over
and shut down the internal panel & external screen (it
As per
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1610591/comments/53
.
** No longer affects: xserver-xorg-video-ati (Ubuntu)
** Project changed: xserver-xorg-driver-ati => xserver-xorg-driver-ati
(Ubuntu)
** Changed in: xserver-xorg-driver-ati (Ubuntu)
Importance: Unknown =>
** No longer affects: xserver-xorg-video-ati (Ubuntu Precise)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
https://bugs.launchpad.net/bugs/1085751
Title:
[drm:radeon_cs_ioctl] *ERROR* Failed to parse
** Package changed: fedora => xorg (Fedora)
** Changed in: xorg (Fedora)
Importance: High => Undecided
** Changed in: xorg (Fedora)
Status: Confirmed => New
** Changed in: xorg (Fedora)
Remote watch: freedesktop.org Bugzilla #54133 => None
** No longer affects: linux (Ubuntu
Norm Paul, it is most helpful if you use the host computer (not VM) the problem
is reproducible with and file a new report with Ubuntu by first ensuring the
package xdiagnose is installed, and click the Yes button for attaching
additional debugging information after running the following from a
Marking Fix Released as not reproducible in latest Ubuntu release as per
https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/1787651/comments/3, and as defined by
https://wiki.ubuntu.com/Bugs/Status .
** Changed in: xorg-server (Ubuntu)
Status: New => Fix Released
--
You received
Leônidas, one may update their kernel and xorg stack in 16.04 via
https://wiki.ubuntu.com/Kernel/LTSEnablementStack .
** Changed in: xorg-server (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
Leônidas, thank you for reporting this and helping make Ubuntu better.
1) To see if this is already resolved in Ubuntu, could you please test
this via http://cdimage.ubuntu.com/daily-live/current/ and advise to the
results?
2) To clarify, does the following provide a WORKAROUND:
Add
Leônidas (leonidasklein), it is most helpful if you use the computer the
problem is reproducible with and file a new report with Ubuntu, by first
ensuring the package xdiagnose is installed, and click the Yes button for
attaching additional debugging information after running the following from
fokedFromTheLife:
1) Regarding the following non-default kernel parameters in use, could you
please advise to each individually on why it was put in place, and if it is
necessary for the touchpad to work:
nouveau.modeset=0
tpm_tis.interrupts=0
acpi_osi=Linux
i915.preliminary_hw_support=1
** Tags added: cosmic
--
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/1784998
Title:
After a while touchpad doesn't work
To manage notifications about this bug go to:
Sergey Menshikov, it is most helpful if you use the computer the problem is
reproducible with, and file a new report with Ubuntu via a terminal:
ubuntu-bug linux
Please feel free to subscribe me to it.
--
You received this bug notification because you are a member of Ubuntu-X,
which is
fokedFromTheLife:
1)
>"so when i install ubuntu the touchpad don't work i go to
>http://pclub.in/2017/01/06/Linux-on-Asus-ROG.html and that' worked"
To clarify, you are stating that by default, the touchpad doesn't work
at all. However, after using the non-default kernel parameters, and
fokedFromTheLife, thank you for reporting this and helping make Ubuntu
better. Please answer all of the following:
1) Regarding your Bug Description comment:
>"after a while..."
1a) Could you please define specifically how long a while is? Seconds, minutes,
hours, etc.?
1b) Could you please
** Tags removed: bios-outdated-1.42
** Tags added: bionic bios-outdated-1.46
--
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/1715749
Title:
Intermittent black screen on HP EliteBook 840 G1
To
Chris Guiver, you may need to use:
sudo ubuntu-bug /var/crash/FILENAME.crash
when filing crash reports in order for the upload/uploaded files to be
generated, and, in turn, to get the errors reported successfully.
Given the reproducibility of the crash, and how you are using the latest
Ubuntu
** Description changed:
// this bug was reported for 18.04.
// I had just had it occur (first time) on 18.10
// new details will be comment @ end
my box is 18.04 (was 17.10 installed; standard Ubuntu with MATE & XFCE
desktops added)
I sleep my XFCE (xubuntu) machine rather than
Chris Guiver:
1) While the issue is being root caused, please keep light-locker, and
caffeine uninstalled.
2) Regarding the file:
-rw-r- 1 guiverc whoopsie 20M Aug 1 08:28 _usr_lib_xorg_Xorg.1000.crash
No error reports have been reported to errors since 2018-07-11. One may
further confirm
Chris Guiver:
1) To confirm, please run the following command and post the results:
sudo cat /var/lib/whoopsie/whoopsie-id
2) To confirm a WORKAROUND in 18.10, if you uninstall both light-locker
and caffeine simultaneously, is a crash still reproducible?
** Changed in: xorg (Ubuntu)
Anders Magnus Andersen, this bug report is being closed due to your last
comment https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
nouveau/+bug/1613863/comments/10 regarding you don't have the equipment
anymore. For future reference you can manage the status of your own bugs
by
Chris Guiver, this report is being closed due to your last comment
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1772542/comments/17
regarding this being fixed with an update. For future reference you can
manage the status of your own bugs by clicking on the current status in
the yellow line
vik:
1) As per the sticker of the monitor itself (not from the Bug
Description, or the result of a terminal command), could you please
provide the full monitor manufacturer and model?
2) Regarding how you have the monitor connected, is it plugged into the
dock's DVI-I, or DisplayPort port? If
Kai Mast:
1) As per the sticker of the monitor itself (not from the Bug
Description, or the result of a terminal command), could you please
provide the full monitor manufacturer and model?
2) Regarding how you have the monitor connected, is this straight into
the computer's miniDP cable, mDP to
** Tags removed: bios-outdated-2.41
** Tags added: bios-outdated-2.49
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1552040
Title:
[Lenovo ThinkPad T440s] Laptop sometimes
James (jamestheawesomedude), it will help immensely if you use the computer the
problem is reproducible with, file a new report with Ubuntu by first ensuring
the package xdiagnose is installed, and click the Yes button for attaching
additional debugging information after running the following
Mario Costa:
A) Could you please provide the result of the following terminal command:
sudo cat /var/lib/whoopsie/whoopsie-id
B) To see if this is already resolved in Ubuntu, could you please test
http://cdimage.ubuntu.com/daily-live/current/ and advise to the result?
** Changed in: xorg
** Changed in: xorg (Ubuntu)
Status: Incomplete => 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/1771539
Title:
Xorg crash
To manage notifications about this bug go to:
1 - 100 of 10660 matches
Mail list logo
