*** This bug is a duplicate of bug 1828697 ***
https://bugs.launchpad.net/bugs/1828697
OK, since we're back to just the flicker issue then we should use bug
1828697. Because it is older, but also because it is not confused by the
tearing issue mentioned here.
** This bug has been marked a dup
P.S. This might also be a security issue. I've noticed that the frame
that's stuck inside the flicker reappears when I shut down / restart my
computer. That's a potential security issue because you might not be the
only person using your computer and all of a sudden this errant frame of
video pops
Launchpad has imported 22 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=1725499.
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
@vanvugt The tearing's a nonissue now so it makes sense to refashion
this report to deal with the flicker only. I'd really rather not shirk
this report with the traction it's received.
Re #19, just the one screen. But that makes no difference either. I have
a multiple screen setup on a different c
Launchpad has imported 20 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=101229.
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
[Expired for llvm-toolchain-7 (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: llvm-toolchain-7 (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to llvm-toolchain-7 in Ubuntu.
htt
[Expired for llvm-toolchain-7 (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: llvm-toolchain-7 (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to llvm-toolchain-7 in Ubuntu.
htt
Do you mean the screen doesn't light up, or the touchpad is
unresponsive?
Certainly the attached files suggest the second screen is not seen as
connected or powered on.
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)
** Also affects: linux (Ubuntu)
Importance: Undecided
Statu
This change was made by a bot.
** Changed in: linux (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/1846090
Title:
Asus UX580GD (GDX1505:00 27C6:0
** Bug watch added: Red Hat Bugzilla #1725499
https://bugzilla.redhat.com/show_bug.cgi?id=1725499
** Also affects: xserver-xorg-video-ati (Fedora) via
https://bugzilla.redhat.com/show_bug.cgi?id=1725499
Importance: Unknown
Status: Unknown
** Also affects: xserver-xorg-video-ati (U
Wait a minute... How many monitors are you running?
Just one or multiple?
** Also affects: xorg-server (Ubuntu)
Importance: Undecided
Status: New
** Changed in: xorg-server (Ubuntu)
Status: New => Incomplete
** Changed in: mpv (Ubuntu)
Status: Confirmed => Incomplete
**
To be absolutely sure you would need to:
1. Convert the display's EDID into binary from hex:
00004c2d09050100
30120103801009780aee91a3544c9926
0f5054bdef80714f8100814081809500
950fb3000101023a801871382d40582c
** Changed in: nouveau
Status: Confirmed => Unknown
** Bug watch added: gitlab.freedesktop.org/mesa/drm/issues #12
https://gitlab.freedesktop.org/mesa/drm/issues/12
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libdrm in Ubuntu.
http
-- 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/mesa/drm/issue
*** This bug is a duplicate of bug 1843987 ***
https://bugs.launchpad.net/bugs/1843987
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1843987, so is being marked as such.
This bug was fixed in the package linux - 4.15.0-65.74
---
linux (4.15.0-65.74) bionic; urgency=medium
* bionic/linux: 4.15.0-65.74 -proposed tracker (LP: #1844403)
* arm64: large modules fail to load (LP: #1841109)
- arm64/kernel: kaslr: reduce module randomization range to
Public bug reported:
Ubuntu does not support asus zenbook pro UX580GD screenpad (touchpad and
screen - all in one)
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21
Uname: Linux 5.0.0-29-generic x86_64
Nonf
Public bug reported:
E: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 3989
(apt) - open (11: Die Ressource ist zur Zeit nicht verfügbar)
N: Be aware that removing the lock file is not a solution and may break your
system.
E: Unable to acquire the dpkg frontend lock (/var/
best to close then
** Changed in: mesa (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1503426
Title:
package libgl1-mesa-glx 10.1.3-0ubuntu0.5 faile
Setting up libegl1-mesa:amd64 (17.2.8-0ubuntu0~16.04.1) ...
update-alternatives: error: cannot stat file
'/usr/bin/java/jdk-9.0.4/bin/jar': Not a directory
dpkg: error processing package libegl1-mesa:amd64 (--configure):
subprocess installed post-installation script returned error exit status
still the same with 18.04.3/19.04?
** Package changed: mesa (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bug
closing as it's reported to be caused by overheating
** Changed in: mesa (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/881526
Title:
AMD graphics har
*** This bug is a duplicate of bug 1753796 ***
https://bugs.launchpad.net/bugs/1753796
** This bug has been marked a duplicate of bug 1753796
Conflict between libglx-mesa and nvidia-390 on Ubuntu 18.04 (pre-release)
--
You received this bug notification because you are a member of Ubuntu-
Public bug reported:
1. llvm 9 has been released, but mesa in the repo still uses llvm 8.
2. llvm 9 bitcode libs for OpenCL cause llvm-8-based mesa to fail because their
file format has changed
3. There was a bug in llvm-8-based mesa in disco that caused the OpenCL
compiler to hang on the kernel
https://askubuntu.com/q/1177674/21005
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
https://bugs.launchpad.net/bugs/958891
Title:
no tty, only blank screen with nvidia driver
To manage notifications about
Can you try the 430 driver from this PPA, please? (I have uploaded a fix
for 18.04 and for 19.10)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
https://bugs.launchpad.net/bugs/1836630
Title:
System76 Oryx P
https://launchpad.net/~oem-solutions-group/+archive/ubuntu/nvidia-
driver-staging
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
https://bugs.launchpad.net/bugs/1836630
Title:
System76 Oryx Pro (oryp5) with
I have the same problem with Xubuntu 18.04. Bug #1811402
The system boots using EFI v1.10 by Apple, but Grub is used, too. I wonder, how
to switch to BIOS boot?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
h
How can I check if the hardware is really sending faulty data or if it
is just incorrectly parsed?
** Also affects: xrandr (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xrandr in Ubuntu.
htt
atomic modesetting is disabled in eoan, btw
--
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/1844934
Title:
screen jitter after long idle
To manage notifications about this bug go to:
http
Actually, the XorgLog.txt shows more definite problems:
[181434.889] (WW) modeset(0): flip queue failed: Device or resource busy
[181434.889] (WW) modeset(0): Page flip failed: Device or resource busy
[181434.889] (EE) modeset(0): present flip failed
[181434.989] (WW) modeset(0): flip queue failed
Or it could be the framebuffer compression or other power saving things.
Since the last relevant kernel message is:
[180893.945295] [drm] Reducing the compressed framebuffer size. This may
lead to less power savings than a non-reduced-size. Try to increase
stolen memory size if available in BIOS.
Yes the kernel log (CurrentDmesg.txt) suggests a disk is faulty so you
should replace that before doing anything else...
Then if the screen flickering persists please attach a video of the
problem here so we can better understand what you mean.
** Package changed: xorg (Ubuntu) => ubuntu
--
You
its problem with vlc as well; I'm neither using wayland.
--
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/1697373
Title:
[screensaver] Screen blanks during video playback in Chrome and
Fi
The kernel log suggests the nouveau kernel driver is having trouble:
[ 5703.539644] nouveau :00:0d.0: bus: MMIO write of 052a0001 FAULT at 00b000
[ 5704.875835] nouveau :00:0d.0: bus: MMIO write of 05270001 FAULT at 00b010
[ 5705.738769] nouveau :00:0d.0: bus: MMIO write of 05270001 FA
https://bugs.launchpad.net/ubuntu/+source/libxkbcommon/+bug/1772512/comments/6
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libxkbcommon in Ubuntu.
https://bugs.launchpad.net/bugs/1772512
Title:
Unable to install i386 and amd64 arch at the
This looks like another atomic mode setting problem. To test this
theory, please try 'Ubuntu on Wayland' and tell us if it avoids the
jitter.
If so, then this Xorg fix from Intel is probably what we want to keep an eye on:
https://gitlab.freedesktop.org/xorg/xserver/merge_requests/180
I keep seei
It appears the freeze was due to a crash mentioned in your kernel:
[ 551.339814] gnome-shell[1798]: segfault at 4400 ip 7f29b593b9e1 sp
7ffe617a1710 error 4 in libmutter-2.so.0.0.0[7f29b58b+158000]
[ 551.339837] Code: 00 4c 89 e2 48 89 ee 48 89 df e8 fa 04 fc ff 85 c0 74 5e
4c 8b 7
** Package changed: xorg (Ubuntu) => wine (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/1845373
Title:
Problem with wine
To manage notifications about this bug go to:
https://bugs.lau
Could you describe the problem in more detail?
Can you please attach a photo of the problem?
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xor
Please open a terminal and run 'top' in it to find out if any process is
hogging the CPU when this happens.
Tip: DON'T run gnome-system-monitor because it uses too many resources
itself :)
If no offending process is found then the next thing to check is for
over-aggressive power management:
1.
41 matches
Mail list logo
