Public bug reported:
When using my AMD Radeon X1300 card, if the screen turns off due to
inactivity, it cannot be woken up by moving the mouse or by hitting a
key.
When I restart the display manager via ssh with another computer, the
screen then comes to life again and I can log back in.
There i
OK. Created Bug #1821505
--
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/1577170
Title:
screen cannot be turned back on after being switched off after some
time of inactivity
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 t
** Also affects: intel-vaapi-driver (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to intel-vaapi-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1821525
Title:
totem assert failure: totem:
** Summary changed:
- totem assert failure: totem: gen9_mfd.c:649:
gen9_hcpd_get_reference_picture_frame_id: La declaración `0' no se cumple.
+ totem assert failure: totem: totem: gen9_mfd.c:649:
gen9_hcpd_get_reference_picture_frame_id: Assertion `0' failed.
--
You received this bug notificat
1) This has never been an issue, until upgrade to 16.04 LTS.
2)
a) These are not workarounds, this are just ways of manually starting the
screen blank, without triggering the bug. If you let the screen blank
automatically, bug will still trigger. And once the bug is triggered, only
restart of
Submitted under
https://gitlab.freedesktop.org/libinput/libinput/issues/256
** Bug watch added: gitlab.freedesktop.org/libinput/libinput/issues #256
https://gitlab.freedesktop.org/libinput/libinput/issues/256
--
You received this bug notification because you are a member of Ubuntu-X,
which is
** Description changed:
- https://gitlab.gnome.org/GNOME/totem/issues/315
+ https://bugzilla.freedesktop.org/show_bug.cgi?id=110232
+ https://gitlab.gnome.org/GNOME/totem/issues/315 (Not totem)
---
Watching movie 4k.
ProblemType: Crash
DistroRelease: Ubuntu 19.04
Package: totem
** Description changed:
+ https://github.com/intel/intel-vaapi-driver/issues/451
https://bugzilla.freedesktop.org/show_bug.cgi?id=110232
https://gitlab.gnome.org/GNOME/totem/issues/315 (No totem)
---
Watching movie 4k.
ProblemType: Crash
DistroRelease: Ubuntu 19.04
Package:
** Description changed:
https://github.com/intel/intel-vaapi-driver/issues/451
https://bugzilla.freedesktop.org/show_bug.cgi?id=110232
https://gitlab.gnome.org/GNOME/totem/issues/315 (No totem)
---
- Watching movie 4k.
+ Watching movie 4k, forward and back.
+
ProblemType: Crash
Public bug reported:
Booting very new laptop hardware (ASUS Zenbook UX431FA) from 18.04 usb
install (also 18.10, also 19.04 daily) leads to black screen. Adding
"nomodeset" to kernel boot parameter gives 800x600 video only and
permits installing OS to disk. Applying updates and hardware enablement
** Description changed:
Booting very new laptop hardware (ASUS Zenbook UX431FA) from 18.04 usb
install (also 18.10, also 19.04 daily) leads to black screen. Adding
"nomodeset" to kernel boot parameter gives 800x600 video only and
permits installing OS to disk. Applying updates and hardware
A simple workaround (that worked for me at least):
sudo apt install slick-greeter
printf '[Seat:*]\ngreeter-session=slick-greeter\n' | sudo tee -a
/etc/lightdm/lightdm.conf
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
** Also affects: libinput via
https://gitlab.freedesktop.org/libinput/libinput/issues/256
Importance: Unknown
Status: Unknown
** Changed in: libinput (Ubuntu)
Status: Incomplete => New
** Changed in: xserver-xorg-input-evdev (Ubuntu)
Status: Incomplete => New
--
You r
** Summary changed:
- Screen remains black/off when the system is resumed from sleep
+ Screen remains black/off when the system is resumed from sleep [(EE)
modeset(0): present flip failed]
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-se
** Changed in: wayland (Ubuntu)
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to wayland in Ubuntu.
https://bugs.launchpad.net/bugs/1821318
Title:
FFe: Wayland 1.17 for disco
To manage notifications about
*** This bug is a duplicate of bug 1821385 ***
https://bugs.launchpad.net/bugs/1821385
Public bug reported:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
xorg-server. This problem was most recently seen with package version
2:1.20.4-1ubuntu2, the problem pag
*** This bug is a duplicate of bug 1821385 ***
https://bugs.launchpad.net/bugs/1821385
** This bug has been marked a duplicate of bug 1821385
Xwayland crashed with SIGABRT in wl_proxy_destroy()
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed
It appears Xorg can't open the GPU device:
[ 125.196] (EE) [drm] Failed to open DRM device for pci::01:00.0: -19
[ 125.196] (EE) open /dev/dri/card0: No such file or directory
[ 125.196] (WW) Falling back to old probe method for modesetting
[ 125.196] (EE) open /dev/dri/card0: No such
Tracking in
https://errors.ubuntu.com/problem/008c7bd0fdc996890cce5f67e5f0214f280aefd8
** Bug watch added: gitlab.freedesktop.org/xorg/xserver/issues #672
https://gitlab.freedesktop.org/xorg/xserver/issues/672
** Also affects: xorg-server via
https://gitlab.freedesktop.org/xorg/xserver/issu
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/1821
** Summary changed:
- Xwayland crashed with SIGABRT in wl_proxy_destroy()
+ Xwayland crashed with SIGABRT in wl_proxy_destroy() from
wl_callback_destroy() from xwl_present_sync_callback() from ffi_call_unix64()
--
You received this bug notification because you are a member of Ubuntu-X,
which is
*** This bug is a duplicate of bug 1821397 ***
https://bugs.launchpad.net/bugs/1821397
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 1821397, so it is being marked as such. Please look
Can you please provide a screenshot or photo of the error you are
seeing?
Also, I notice your kernel keeps logging:
[4.513233] nvidia-modeset: WARNING: GPU:0: Unable to read EDID for
display device DVI-I-0
which means you might need to try a different DVI cable if not a
different monitor to
** Tags added: radeon
** Summary changed:
- screen cannot be turned back on after some time of inactivity
+ [radeon] screen cannot be turned back on after some time of inactivity
** Package changed: xorg (Ubuntu) => xserver-xorg-video-ati (Ubuntu)
** Changed in: xserver-xorg-video-ati (Ubuntu)
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Package changed: linux (Ubuntu) => linux-hwe (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-
** Changed in: xorg-server
Status: Unknown => New
--
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/1821385
Title:
Xwayland crashed with SIGABRT in wl_proxy_destroy() from
wl_callba
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v5.1-rc2 kernel [0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not f
Thanks for your help.
Unfortunately, no change after installing v5.1-rc2: Still stuck in
800x600 after booting with nomodeset kernel option.
Added kernel-bug-exists-upstream and marked confirmed.
dmesg output attached.
** Attachment added: "dmesg"
https://bugs.launchpad.net/ubuntu/+source/x
Also: booting without nomodeset kernel option for v5.1-rc2 kernel leads
to black screen, just as before. At that point the system cannot even be
switched to text console with ctrl-alt-Fn.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-serve
** Package changed: xorg (Ubuntu) => 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/1821508
Title:
there is a lagging while i am accessing the software or browing
To manage notifications
Based on a lead from an Arch Linux blog post, I tried adding the i915
module to the initramfs. This could possibly lead to earlier
initialization of the graphics device and it also seems consistent with
the DragonFlyBSD "probe early" patch I linked to in my initial bug
report which may have fixed t
33 matches
Mail list logo
