I thought I had reproduced this bug in the past when doing radeon
testing. And my radeon testing does not involve AMDGPU or PPAs. Just
vanilla Ubuntu on radeon was enough to reproduce it.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in
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
Or as one user posted, the official AMDGPU Pro package, which also
enables 10bpc.
--
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/1767312
Title:
[radeon] Totem with gstreamer1.0-vaapi and Xorg:
Can you please attach a photo of the problem, and any other information?
** 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 xorg in Ubuntu.
This bug can only occur if 10bpc is enabled. There is no other
possibility. It is clearly a colorspace mismatch between VAAPI and the
decode target surface. If disabling 10bpc happens in Ubuntu Mesa
packages, then it is clearly someone using unofficial package builds of
Mesa which have 10bpc
Public bug reported:
při startu píše chyba systémového souboru
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
Uname: Linux 4.15.0-46-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
It appears one of your hard disks is failing and causing long delays in
the kernel:
[ 1137.804251] ata3: exception Emask 0x10 SAct 0x0 SErr 0x400 action 0xe
frozen
[ 1137.804258] ata3: irq_stat 0x0040, connection status changed
[ 1137.804264] ata3: SError: { DevExch }
[ 1137.804273]
Please do attach a photo or video of the problem ASAP.
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)
** Changed in: xorg-server (Ubuntu)
Status: Confirmed => Incomplete
** Tags added: nouveau
** Summary changed:
- Scrolling screen flicker, especially on default Ubuntu lock
Oh. gen9_mfd.c and gen9_hcpd_get_reference_picture_frame_id are from
intel-vaapi-driver.
As a workaround, please try:
sudo apt remove i965-va-driver
** Also affects: intel-vaapi-driver (Ubuntu)
Importance: Undecided
Status: New
** Changed in: totem (Ubuntu)
Status:
** 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/1818386
Title:
Deb Packages not installing web browsers
To manage notifications about this bug go to:
** Summary changed:
- Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError()
from xf86VTEnter() from WakeupHandler()
+ Xorg crashed with SIGABRT in OsAbort() from AbortServer() from
FatalError("EnterVT failed for screen %d) from xf86VTEnter() from
WakeupHandler()
**
*** This bug is a duplicate of bug 1421808 ***
https://bugs.launchpad.net/bugs/1421808
** This bug is no longer a duplicate of private bug 1819008
** This bug has been marked a duplicate of bug 1421808
Xorg crashed with SIGABRT in OsAbort() from AbortServer() from
FatalError("EnterVT
** Summary changed:
- Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError()
from xf86VTEnter() from xf86VTSwitch()
+ Xorg crashed with SIGABRT in OsAbort() from AbortServer() from
FatalError("EnterVT failed for screen %d\n") from xf86VTEnter() from
xf86VTSwitch()
--
You
*** This bug is a duplicate of bug 1819008 ***
https://bugs.launchpad.net/bugs/1819008
** This bug has been marked a duplicate of private bug 1819008
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
Also affects me, after idling for some time computer is taking a very
long time to come back to life.
AMD Ryzen 7 1700
AMD RX550
[ 6380.343388] [drm:generic_reg_wait [amdgpu]] *ERROR* REG_WAIT timeout 10us *
3000 tries - dce110_stream_encoder_dp_blank line:927
[ 6380.343515] WARNING: CPU: 1
*** This bug is a duplicate of bug 1818972 ***
https://bugs.launchpad.net/bugs/1818972
** This bug has been marked a duplicate of bug 1818972
[regression] GLX is missing. gnome-shell visible latency is very high with
Xorg 2:1.20.4-1ubuntu1
--
You received this bug notification because
Bug #1819077
** Tags removed: verification-needed-xenial
** Tags added: verification-failed-xenial
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-304 in Ubuntu.
https://bugs.launchpad.net/bugs/1573508
Title:
Hello.
I have the same laptop.. It malfunctions all the time. The touchpad has to be
used slowly or it freezes. and I am unable to drag and select/move text..
I can see there was a simillar bug to this..
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1048258
Some interesting information
Hello. I am running the same os, on the same laptop.. On my case besides having
the move the mouse slowly it prevents me from clicking and dragging.. or from
selecting text..
Any more information that you need
?
--
You received this bug notification because you are a member of Ubuntu-X,
which
can confirm that downgrading xserver fix the issue, looks like build
issue. Now i know why it's called bleeding edge.
--
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/1819056
Title:
AIGLX error
After spending some more time with this, I can confirm that this is
definitely a regression. Both nouveau and the old bbswitch based method
in 16.04 were able to power off the nvidia card successfully when not in
use. The current implementation of prime-select in 18.04 doesn't do
that. It may be
Downgrading xserver-xorg-core 2:1.20.4-1ubuntu1 (from disco-proposed) ->
2:1.20.3-1ubuntu1 fixed this issue for me. So probably the bug is in
xserver-xorg-core package.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
Similar situation in link:
https://github.com/LibreELEC/LibreELEC.tv/pull/2769
--
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/1819056
Title:
AIGLX error with i965 dri
To manage notifications
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mesa (Ubuntu)
Status: New => Confirmed
--
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/1819056
Title:
Thank you for taking the time to verify this stable release fix. We
have noticed that you have used the verification-done tag for marking
the bug as verified and would like to point out that due to a recent
change in SRU bug verification policy fixes now have to be marked with
per-release tags
$ dpkg -l | grep mesa
ii libegl-mesa0:amd6418.3.4-2ubuntu1
amd64free implementation of the EGL API --
Mesa vendor library
ii libegl1-mesa:amd6418.3.4-2ubuntu1
Public bug reported:
Those lines are most importat:
[10.707] (EE) AIGLX error: dlopen of
/usr//usr/lib/x86_64-linux-gnu/dri/i965_dri.so failed
(/usr//usr/lib/x86_64-linux-gnu/dri/i965_dri.so: cannot open shared object
file: No such file or directory)
[10.707] (EE) AIGLX error: unable
Thanks for your comments. This does not appear to be a bug report and we
are closing it. We appreciate the difficulties you are facing, but it
would make more sense to raise your question in the support tracker.
Please visit https://answers.launchpad.net/ubuntu/+addquestion
** Information type
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
Hello khanpak...@gmail.com, or anyone else affected,
Accepted nvidia-graphics-drivers-304 into trusty-proposed. The package
will build now and be available at https://launchpad.net/ubuntu/+source
/nvidia-graphics-drivers-304/304.135-0ubuntu0.14.04.2 in a few hours,
and then in the -proposed
Hello khanpak...@gmail.com, or anyone else affected,
Accepted nvidia-graphics-drivers-340 into trusty-proposed. The package
will build now and be available at https://launchpad.net/ubuntu/+source
/nvidia-graphics-drivers-340/340.107-0ubuntu0.14.04.1 in a few hours,
and then in the -proposed
Hello khanpak...@gmail.com, or anyone else affected,
Accepted nvidia-graphics-drivers-384 into trusty-proposed. The package
will build now and be available at https://launchpad.net/ubuntu/+source
/nvidia-graphics-drivers-384/384.130-0ubuntu0.14.04.2 in a few hours,
and then in the -proposed
Public bug reported:
My screen is experiencing a weird "scrolling" flicker, especially while
displaying blue, indigo, and violet hues/colors, such as on the default
Ubuntu 18.10 (x64 Desktop) lock screen. The screen flicker scrolls up
and down, with the brightest part of the flicker being towards
Hello khanpak...@gmail.com, or anyone else affected,
Accepted nvidia-graphics-drivers-384 into xenial-proposed. The package
will build now and be available at https://launchpad.net/ubuntu/+source
/nvidia-graphics-drivers-384/384.130-0ubuntu0.16.04.2 in a few hours,
and then in the -proposed
Hello khanpak...@gmail.com, or anyone else affected,
Accepted nvidia-graphics-drivers-304 into xenial-proposed. The package
will build now and be available at https://launchpad.net/ubuntu/+source
/nvidia-graphics-drivers-304/304.135-0ubuntu0.16.04.3 in a few hours,
and then in the -proposed
assuming this is fixed in a later release, but if not, feel free to file
a new bug
** Package changed: wacom-tools (Ubuntu) => xf86-input-wacom (Ubuntu)
** Changed in: xf86-input-wacom (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member
do you still have this bug with 18.04 or newer?
** Package changed: wacom-tools (Ubuntu) => xf86-input-wacom (Ubuntu)
** Changed in: xf86-input-wacom (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
Do you have a better solution? If I change the HDMI display to
-2560x-360 it doesn't work either. Now there is space to the bottom and
right of the laptop display (captured in screenshot) and the external
monitor is not actually at that position either, it's more like
-2560x-180 (not sure if
** Changed in: xorg-server (Ubuntu)
Status: New => In Progress
** Changed in: xorg-server (Ubuntu)
Assignee: (unassigned) => Timo Aaltonen (tjaalton)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
Why look for -rc? if there is no problem only in the kernel version
4.18. (10, 11, 12), in all other kernel versions 4.18 there is a bug
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-amdgpu in Ubuntu.
Thanks for the advice. I thought that the crash report would be attached
automatically when I do ubuntu-bug command-name. Anyway, the new bug is
#1819008.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
Tagged bionic-failed, what sort of testing was done? Did we get the
systemd change? Or is the regression described earlier in the discussion
is still problematic?
** Tags removed: verification-done-bionic
** Tags added: verification-failed-bionic
--
You received this bug notification because
This bug was fixed in the package xkeyboard-config -
2.23.1-1ubuntu1.18.10.1
---
xkeyboard-config (2.23.1-1ubuntu1.18.10.1) cosmic; urgency=medium
* debian/patch/git_airplane_key.patch:
- define the keys needed for airplane mode toggling from the desktop
(lp: #1740894)
The verification of the Stable Release Update for xkeyboard-config has
completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
** Description changed:
[Impact]
GLX is missing. gnome-shell visible latency is very high with Xorg
2:1.20.4-1ubuntu1. And reinstalling the previous version
(2:1.20.3-1ubuntu1) seems to fix it.
[Test Case]
+
+ $ glxinfo
+
+ Expect: Lots of information
+ Observed: An error
+
+ -
And as Timo just pointed out:
[46.827] (EE) AIGLX error: dlopen of
/usr//usr/lib/x86_64-linux-gnu/dri/i965_dri.so failed
(/usr//usr/lib/x86_64-linux-gnu/dri/i965_dri.so: cannot open shared object
file: No such file or directory)
[46.827] (EE) AIGLX error: unable to load driver i965
[
** Tags added: block-proposed
--
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/1818972
Title:
[regression] GLX is missing. gnome-shell visible latency is very high
with Xorg
Found the problem in mutter:
CLUTTER_FEATURE_SWAP_EVENTS is missing because
COGL_WINSYS_FEATURE_SWAP_BUFFERS_EVENT is missing because
cogl-winsys-glx isn't being used because
xorg 2:1.20.4-1ubuntu1 is missing/has broken GLX support...
$ glxinfo
name of display: :4
Error: couldn't find RGB GLX
*** This bug is a duplicate of bug 1813162 ***
https://bugs.launchpad.net/bugs/1813162
** This bug has been marked a duplicate of bug 1813162
package libomp5-7 1:7.0.1-4 failed to install/upgrade: trying to overwrite
shared '/usr/lib/llvm-7/lib/libomp-7.so.5', which is different from
this is available on ppa:canonical-x/x-staging
though it's built with proposed enabled, so could need bits from there
--
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/1818516
Title:
FFe: Mesa
@vanvugt, I installed nvidia-driver-390, and now the second display
doesn't work (again). I have removed it, but the damage persists. I'll
see what I can do re disabling in BIOS.
@kaihengfeng, I'd like to test the mainline kernel, but could you give
me a couple of lines on how? I'm guessing I
Public bug reported:
[Impact]
gnome-shell visible latency is very high with Xorg 2:1.20.4-1ubuntu1.
And reinstalling the previous version (2:1.20.3-1ubuntu1) seems to fix
it.
[Test Case]
1. Log into a gnome-shell Xorg session ("Ubuntu").
2. Drag a window around in circles by its titlebar.
Which DRI driver are you using? 10bpc is disabled for every gallium
driver (like radeonsi) and intel, so I don't understand how changing the
drirc would affect at all.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
** Changed in: xserver-xorg-video-vesa (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-vesa in Ubuntu.
https://bugs.launchpad.net/bugs/1818879
Title:
pull cirrus.ko into main kernel
ajax gave a patch to fix selecting a better default bpp, so that'll fix
the server to start even without cirrus.ko
** Package changed: xorg-server (Ubuntu) => xserver-xorg-video-vesa
(Ubuntu)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1818879/+attachment/5244324/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
Just the plain Disco kernel environment as you get it when spawning a
new guest - data provided changing state of both bug tasks back.
** Changed in: xorg-server (Ubuntu)
Status: Incomplete => New
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1818879/+attachment/5244322/+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: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1818879/+attachment/5244320/+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: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1818879/+attachment/5244321/+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/1818879/+attachment/5244319/+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: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1818879/+attachment/5244323/+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/1818879
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1818879/+attachment/5244318/+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: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1818879/+attachment/5244316/+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: "Lspci.txt"
https://bugs.launchpad.net/bugs/1818879/+attachment/5244317/+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/1818879
ProblemType: Bug
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Mar 7 08:12 seq
crw-rw 1 root audio 116, 33 Mar 7 08:12 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.10-0ubuntu23
Architecture: amd64
ArecordDevices: Error: [Errno
@Daniel - on one hand it is also a change in xorg that makes the driver missing
now - so an FYI for that.
But in an IRC discussion there were two potential paths to resolve this issue
overall:
- make the cirrus.ko available in the non -extra package so that it works out
of the box using this
67 matches
Mail list logo
