This appears to be the issue. DRM_UNLOCKED does not exist for nvidia-
drm-drv.c to compile. Missing ot changed kernel header?
# CC [M]
/var/lib/dkms/nvidia/545.29.06/build/nvidia-drm/nvidia-drm-gem-nvkms-memory.o
cc
** Attachment added: "The make.log referred to in my comment above"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2063503/+attachment/5770654/+files/make.log
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
Tried again after purging all things NVidia and rebooting.
:~$ sudo ubuntu-drivers install --recommended
udevadm hwdb is deprecated. Use systemd-hwdb instead.
udevadm hwdb is deprecated. Use systemd-hwdb instead.
udevadm hwdb is deprecated. Use systemd-hwdb instead.
udevadm hwdb is deprecated.
Public bug reported:
ll versions of the nvidia driver fail to install no matter what.
Including the one downloaded from Nvidia. It doesn't matter the version.
:~$ sudo apt install nvidia-driver-550
[sudo] password for jim:
Reading package lists... Done
Building dependency tree... Done
Reading
Public bug reported:
Starting a few weeks ago after applying regular maintenance to 22.04.3
LTS one of my two displays, an LG 22MP47HQ-P connected to my tower by a
D-Sub cable, blinked multiple times immediately on resume from suspend.
My second display which is connected using HDMI works
(In reply to Adam Williamson from comment #20)
> Scratch build is done for x86_64:
> https://koji.fedoraproject.org/koji/taskinfo?taskID=107101328
>
> can folks test that and see if it helps? Thanks!
Works after updating to the packages in that Koji task.
--
You received this bug notification
(In reply to Adam Williamson from comment #14)
> Can reporters please test downgrading packages to figure out what actually
> fixes this? I'd suggest this order:
>
> 1. Downgrade mesa to
> https://koji.fedoraproject.org/koji/buildinfo?buildID=2274339
> 2. If that doesn't fix it, downgrade mutter
** Bug watch added: gitlab.freedesktop.org/gstreamer/gstreamer/-/issues #2580
https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/2580
** Also affects: gstreamer via
https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/2580
Importance: Unknown
Status: Unknown
--
The use of vaapipostproc in Totem appears to be through vaapidecodebin:
https://gitlab.freedesktop.org/gstreamer/gstreamer/-/blob/main/subprojects/gstreamer-
vaapi/gst/vaapi/gstvaapidecodebin.c#L326-329
The error path there calls post_missing_element_message(), which would
trigger Totem's
It looks like this isn't related to the other bug report. I hadn't fully
understood the table at the bottom of this readme file:
https://github.com/intel/media-driver/blob/master/README.md
Looks like my CPU is one year too old to support post-processing with
the free shaders.
--
You received
I also ran into a problem with missing VA-API post processing support on
Lunar. I filed it as bug 2019917 since Lunar ships a version that
includes the purported fix mentioned in the Github issue, and I'm unsure
if it is actually the same problem.
--
You received this bug notification because
Public bug reported:
On my laptop with an Intel Core i7-7500U CPU (Kaby Lake), the iHD VA-API
driver does not report VAEntrypointVideoProc support in the output of
vainfo:
libva info: VA-API version 1.17.0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
Hope this email finds you well! Been thinking of you lately. Please let
me know when you get this, I'd like to ask you something. Stay safe and
healthy,
Jim
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
*** This bug is a duplicate of bug 1964037 ***
https://bugs.launchpad.net/bugs/1964037
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1967064/+attachment/5574624/+files/ProcInterrupts.txt
--
You received this bug notification because you
*** This bug is a duplicate of bug 1964037 ***
https://bugs.launchpad.net/bugs/1964037
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1967064/+attachment/5574622/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification
*** This bug is a duplicate of bug 1964037 ***
https://bugs.launchpad.net/bugs/1964037
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1967064/+attachment/5574617/+files/Lsusb.txt
--
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 1964037 ***
https://bugs.launchpad.net/bugs/1964037
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/1967064/+attachment/5574628/+files/acpidump.txt
--
You received this bug notification because you are a member
*** This bug is a duplicate of bug 1964037 ***
https://bugs.launchpad.net/bugs/1964037
apport information
** Attachment added: "xdpyinfo.txt"
https://bugs.launchpad.net/bugs/1967064/+attachment/5574630/+files/xdpyinfo.txt
--
You received this bug notification because you are a member
*** This bug is a duplicate of bug 1964037 ***
https://bugs.launchpad.net/bugs/1964037
apport information
** Attachment added: "Xrandr.txt"
https://bugs.launchpad.net/bugs/1967064/+attachment/5574627/+files/Xrandr.txt
--
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 1964037 ***
https://bugs.launchpad.net/bugs/1964037
apport information
** Attachment added: "nvidia-settings.txt"
https://bugs.launchpad.net/bugs/1967064/+attachment/5574629/+files/nvidia-settings.txt
--
You received this bug notification because you
*** This bug is a duplicate of bug 1964037 ***
https://bugs.launchpad.net/bugs/1964037
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1967064/+attachment/5574626/+files/UdevDb.txt
--
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 1964037 ***
https://bugs.launchpad.net/bugs/1964037
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1967064/+attachment/5574625/+files/ProcModules.txt
--
You received this bug notification because you are a
*** This bug is a duplicate of bug 1964037 ***
https://bugs.launchpad.net/bugs/1964037
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1967064/+attachment/5574623/+files/ProcEnviron.txt
--
You received this bug notification because you are a
*** This bug is a duplicate of bug 1964037 ***
https://bugs.launchpad.net/bugs/1964037
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1967064/+attachment/5574621/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a
*** This bug is a duplicate of bug 1964037 ***
https://bugs.launchpad.net/bugs/1964037
apport information
** Attachment added: "NvidiaBugReportLog.txt"
https://bugs.launchpad.net/bugs/1967064/+attachment/5574620/+files/NvidiaBugReportLog.txt
--
You received this bug notification
*** This bug is a duplicate of bug 1964037 ***
https://bugs.launchpad.net/bugs/1964037
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1967064/+attachment/5574616/+files/Lspci-vt.txt
--
You received this bug notification because you are a member
*** This bug is a duplicate of bug 1964037 ***
https://bugs.launchpad.net/bugs/1964037
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1967064/+attachment/5574619/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 1964037 ***
https://bugs.launchpad.net/bugs/1964037
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1967064/+attachment/5574618/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 1964037 ***
https://bugs.launchpad.net/bugs/1964037
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1967064/+attachment/5574613/+files/CurrentDmesg.txt
--
You received this bug notification because you are a
*** This bug is a duplicate of bug 1964037 ***
https://bugs.launchpad.net/bugs/1964037
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1967064/+attachment/5574615/+files/Lspci.txt
--
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 1964037 ***
https://bugs.launchpad.net/bugs/1964037
apport information
** Attachment added: "DpkgLog.txt"
https://bugs.launchpad.net/bugs/1967064/+attachment/5574614/+files/DpkgLog.txt
--
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 1964037 ***
https://bugs.launchpad.net/bugs/1964037
apport information
** Tags added: apport-collected jammy ubuntu wayland-session
** Description changed:
- When I plug in an external monitor via usb-c thunderbolt port wayland
- crashes and returns to
Public bug reported:
When I plug in an external monitor via usb-c thunderbolt port wayland
crashes and returns to the login screen.
** Affects: wayland (Ubuntu)
Importance: Undecided
Status: New
** Tags: nvidia wayland
--
You received this bug notification because you are a
never mind. Batteries replaced work wonders.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xdiagnose in Ubuntu.
https://bugs.launchpad.net/bugs/1962237
Title:
blue tooth/wireless mouse not working
To manage notifications about this bug go
Ran this hack: https://www.youtube.com/watch?v=I2rHRi2ll9Q
and rebooted in recovery mode and mouse is at least temporarily
functional.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xdiagnose in Ubuntu.
https://bugs.launchpad.net/bugs/1962237
I left a comment about how my system on re-launch appears to revert to
2-22-22 which, I assume is when I attempted to install the update.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xdiagnose in Ubuntu.
It appears that on launch, my system is reverting to 2-22-22 which, I
assume, is when the update was autoloaded and attempted to run.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xdiagnose in Ubuntu.
https://bugs.launchpad.net/bugs/1962237
Public bug reported:
The mouse can occasionally be made to work by going back through
settings, etc. but then very shortly stops again.
I recently updated the system and had to interrupt the update as it was
in an infinite loop while install was running.
I am also running a bitcoin node that is
@Daniel .. Thanks.
* I think brightness-controller is a thin UI around xrandr. If something in
Ubuntu is improperly changing "Brightness" and xrandr is the only cure, why
remove brightness-controller? Or, do your comments about it apply equally to
xrandr -- namely that I should avoid xrandr,
Please feel free to let the bug expire unsolved. While I still use two
monitors arranged as described in the bug report, I don't have software
available to test whether the bug still exists.
On my Ubuntu 20.04systemI don't have an Amazon icon on a launcher
screen, and "webbrowser-app" is not
Public bug reported:
An attempt to do a clean install of NVIDIA drivers resulted in errors. I
was doing so as a program I was intending to use detected that the pre-
installed drivers did not let me use CUDA.
Running a somewhat newly installed Ubuntu 20.04
I expected it to load the drivers as
It appears the same crash symptoms are still happening on Ubuntu 20.04
with xserver-xorg-video-nouveau package and Nvidia GT240 chipset.
Details in Launchpad bug #1954335 -
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
nouveau/+bug/1954335
Package version:
$ dpkg -l
*** This bug is a duplicate of bug 1217585 ***
https://bugs.launchpad.net/bugs/1217585
** This bug has been marked a duplicate of bug 1217585
System hangs after some time with nouveau and GT240
** Tags added: amd64
** Tags added: focal
--
You received this bug notification because you
*** This bug is a duplicate of bug 1217585 ***
https://bugs.launchpad.net/bugs/1217585
Public bug reported:
Hello,
I'm experiencing frequent crashes that hard-lock the system and kernel
completely.
Symptoms are:
- Frozen screen
- No Keyboard or Mouse input accepted
- Remote SSH times out
Public bug reported:
shortly after switching to kernel 5.8.0-50 on Apr 16, I got progressively worse
display scrambling on all programs. Wrote to ubuntuforums.org Apr 19 but found
no resolution. Thinking it was that kernel, I ran on 5.8.0-49 for a day without
problem, then it too started the
The solution has been found and should have been rather obvious in the
first place... Just try a different distribution.
I decided to try out Linux Mint 20.1 and have been testing it for the
past ~6 hours, completely stock (except for all updates installed), no
kernel modifications or GRUB
Well, I spent the past few hours pouring over the entirety of this
thread and I didn't try the patches to pinctrl-amd.c provided by @Helmut
Stult in post #317. These were downloaded and placed in the same source
directory as the other patches for Manjaro kernel 5.11.13-1 and lines
were added to
Hey there @Coiby Xu thank you,
I think I understand what you mean, basically use your Github for this,
standalone_i2c_hid, but copy the i2c drivers from the cloned Manjaro
kernel 5.9.16-1 ../src/linux-5.9/drivers/hid/i2c-hid/ directory into the
../i2c-hid_standalone/ directory in your project
I don't know what I was comparing before, but I was wrong. The pinctrl-
amd.c drivers are different between the two kernels. Apologies. I wonder
if just dropping in the 5.9 pinctrl-amd.c driver (+possibly other
related needed ones?) into 5.10 (or later) would work?
--
You received this bug
Since this is the main thread on the Internet about this issue, I
suppose it is appropriate to post here even though I am using Manjaro.
- This issue is non-present on a Thinkpad 3 14ADA05 with touchpad
MSFT0001:00 06CB:CE2D on kernel 5.9.16-1 which uses i2c_hid. It is not
elantech or designware
Public bug reported:
System
Description:Ubuntu 20.04.1 LTS
Release:20.04
Description:
Plugging in USB hub with peripherals while system is running causes gradual lag
of a visual response, until freezing. usually takes < 1 min. Only work around
is to sleep system between plugging
includes crash
```
Oct 18 21:43:21 james-ThinkPad-X230 kernel: [ 2327.457323] usb 3-3.1: USB
disconnect, device number 4
Oct 18 21:43:21 james-ThinkPad-X230 kernel: [ 2327.457328] usb 3-3.1.1: USB
disconnect, device number 5
Oct 18 21:43:21 james-ThinkPad-X230 kernel: [ 2327.504690] usb 3-3.1.4
Public bug reported:
cannot run windows programs on playonlinux program especially empire
earth 2 which it opens the program but the mouse cursor hangs
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg (not installed)
ProcVersionSignature: Ubuntu 4.15.0-88.88~16.04.1-generic 4.15.18
Just checked, issue persists in 5.6.0 RC1 Kernel, Bios 1.10.0, Ubuntu 20.04.
Closing laptop lid while at login until suspend occurs and then immediately
resuming from suspend appears to enable the keyboard and touchpad.
--
You received this bug notification because you are a member of
I have done some searching around and each of the OD_RANGE parameters,
as they appear in PP_OD_CLK_VOLTAGE seem to be defined in lines 4495 to
4506 of linux/drivers/gpu/drm/amd/powerplay/hwmgr/smu7_hwmgr.c as
follows:
linux/drivers/gpu/drm/amd/powerplay/hwmgr/smu7_hwmgr.c
As copied from file:
""
** Description changed:
GPU=Rx vega m gl
Release=Focal, 20.04 (development)
xserver-xorg-video-amdgpu version=19.1.0-1 (active development)
/sys/class/drm/card1/device/pp_od_clk_voltage cannot be change beyond
the parameters stated at the bottom of this file within the title
Following my previous post I have amended the above, to reflect that
values can be changed, but only within constrictive ranges. Please amend
these ranges to allow overclocking and undervolting.
** Description changed:
GPU=Rx vega m gl
Release=Focal, 20.04 (development)
** Description changed:
- GPU=Rx vega m gl
+ GPU=Rx vega m gl
Release=Focal, 20.04 (development)
xserver-xorg-video-amdgpu version=19.1.0-1 (active development)
- The expected outcome of altering the file, pp_od_clk_voltage, p-states cannot
be changed using echo commands i.e.
+ The
I am running BIOS 1.10.0, Kernel 5.5, Ubuntu 20.04 (development) and am getting
the same issue. The duration appears to vary for the keyboard and track pad to
activate, sometimes it is longer or shorter than 13seconds stated above.
I am also running 9575.
--
You received this bug notification
Public bug reported:
GPU=Rx vega m gl
Release=Focal, 20.04 (development)
xserver-xorg-video-amdgpu version=19.1.0-1 (active development)
The expected outcome of altering the file, pp_od_clk_voltage, p-states cannot
be changed using echo commands i.e.
echo "s 3 700 700" >
Appears to work with updated Ubuntu 18.04. I'll keep the 19.10 partition
around for a little while in case I can provide further information.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-amdgpu in Ubuntu.
dmesg.0.before-hot-plug.txt
dmesg.1.not-yet-frozen-after-hot-plug.txt
dmesg.2.frozen-after-hot-plug.txt
dmesg.3.kernel-oops-reboot-while-attached.jpg
lspci-vvnn.log
regdump_broke.txt
regdump_good.txt
uname-a.log
version.log
Xorg.0.log
** Attachment added: "logs.tgz"
Public bug reported:
Hardware (verified working with Windows 10)
- Lenovo X1 Carbon Gen 7
- Razer Core X with Saphire RX 580
- lspci-vvnn.log
Software
- New install of Ubuntu 19.10
- uname-a.log
- version.log
- mesa and amdgpu software from eoan repo
Symptoms when hot connected
- Doesn't
I extracted the following from /var/log/syslog:
Dec 11 20:53:17 solidus kernel: [ 6767.461655] INFO: task Xorg:3261 blocked for
more than 120 seconds.
Dec 11 20:53:17 solidus kernel: [ 6767.462842] Tainted: G OE
5.3.0-24-generic #26-Ubuntu
Dec 11 20:53:17 solidus kernel: [
Public bug reported:
On this occasion (and there have been many before), X froze (with cursor
still movable) while using Firefox.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
Uname: Linux 5.3.0-24-generic
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
** Changed in: xserver-xorg-video-ati (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
I've hit this too on 18.04.
It may be related to kernel lockdown in UEFI secure boot.
https://bugs.freedesktop.org/show_bug.cgi?id=93199
** Bug watch added: freedesktop.org Bugzilla #93199
https://bugs.freedesktop.org/show_bug.cgi?id=93199
--
You received this bug notification because you
.04.1
> version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
> version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
> version.xserver-xorg-core: xserver-xorg-core N/A
> version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
> version.
Our company just purchased these laptops and we could really use a fix
for them. Would you mind sharing the edid files you created to get the
displays functioning?
** Bug watch added: bugs.dragonflybsd.org/issues #3167
https://bugs.dragonflybsd.org/issues/3167
--
You received this bug
Does Linux plan of patching this issue since 18.04 is an LTS? Anyone
know?
--
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/1821533
Title:
drm fails to accept edid version 2.4
To manage
Public bug reported:
Firefox could not play videos on Gaia.com. The error message blamed the
browser. So I downloaded and installed the browser Opera, with the same
results and message. Both browsers would play Youtube videos.
Please enable Gaia.com videos.
Thanks.
I downloaded the latest
Public bug reported:
FreeCAD installed from Ubuntu Software Center - FreeCAD 17 Beta - worked with
Ubuntu 18.04
but after upgrading to Ubuntu 18.10 the display is unusable.
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: xorg 1:7.7+19ubuntu8
ProcVersionSignature: Ubuntu
@penalvch Unfortunately, 5 years later, this exact bug is still here.
HP EliteBook 8470p, the TouchStyk is showing up as a "PS/2 Generic
Mouse" with no way to configure tap-to-click through either xinput or a
config file.
** Also affects: libinput (Ubuntu)
Importance: Undecided
Status:
Thanks jkampe68! Attachment 6590 completely fixes the problem for me on
Ubuntu and Arch Linux. I've made an AUR package including your patch:
https://aur.archlinux.org/packages/xfce4-settings-blank-screen-fix/
--
You received this bug notification because you are a member of Ubuntu-X,
which is
Public bug reported:
To comply with reporting guidelines:
1) lsb_release -rd output:
Description:Ubuntu 18.04 LTS
Release:18.04
2) Unsure of package name
3) I expected that on boot, the lasso color would immediately be the
correct color, based on background image and/or theme.
4)
Reiterating the above experiences regarding the Dell XPS 9560. Black
screen with nvidia drivers. Cannot workaround this issue unless I
remove the drivers.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
Public bug reported:
I get a blank screen with only mouse pointer upon boot, after the splash. This
started after the mesa driver update on 2/15/18. The display does not appear
to switch to tty7 upon lightdm start.
Xorg.0.log quickly grows and continues to grow.
I believe `lightdm` is not
I have raised this bug at
https://bugzilla.kernel.org/show_bug.cgi?id=198669
** Bug watch added: Linux Kernel Bug Tracker #198669
https://bugzilla.kernel.org/show_bug.cgi?id=198669
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
The file name above should read radeon_ring.c. I thought you used to be
able to edit comments on here!
--
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/1746232
Title:
driver
This crash looks very similar to #1301649. However is does not require
the system to go into power save.
The crash is in radeon_ring_backup which is in
linux/drivers/gpu/drm/radeon/radeon_device.c and part of the linux
(kernel) package.
I have added that package to this bug.
--
You received
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
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/1746232
Title:
driver looping then crashing
To
Public bug reported:
Running driver on Artful with the xwayland compositor. At random times
the GPU stalls with.
Jan 30 11:22:28 dragon kernel: [ 487.046219] radeon :02:00.0: ring 0
stalled for more than 29200msec
Jan 30 11:22:28 dragon kernel: [ 487.046224] radeon :02:00.0: GPU
Right after reporting this and 3 other bugs all at the same time, I
rebooted and it got cought in a loop right before the login and I had to
reinstall.
Thank you for working on these issues, your way ahead of me.
James
On Tue, Jan 9, 2018 at 7:27 AM, Videonauth <1741...@bugs.launchpad.net>
Right after reporting this and 3 other bugs all at the same time, I
rebooted and it got cought in a loop right before the login and I had to
reinstall.
Thank you for working on these issues, your way ahead of me.
James
On Tue, Jan 9, 2018 at 5:17 AM, Jacques Koch <1741...@bugs.launchpad.
** Also affects: lightdm-gtk-greeter-settings
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xdiagnose in Ubuntu.
https://bugs.launchpad.net/bugs/1713313
Title:
Unable to launch pkexec'ed
Anyone with a dual monitor setup (regardless of whether either monitor
is physically rotated) should be able to test if they observe this
problem after setting one monitor rotate-setting to Clockwise. I don't
know whether it can be observed on a single-monitor system.
--
You received this bug
Public bug reported:
I use two monitors, a Plain Tree 22" on the left and a Goldstar 29" on
the right. The Plain Tree is physically rotated 90 degrees
counterclockwise and the Goldstar is not rotated.
In Settings - Displays, the Goldstar 29" has Rotation set to Normal, and
content displays ok
In my case I want to disable the touchpad completely :)
--
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/1694225
Title:
[Thinkpad T450s] Click lock effect on trackpoint
I'm not sure why but a workaround is to run:
sudo rmmod psmouse && sudo modprobe psmouse proto=imps
Then the touchpad gets recognized as:
I: Bus=0011 Vendor=0002 Product=0001 Version=
N: Name="PS/2 Synaptics TouchPad"
P: Phys=isa0060/serio1/input0
S:
Today I grabbed the daily build of 17.10 and booted into it from a USB
drive. It still rotates--but at times I can't predict, the screen will
blank out and then come back rotated. (Should I create a new bug for
17.10?) I should mention that this happens on my laptop, an HP Pavilion
with AMD
** Bug watch added: Red Hat Bugzilla #1448962
https://bugzilla.redhat.com/show_bug.cgi?id=1448962
** Also affects: libinput (Fedora) via
https://bugzilla.redhat.com/show_bug.cgi?id=1448962
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are
Here is what I'm seeing in dmesg:
[2.827809] psmouse serio1: synaptics: queried max coordinates: x [..5676], y
[..4758]
[2.859072] psmouse serio1: synaptics: queried min coordinates: x [1266..], y
[1096..]
[2.920584] psmouse serio1: synaptics: Touchpad model: 1, fw: 8.2, id: 0x1e2b
Bug also affects me. I've isolated it to a specific kernel patch and
updated the upstream bug.
--
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/1406810
Title:
[iMac11,1] Unable to boot
To
For me, it's counterclockwise. I tried setting the "lock rotation"
option referenced in https://askubuntu.com/questions/874487/ubuntu-
gnome-16-10-screen-orientation-spontaneously-changes (had to switch to
Unity 8 to find it), but it didn't make a difference when I logged back
in under Cinnamon,
Public bug reported:
When I first set up ubuntu I was able to look at youtube videos, but
then they just stopped running. I have no real idea why.
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: xorg 1:7.7+7ubuntu4
ProcVersionSignature: Ubuntu 3.19.0-82.90-generic 3.19.8-ckt22
Uname:
Public bug reported:
I don't know
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: xorg 1:7.7+13ubuntu4
ProcVersionSignature: Ubuntu 4.8.0-42.45-generic 4.8.17
Uname: Linux 4.8.0-42-generic x86_64
.tmp.unity_support_test.0:
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
Public bug reported:
post initramfs ??? error satus 1, or something like that new to ubuntu
and don't know much about commandline and how to find and repair
problems; please help thank you much James Street
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
The tricky thing is that it is not a system crash, the computer keeps
running fine. Just the screen goes blank and it is pretty much
impossible to do anything after that. I hope that there is some kind of
error message produced when it happens, now if i could only find it.
--
You received this
No luck with the daily live-cd, some of the kernel messages fly by and
when it tries to change graphics modes for the first time, black screen.
With 16.04 it would sometimes get to the desktop and then would go to
black screen.
I also found this bug report describing the same exact problem:
Done, please note that in the bug report i am using the crimson (fglrx)
driver and kubuntu 15.10, because this is the only way that i can use my
computer. If i try to upgrade to 16.04 and AMDGPU, my computer is
unusable because of the bug. But maybe my hardware information helps.
--
You received
1 - 100 of 819 matches
Mail list logo
