[39.611] (II) AIGLX: Screen 0 is not DRI2 capable
[39.611] (EE) AIGLX: reverting to software rendering
16.04 is just old and you're not getting any (gfx) updates there anymore
at this point
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed
No they're not really. That's just recovery mode, required to log this
bug.
--
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/1901342
Title:
Xorg sessions fail to start on Intel Core 2
you're using 'nomodeset' boot option which disables things, don't do
that
--
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/1901342
Title:
Xorg sessions fail to start on Intel Core 2 T5800:
This sounds like either bug 1896110 or bug 1874578. Do you think?
** Summary changed:
- Xorg freeze
+ Freeze
** Package changed: xorg (Ubuntu) => gnome-shell-extension-ubuntu-dock
(Ubuntu)
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
Status: New => Incomplete
--
You
OK, clarified somewhat now. This bug is back to being about just "no
screens found".
** Summary changed:
- Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError()
from dix_main()
+ Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError("no
screens found")
It looks like bug 1897530 might cover this but it's unclear. The fix for
that is only in Ubuntu 20.10 so far.
--
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/1791981
Title:
[nvidia] X
** Summary changed:
- Xorg crashed with SIGABRT in OsAbort() from AbortServer() from
FatalError("EnterVT failed for screen ...") from xf86VTEnter() from
systemd_logind_vtenter()
+ Xorg crashed with SIGABRT in OsAbort() from AbortServer() from
FatalError("EnterVT failed for screen %d\n") from
There's not enough information here to tell which FatalError this is.
** This bug is no longer a duplicate of bug 1543192
Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError()
from dix_main()
** Changed in: xorg-server (Ubuntu)
Status: New => Incomplete
--
You
I can't see any evidence of which Xorg crash this is.
** This bug is no longer a duplicate of bug 1543192
Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError()
from dix_main()
** Changed in: xorg-server (Ubuntu)
Status: New => Incomplete
--
You received this
I can't tell *which* FatalError this is.
** This bug is no longer a duplicate of bug 1543192
Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError()
from dix_main()
** Changed in: xorg-server (Ubuntu)
Status: New => Incomplete
--
You received this bug
*** This bug is a duplicate of bug 1543192 ***
https://bugs.launchpad.net/bugs/1543192
** Summary changed:
- Xorg crashed with SIGABRT in OsAbort()
+ Xorg crashed with SIGABRT in OsAbort() from ?? from FatalError("no screens
found")
--
You received this bug notification because you are a
There's not enough information here to tell which FatalError this is.
** This bug is no longer a duplicate of bug 1543192
Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError()
from dix_main()
** Changed in: xorg-server (Ubuntu)
Status: New => Incomplete
--
You
I think this is the wrong bug for all of those duplicates. There's no
evidence of either of those messages here. I'll see if I can split this
into other bugs...
** Summary changed:
- Xorg crashed with SIGABRT in OsAbort() from AbortServer() from
FatalError("EnterVT failed for gpu screen %d\n")
*** This bug is a duplicate of bug 1813897 ***
https://bugs.launchpad.net/bugs/1813897
** This bug is no longer a duplicate of bug 1543192
Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError()
from dix_main()
** Summary changed:
- Xorg crashed with SIGABRT in
Ubuntu 14.04 reached end of standard support in April 2019:
https://wiki.ubuntu.com/Releases
If you would like to continue with free support then please update to a
newer Ubuntu version and tell us if the problem still occurs.
If you would like to continue with Ubuntu 14.04 then there is a
Thank you for reporting this bug to Ubuntu.
Ubuntu GNOME 14.04 (trusty) reached end-of-life on April 28, 2017
https://wiki.ubuntu.com/TrustyTahr/ReleaseNotes/UbuntuGNOME#Support
https://lists.ubuntu.com/archives/ubuntu-gnome/2017-March/004211.html
We appreciate that this bug may be old and you
*** This bug is a duplicate of bug 1791981 ***
https://bugs.launchpad.net/bugs/1791981
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 1791981, so it is being marked as such. Please
** Summary changed:
- X Server session crash for "No space left on device"
+ X Server session crash with "No space left on device" and then "EnterVT
failed for gpu screen 0"
** Summary changed:
- X Server session crash with "No space left on device" and then "EnterVT
failed for gpu screen 0"
It appears the Xorg radeon driver is working. It's only 3D that's not
working so that's Mesa.
** Summary changed:
- No hardware aceleration
+ [radeon] No hardware aceleration
** Summary changed:
- [radeon] No hardware aceleration
+ [radeon] No hardware acceleration
** Tags added: radeon
**
Yep, the detailed mode 2560x1440 is in the EDID returned by the monitor:
Standard Timings: none
Detailed mode: Clock 241.500 MHz, 598 mm x 336 mm
2560 2608 2640 2720 ( 48 32 80)
1440 1443 1448 1481 ( 3 5 33)
+hsync -vsync
VertFreq:
I would like to check to see if the problem is occurring in the kernel
and not just in Xorg. Please run:
grep . /sys/class/drm/*/modes > modes.txt
and then attach the resulting text file here.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
** Changed in: gdm3 (Ubuntu)
Status: Incomplete => New
** Changed in: mutter (Ubuntu)
Status: Incomplete => New
** Changed in: xorg-server (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
** No longer affects: xorg-server (Ubuntu)
--
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/1550779
Title:
Black screen flickering and [drm:intel_cpu_fifo_underrun_irq_handler
[i915]]
Yes - "after login" means after I have successfully entered my password.
Also, I have not been able to locate the 'Ubuntu on Wayland' selection.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
** 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/1901736
Title:
Xorg freeze
To manage notifications about this bug go to:
You have been subscribed to a public bug:
Most of the time Ubuntu boots the dock seems to freeze and not load any
icons, sometimes for up to a minute. When this happens the dock will not
appear when any window is maximized.
Once in a while Ubuntu loads without a problem. The dock loads
The standalone patch #217 is working for MSFT0001:00 04F3:3140 but isn't
working perfectly for MSFT0001:00 06CB:7F28. The MSFT0001:00 06CB:7F28
touchpad frequently locks into scroll mode when using multitouch
gestures.
--
You received this bug notification because you are a member of Ubuntu-X,
Daniel, this seems consistent: so long as I don't load the Dropbox app,
I haven't seen the suspend. I don't know if this is the cause but
regardless the Dropbox app may help in reproducing this issue? Thanks...
--
You received this bug notification because you are a member of Ubuntu-X,
which is
Hello John, or anyone else affected,
Accepted mutter into groovy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/mutter/3.38.1-2ubuntu1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** 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/1901694
Title:
No hardware aceleration
To manage notifications about this bug go to:
You have been subscribed to a public bug:
Computer HP EliteBook 8460p. It uses hybrid graphics card. Processor Intel Core
i5-2520M CPU @ 2.50GHz × 4; 2nd generation. The system only runs well with
llvmpipe (LLVM 6.0, 256 bits) graphic software, AMD Caicos sometimes it's
charged too, but the
** Changed in: mutter (Ubuntu Focal)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
--
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/1855757
Title:
[nvidia]
Sounds somewhat similar to bug #1879893 but it appears that is supposed
to be fixed now.
** Description changed:
Steps to reproduce:
- - Boot docked laptop (i.e. lid closed, external monitors connected, USB
keyboard plugged in)
- - Log in, click desktop menu item "Power off / logout ->
Public bug reported:
Steps to reproduce:
- Boot docked laptop (i.e. lid closed, external monitors connected, USB
keyboard plugged in)
- Log in, click desktop menu item "Power off / logout -> suspend"
- Laptop will suspend
- Press key on USB keyboard to resume
- Resume fails - external
** Attachment added: "journal"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1901695/+attachment/5427808/+files/journal
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
You have been subscribed to a public bug:
Steps to reproduce:
- Boot docked laptop (i.e. lid closed, external monitors connected, USB
keyboard plugged in)
- Log in, click desktop menu item "Power off / logout -> suspend"
- Laptop will suspend
- Press key on USB keyboard to resume
-
apport information
** Attachment added: "DpkgLog.txt"
https://bugs.launchpad.net/bugs/1901470/+attachment/5427742/+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: "nvidia-settings.txt"
https://bugs.launchpad.net/bugs/1901470/+attachment/5427764/+files/nvidia-settings.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: "xdpyinfo.txt"
https://bugs.launchpad.net/bugs/1901470/+attachment/5427765/+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: "acpidump.txt"
https://bugs.launchpad.net/bugs/1901470/+attachment/5427763/+files/acpidump.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/1901470/+attachment/5427761/+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/1901470
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1901470/+attachment/5427757/+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/1901470
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1901470/+attachment/5427755/+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: "XorgLog.txt"
https://bugs.launchpad.net/bugs/1901470/+attachment/5427759/+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/1901470/+attachment/5427760/+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: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1901470/+attachment/5427754/+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: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1901470/+attachment/5427752/+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/1901470/+attachment/5427750/+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: "MonitorsUser.xml.txt"
https://bugs.launchpad.net/bugs/1901470/+attachment/5427748/+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
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1901470/+attachment/5427753/+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: "NvidiaBugReportLog.txt"
https://bugs.launchpad.net/bugs/1901470/+attachment/5427749/+files/NvidiaBugReportLog.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: "Lspci.txt"
https://bugs.launchpad.net/bugs/1901470/+attachment/5427743/+files/Lspci.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/1901470
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1901470/+attachment/5427747/+files/Lsusb-v.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: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1901470/+attachment/5427745/+files/Lsusb.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/1901470
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1901470/+attachment/5427746/+files/Lsusb-t.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: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1901470/+attachment/5427744/+files/Lspci-vt.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:
The PG278QR monitor supports 2560x1440. After installing Ubuntu 20.4,
the max resolution presented in the Settings app is 1920x1080, and this
resolution is the one that it uses. Switching between the
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1901470/+attachment/5427741/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
I initially saw flickering with Wayland, so i switched to Xorg to check
if it happens also there... and it happens.
--
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/1550779
Title:
Black
** Tags added: nvidia
** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-450
(Ubuntu)
** Also affects: mutter (Ubuntu)
Importance: Undecided
Status: New
** Changed in: mutter (Ubuntu)
Importance: Undecided => High
** Changed in: nvidia-graphics-drivers-450 (Ubuntu)
It looks like the Nvidia driver also is not working for you... Try
removing and reinstalling the Nvidia driver via the 'Additional Drivers'
app.
Failing that, I think this should be merged into one of: bug 1880739,
bug 1890957
--
You received this bug notification because you are a member of
Your kernel log mentions:
[ 618.131916] i915 :00:02.0: [drm] *ERROR* Atomic update failure on
pipe B (start=36634 end=36635) time 217 us, min 1431, max 1439, scanline
start 1421, end 1440
which I think can only happen in Xorg sessions.
Try selecting 'Ubuntu on Wayland' from the login
It also looks like the BIOS is hiding the Intel GPU, which your old Xorg
logs seem to suggest is required to drive the screen, and night light.
Please look in your BIOS to try and re-enable the integrated Intel GPU.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
63 matches
Mail list logo
