I've tested the "apt-get install xdiagnose/noble-proposed" on 24.04.1 (just the
apt-get upgrade had been stuck for several weeks now).
This install worked, and a subsequent apt upgrade now also completed
successfully, however a it created a bunch of output that seems like there's
something.
Ins
Thank you, in advance, for your line by line assistance in helping me.
electron_...@protonmail.com
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libxcb in Ubuntu.
https://bugs.launchpad.net/bugs/2003703
Title:
package libxcb-record0:amd64 1.
Public bug reported:
I have tried to fix but to no avail.
Please send fix to electron_...@protonmail.com
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: libxcb-record0:amd64 1.14-3ubuntu3
ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74
Uname: Linux 5.15.0-58-generic x86_64
App
** Changed in: mesa (Ubuntu)
Status: New => 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/1960544
Title:
External Monitors Not Detected Anymore
To manage notifications about thi
You are right, updating the kernel did solve the problem. Thanks a lot
for your swift answer!
--
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/1960544
Title:
External Monitors Not Detected Anymore
Public bug reported:
On Ubuntu 20.04 on a DELL XPS13 (with i915 Chip): after the update of
mesa-vulkan-drivers from 21.0.3 to 21.2.6 (incl. libgl*, libdrm* etc.),
external displays (here connected via DELL USB Dock) are not detected
anymore. I had to restore the old version with Timeshift.
** Aff
Same here with Ubuntu 20.04 on a DELL XPS 13 (with i915 Chip): after the
update of mesa-vulkan-drivers from 21.0.3 to 21.2.6 (incl. libgl,
libglapi, libdrm etc.), external monitors (here connected via DELL USB
Dock) are not detected anymore. I had to restore the old version with
Timeshift.
--
You
Public bug reported:
I recently installed ubuntu 20.04 on my computer, and I am running into
an issue when I do the following:
* Login with a user on desktop
* Select switch user, and login as second user
* Switch user again, and return to original user
At this point, text and icons in the menub
Kodi devs-team were very conservative they would not help and asked me
to wait Ubuntu fix the bug.
Kodi is a reference to a bug that affects every graphical software
installed.
I'm observing every new mesa and kernels upgrades, I'll keep informing.
--
You received this bug notification because
No, Kodi does not crash anymore with x-swat and since official mesa
19.0.8-0ubuntu0~18.04.2
But it's followed by another problem, it's not 100% solved.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bu
Just tested your ppa with mesa 19.2.1-1ubuntu1~18.04.1~ppa2, thank you
Since mesa 19.0.8-0ubuntu0~18.04.2 the image produced by Ubuntu with all
media players and browsers is very dark, like the contrast and black
levels were adjusted at a very low value. It became worse than before,
including your
** Attachment added: ""journalctl -b -1" (failed boot) for other user"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1848900/+attachment/5298524/+files/jj9k.log
** Summary changed:
- blank display with Eoan Ermine live DVD on Rysen 2200G
+ Blank display with Eoan Ermine live DVD on Ryze
I was supporting another Xubuntu 19.10 user on AMD Ryzen 3 2200G
(Gigabyte Technology Co., Ltd. B450 AORUS M/B450 AORUS M, BIOS F2
08/08/2018) today, whose log of a failed (standard) boot (to black
screen) showed
kernel: WARNING: CPU: 2 PID: 255 at
drivers/gpu/drm/amd/amdgpu/../display/dc/dcn10/dc
hi guys, on ubuntu bionic 18.04 amd64 I still can't install
libsdl2-dev:i386 and libsdl2-dev:amd64 because of that libxkbcommon-
dev:i386 and libxkbcommon-dev:amd64 can't coexist. Is there any progress
so far?
--
You received this bug notification because you are a member of Ubuntu-X,
which is su
Thank you for your assistance.
Let me know when it's figured out.
--
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/1837170
Title:
Kodi package crash after the update of libdrm-amdgpu1
To manage
Using Kodi as reference for the behaviour of VDPAU hw acceleration on
the system:
The latest version of mesa doesn't work and makes Kodi crash when opening any
video.
I figured that when I downgrade every package of mesa to version 18.2.8, kodi
is now able to
run videos, but still without vdpau.
I suggest you mark the importance of this bug as Critical, because it
affects every single user of AMD APUs.
We have no HW Acceleration.
--
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/1837170
Tit
Not yet mate.
Installing the packages from this ppa have the same effect of downgrading them.
Kodi responds better, still there's no HW Acceleration.
I've just tested a Nvidia card using noveau and proprietary drivers, it worked
well.
But it was borrowed, I'll have to return it unfortunately ;(
Please Timo, there's really a problem with AMD APUs
We are running our systems without HW Acceleration support
--
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/1837170
Title:
Kodi package crash a
Should I create a new bug report on linux-firmware package?
--
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/1837170
Title:
Kodi package crash after the update of libdrm-amdgpu1
To manage notific
I've tested Ubuntu 18.04.2 on 2 machines with different hardware:
- One Laptop with Intel CPU integrated graphics, it works well.
- A Laptop with an AMD APU, the problem is the same.
I use a Kaveri AMD APU on my main PC and the other person affected on
this bug, another AMD APU.
So we have 3x p
Thanks for your feedback. Please post a link here to the upstream bug
report once you filed it.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-amdgpu in Ubuntu.
https://bugs.launchpad.net/bugs/1837945
Title:
AMD RX 570 Blac
Oh, I see incoming updates for mesa 19.0.8 in bionic as well. They're
still under final adjustments then, I hope it fix my issue.
--
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/1837170
Title:
Ko
What's happening here?
Everything I download from this server
http://mirrors.edge.kernel.org/ubuntu/pool/main/u/ubuntu-meta/
Firefox accuses of having a virus or malware and eliminate the files.
It's an official Ubuntu North America server.
--
You received this bug notification because you ar
Please ignore the solution I commented, I committed a mistake and had
vdpau disabled.
But there's this update that hasn't been released by the server.
--
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
Solution's found:
ubuntu-meta (1.417.3) bionic; urgency=medium
* Added dbus-x11 to wsl-recommends (LP: #1837466)
-- Balint Reczey Wed, 24 Jul 2019 01:21:39 +0200
I found in the server this latest version of ubuntu-desktop and
installed the .deb file.
Indeed we see a correction for X11/xor
https://lists.ubuntu.com/archives/bionic-changes/2019-July/021427.html
--
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/1837170
Title:
Kodi package crash after the update of libdrm-amdgpu1
To man
Timo, I think the problem is with xorg-server,
along with mesa, it was present on the latest updates when the crash came up.
When kodi tries to load a video, its window simply closes.
If switch to Wayland, it works.
But everything is very buggy with this server, it's inoperable.
Maybe there are
** Changed in: xserver-xorg-video-amdgpu (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-amdgpu in Ubuntu.
https://bugs.launchpad.net/bugs/1837945
Title:
AMD RX 570 Black Scree
Surena: After collecting logs, please continue and report this upstream where
other amdgpu bugs have already been reported:
https://bugs.freedesktop.org/buglist.cgi?product=DRI&component=DRM%2FAMDgpu&list_id=676975&resolution=---
You can file a new bug at https://bugs.freedesktop.org/enter_bug.cg
Apologies, the correct command is:
apport-collect 1837945
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-amdgpu in Ubuntu.
https://bugs.launchpad.net/bugs/1837945
Title:
AMD RX 570 Black Screen at boot
To manage notific
Please also test with the default 19.04 kernel (ideally the installer,
too), can you get graphical output there using amdgpu.dc=0 ?
While running from the installed system, if possible using the default (after
updates) kernel image, with amdgpu.dc=0 set, please run:
apport collect-logs 1837945
Currently I found that downgrading these packages:
libgl1-mesa-dri_18.2.8-0ubuntu0~18.10.2_amd64.deb
mesa-vdpau-drivers_18.2.8-0ubuntu0~18.10.2_amd64.deb
I can run Kodi with every single Ubuntu package updated, including
libdrm-amdgpu.
**Note: from oibaf's ppa I need only libdrm-amdgpu1 libdrm-c
How could I make mesa-vdpau-drivers work?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libdrm in Ubuntu.
https://bugs.launchpad.net/bugs/1837170
Title:
Kodi package crash after the update of libdrm-amdgpu1
To manage notifications about thi
I've tested Ubuntu Studio Bionic Beaver 18.04, and since it receives all the
same updates from default Ubuntu, the results were identical.
As to disco dingo, I really prefer to go with the more polished LTS versions as
a personal choice of mine.
--
You received this bug notification because yo
As I said, the closest package to linux-image-hwe-edge I found for
installation is:
sudo apt install --install-recommends linux-image-generic-hwe-18.04-edge
That gives me the Kernel version
uname -r 5.0.0-20-generic
Unfortunately kodi didn't work, only with the removal of mesa-vdpau-
drivers.
-
I've found a different problem situation:
I first applied the downgrade of libdrm-amdgpu1 2.4.97-1ubuntu1~18.04.1 to
2.4.95-1ubuntu1~18.04.1, on the first launch of a newly installed Ubuntu
18.04.2 without any of the 400 updates packages available.
This way I got package Kodi working.
Now, afte
Public bug reported:
Greetings,
The last update of libdrm-amdgpu1 caused a bug on Kodi package, making
it to crash after loading any video or reproduce a black image.
Version: 2.4.97-1ubuntu1~18.04.12019-07-03 15:07:54 UTC
libdrm (2.4.97-1ubuntu1~18.04.1) bionic; urgency=medium
* B
** Summary changed:
- High memory usage by Xorg.
+ High memory usage by Xorg with Kubuntu 18.04, plasma-desktop, nvidia 390
--
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/1833829
Title:
High me
The mouse has a left-click button, a right-click button and a
scrollwheel in between that is clickable.
--
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/1832133
Title:
Mouse unresponsive on Ubuntu
Here are details on my mouse.
Manufacturer: TRUST (www.trust.com)
Model: AMI MOUSE 250S OPTICAL
--
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/1832133
Title:
Mouse unresponsive on Ubuntu 18.04
.
Result of lsb_release -rd: Description: Ubuntu 18.04.2 LTS. Release:18.04
I am using Xdiagnose version 3.8.8
Please help!
Tom.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
Uname: Linux 4.15.0-51-generic
I have this same problem on 18.04. It's very noticeable that when my
network has no DNS working, screen unlock takes a long time - as much as
a minute or two.
I notice this because I often manually configure my network to do DNS
lookups over an SSH tunnel. If I just close the lid of my laptop it
Thanks for your report. I'm not a developer, just having a quick glance
on your logs:
Your system log shows I/O errors on /dev/sdb, a 1.00 TB storage. This
can be due to bad cabling / connectors or due to a bad disk.
Additionally, the USB connection to the WD My Passport 25E1 drive was
reset twice
I'm facing this issue in the latest kernel mainline, too.
CPU is an Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz (which uses i915 graphics).
The graphic glitches were gone after some kernel update but the error messages
in dmesg remained.
--
You received this bug notification because you are a memb
@tjaalton ... funny, >185 persons report they have same issue here
without any solution.. and then bug reports get closed without reference
to where to duplicate all reports ? ))
Do you have bug number where we can copy and paste this to ?
--
You received this bug notification because you are a
It remains weird that a complete ciritical-show-stopping bug receives no
attention from the true experts... What are we doing wrong to report it
here?
--
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
It's indeed a big mystery when one of the maybe most serious bugs in
18.04 is marked as fixed while it clearly is not
--
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/1752053
Title:
nvidia-39
@aurelienpierre: are you sure your laptop uses the same device number as
the Dell XPS 15 this script was for (:01:00.0)?
--
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/1752053
Title:
nvidia-
@bernadette, it baffels me. Today my Xps 15, 9560 works flawlessly fast
and nimble. I also nailed the power drain and now have ~5W running on
battery, see https://github.com/stockmind/dell-xps-9560-ubuntu-
respin/issues/8
Makes me thinking... what BIOS version do you have ? I run 1.9.4
** Bug wat
echo "1" > /sys/bus/pci/devices/\:01\:00.0/remove is required for me
to powerdown nvidia, but it results in powerdown freeze
Still investigating ... ((
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.ne
It seems with the following two commands, I can get my power from ~15W
to ~8W on Dell XPS 15 9560:
# move from Nvidia to intel graphics (if not already done)
prime-select intel
# switch of power to Nvidia (repeat after each laptop start)
sudo sh -c 'echo auto > /sys/bus/pci/devices/\:01\:
@Dedas: I cant see any difference; power consumption on Dell XPS 15 9560
stays the same...
--
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/1752053
Title:
nvidia-390 fails to boot graphical displa
@Dedas can you elaborate a bit more what that does?
- Is it safe?
- Will it allow switching nvidia on with "sudo prime-select nvidia" ?
- Is this command needed only once?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bu
@Joseph: did you try #121 ?
--
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/1752053
Title:
nvidia-390 fails to boot graphical display
To manage notifications about this bug go to:
https://bugs.l
Confirm the issue seems everybody on 18.04 and Nvidia GeForce is
suffering...
Duplicates ?
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1752053
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1765363
--
You received this bug notification becaus
This all might be related to https://bugs.launchpad.net/ubuntu/+source
/nvidia-prime/+bug/1765363 I think...
--
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/1752053
Title:
nvidia-390 fails to bo
@Bernadette: If I would have same situation again, I think I would:
1 - Ctrl-Alt-F3/2 at login prompt
2 - sudo apt purge nvidia*
3 - sudo apt install nvidia-390
4 - sudo prime-select intel
5 - sudo nvidia-xconfig
6 - sudo nano /etc/X11/xorg.conf
7 - .. and replace with contents of #117
8 - sudo n
#117 worked for me, although "suspend" is still shaky; 50% of time I
need to force power off.
--
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/1752053
Title:
nvidia-390 fails to boot graphical dis
Today I got all working, but although prime-select query showed me
"nvidia", nvidia drivers were not loaded and nvidia-settings did not
start. I regret that I decided to run "sudo prime-select intel". Login
worked but it broke suspend mode and my logout/shutdown times are
horrible: 1,5 minutes.
*
@Benadette: I've done both several times: upgrade and fresh reinstall; same
troubles so it does not seem to matter. I also got the pci bus errors at first,
before the nvidia driver took it's place . Do you get to the login prompt? My
procedure above, starting at the login prompt with Ctrl-AltF2
to myself: avoid Nvidia in
laptops like the plague. Please... read this again, Tom, in 3 years when
a new laptop is due **no optimus/prime/Nvidia on laptops** ... !!
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.lau
Proposed update fixed issue on gen5 Ironlake hardware (Dell Inspiron
N5040).
libgl1-mesa-dri:
Installed: 17.2.4-0ubuntu1~16.04.3
Candidate: 17.2.4-0ubuntu1~16.04.3
Version table:
*** 17.2.4-0ubuntu1~16.04.3 400
400 http://us.archive.ubuntu.com/ubuntu xenial-proposed/main amd64
Pack
Same problem here - booting kubuntu 17.10 using the new, default
'lowlatency' kernel led to a black screen. Manually selecting the
'generic' kernel via the advanced options in grub worked fine. I've got
an nvidia 780 card.
--
You received this bug notification because you are a member of Ubuntu-
I should add that when file is opened by CLI, every file inside has the
locked icon, so something funky with users/permissions/root is likely
going on.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xrandr in Ubuntu.
https://bugs.launchpad.net/b
Used synaptic to "remove completely" all zulucrypt packages. Installed
the 4 .deb packages in order again. Same errors.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xrandr in Ubuntu.
https://bugs.launchpad.net/bugs/1722615
Title:
zuluCrypt
OK. Broke into synaptic with
https://ubuntuforums.org/showthread.php?t=2367294.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xrandr in Ubuntu.
https://bugs.launchpad.net/bugs/1722615
Title:
zuluCrypt doesn't launch
To manage notifications
figured out xhost +local was not the command.
after running xhost +MyHostname
sudo synaptic
[sudo] password for tom:
No protocol specified
Unable to init server: Could not connect: Connection refused
(synaptic:5993): Gtk-WARNING **: cannot open display: :0
--
You received this bug
1. Synaptic doesn't run in Wayland (17.10 is wayland).
2. sudo xhost +local
no protocol specified
xhost: unable to open display ':0'
xhost +local
xhost: bad hostname 'local'
Yes, I have those packages installed, but they're the ones you told me to
install in the binary, which i installed per the
+++-==---=
iU zulucrypt-cli 5.2.0-1 amd64tool for encrypting volumes
iU zulucrypt-gui 5.2.0-1 amd64graphical front end for
zulucrypt
On Thu, Oct 12, 2017 at 1:05 PM, Tom Mercer wrote:
> Before installing the binary, I ran sudo apt rem
(no description available)
in libzulucryptplamd64(no description available)
iU zulucrypt-cli 5.2.0-1 amd64tool for encrypting volumes
iU zulucrypt-gui 5.2.0-1 amd64graphical front end for
zulucrypt
On Thu, Oct 12, 2017 at 1:07 PM, Tom Mercer wrote
Before installing the binary, I ran sudo apt remove zuluCrypt-cli
zuluCrypt-gui, then autoremoved. How would you advise to remove all
zuluCrypt packages?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xrandr in Ubuntu.
https://bugs.launchpad.net
So zuluCrypt-cli -o -d /home/USERNAME/filename fails, but
sudo zuluCrypt-cli -o -d /home/USERNAME/filename works, with either the old
zC or the new binary you gave me.
If I run through the GUI from the binary, it looks MUCH nicer than it has.
Finally modern look and scaling and windows and buttons
Thanks a million for the prompt and thorough response!
I'm really newb, so with that in mind, I came up with 3 different
possible ways I can solve this:
1. Can you give me a stupid-simple complete example of mounting and
unmounting a file from cli with a password? The examples I can find are
insu
Public bug reported:
type zuluCrypt-gui from command line, or select it from launcher.
am prompted to authenticate, but after authentication, no window opens.
tried uninstalling, reinstalling.
17.10 Wayland artful zuluCrypt
** Affects: xrandr (Ubuntu)
Importance: Undecided
Status
** 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.
https://bugs.launchpad.net/bugs/1722419
Title:
17.10 xrandr doesn't seem to function
To manage noti
The file I'm testing with has a "H264 - MPEG-4 AVC (part 10) (avc1)"
video track.
--
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/1574354
Title:
playing .mp4 in VLC freezes machine
To manage not
I'm on Ubuntu 16.04.3 with mainline kernel
Linux version 4.13.2-041302-generic (kernel@tangerine) (gcc version
7.2.0 (Ubuntu 7.2.0-3ubuntu1)) #201709132057 SMP Thu Sep 14 00:59:32 UTC
2017
and mesa 1:17.3~git170914191100.7ffd4d2~x~padoka0 and X from the Padoka
PPA.
OpenGL renderer string: Radeon
Public bug reported:
occasionally the screen will darken and just do nothing for a while..
then lighten up and everything is fine. Also, occasionally the screen
will go into a spasm with multiple colors all across, (with previous
screen barely visable behind it. I push cont alt del and when the
-
and-missing-letters (intel driver issue?). Only restarting lightdm (or
logging out and in again), fixed the situation.
root@tom-laptop:/home/tdesloovere# lshw -sanitize -numeric -C display
*-display
description: VGA compatible controller
product: 4th Gen Core
Note this only happens with the laptop's built-in keyboard, not a USB
keyboard.
--
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/1620128
Title:
Keys that are held down for more than 1s repeat endl
Public bug reported:
I'm not sure how else to describe this than the title: keys that are
held down for more than 1s (as near as I can judge) repeat endlessly.
If I strike the 'n' key, I get one 'n'. If I hold it down for over one
second, I get a never-ending stream of 'n's, until I press the 'n'
Public bug reported:
xdypinfo reports wrong screen dimensions and resolution (always 96x96
dpi).
$ xdpyinfo | grep -B2 resolution
screen #0:
dimensions:3840x2160 pixels (1016x571 millimeters)
resolution:96x96 dots per inch
However, xrandr reports the right dimensions:
$ xrandr
Scr
** Description changed:
+ **UPDATED AS REQUESTED**
+
+ 7/02: The display setting commands are to change the display orientation
+ (I want to rotate the display 90' clockwise). Two displays, on the same
+ graphics card, the primary card as listed in the BIOS, will respond to
+ those commands. Howe
I find that once this happens, if I move the cursor to a second monitor
and back it reappears.
--
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/1568604
Title:
Mouse cursor lost
** Description changed:
I have two identical AMD Cards and whichever card I name in the BIOS as
primary correctly displays the desktop and allows me to orient the
desktop directly (landscape, portrait, etc).
The secondary card will not allow the settings to be changed in anyway.
Perfo
Public bug reported:
I have had consistent issues in both 14.04 (even with FGLRX installed)
and 16.04 with the graphics card labeled as secondary in the BIOS
correctly displaying or even responding to display setting commands in
Unity.
LSPCI Info
00:00.0 Host bridge: Intel Corporation 4th Gen Co
Please note that this issue has come up with a machine upgraded from
14.04 to 16.04.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
https://bugs.launchpad.net/bugs/1354793
Title:
Radeon X-Server Error
I meant to include the bug # filed under Xorg: Bug #1582947
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
https://bugs.launchpad.net/bugs/1354793
Title:
Radeon X-Server Error
To manage notifications a
** Summary changed:
- mouse pointer vanishes when i double click any folder
+ Same Radeon X-Server Error
** Summary changed:
- Same Radeon X-Server Error
+ Radeon X-Server Error
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-inpu
Public bug reported:
I have two identical AMD Cards and whichever card I name in the BIOS as
primary correctly displays the desktop and allows me to orient the
desktop directly (landscape, portrait, etc).
The secondary card will not allow the settings to be changed in anyway.
Performance is not i
Hi Mika
Yes, applying patch 66697 against the latest intel-drm-nightly does
still resolve the issue.
--
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/1522922
Title:
Screen fli
(In reply to Tom Furniss from comment #72)
> Hi Mika
>
> Yes, applying patch 66697 against the latest intel-drm-nightly does still
> resolve the issue.
Actually, within 10 seconds of posting that message the flickering
started again, and has continued through multiple reboots. So I
Created attachment 120920
dmesg for 3 patches with increased debug
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libdrm in Ubuntu.
https://bugs.launchpad.net/bugs/1522922
Title:
Screen flickering in Intel i915 driver
To manage notifications
Created attachment 120919
syslog for 3 patches with increased debug
Hi Mika
No problem. I applied the following patches to the latest drm-intel-nightly:
https://patchwork.freedesktop.org/patch/69394/
https://patchwork.freedesktop.org/patch/69395/
https://patchwork.freedesktop.org/patch/69396/
ht
Created attachment 120819
dmesg after three patches and returned flicker
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libdrm in Ubuntu.
https://bugs.launchpad.net/bugs/1522922
Title:
Screen flickering in Intel i915 driver
To manage notific
(In reply to Rodrigo Vivi from comment #65)
> Seeing the video again and based on recent issues I faced I believe this
> could be watermark related...
> So, could you please apply http://patchwork.freedesktop.org/patch/69417/
> and boot with i915.enable_watermark=0 and let us know what happens?
Th
Created attachment 120818
syslog after three patches and returned flicker
Hi Mika.
I seem to have regressed, and the flicker has returned. I took a new
branch of intel-drm-nightly, and applied the three patches in the
sequence you provided, but the flickering has returned and is consistent
on ev
Created attachment 120678
syslog for sleep/resume flickering issue
Mika - this is the syslog for the flickering on resume from sleep, after
applying your latest patch
(https://bugs.freedesktop.org/attachment.cgi?id=120493)
I do fairly consistently see a single flicker after requesting sleep,
and
(In reply to Mika Kahola from comment #55)
> Created attachment 120493 [details] [review]
> Disable fast link training when resuming
>
> Tom - thank you for you feedback and logs. I think I need to disable the
> fast link training feature when resuming from the suspend state. Th
1 - 100 of 529 matches
Mail list logo
