Public bug reported:
https://askubuntu.com/questions/1500676/is-there-a-solution-
for-22-04-and-kernel-6-5-0-14-or-6-5-0-15-22-04-for-users?noredirect=1
I'm running 22.04 LTS with an Asus NVidia GeForce GT 730.
I'm using the Ubuntu provided video driver (Nouveau).
Since upgrading my kernel to
i guess rebuilding gnome snaps with proposed on arm64 and testing that
new gnome snap on mantic for pi5 & x1s would help.
--
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/2037604
Title:
Backport
Public bug reported:
my ubuntu freeze when I update my kernel version, I hope this log can
help me find the cause
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.2.0-33.33-generic 6.2.16
Uname: Linux 6.2.0-33-generic x86_64
libcamera is not shipped on the images, and will be SRUed once tested.
** Changed in: pipewire (Ubuntu)
Status: Triaged => Invalid
** Changed in: libcamera (Ubuntu)
Milestone: None => mantic-updates
--
You received this bug notification because you are a member of Ubuntu-X,
which is
I cannot tell if
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1923363 has FFe
or not for the uaccess addition on udev rules.
** Changed in: mesa (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu-X,
which is
Public bug reported:
[ Impact ]
* HWE for Raspberry Pi 5 https://raspberrypi.com/5
[ Test Plan ]
* Private builds tested on all existing/supported Raspberry Pi SKUs in
armhf & arm64 variants
* No regressions on any existing SKUs
* Test that Raspberry Pi 5 boards work
[ Where problems
** Description changed:
Upstream still hasn't released Mesa 23.2.0 (as of Sep 19th) which is
almost seven weeks past it's original release date. But at least we have
an rc3 which is "only" two weeks old. Yes, we are getting close to
mantic release but this series is something we want for
** Description changed:
Upstream still hasn't released Mesa 23.2.0 (as of Sep 19th) which is
almost seven weeks past it's original release date. But at least we have
an rc3 which is "only" two weeks old. Yes, we are getting close to
mantic release but this series is something we want for
--disable-gpu-driver-bug-workarounds did not work for me, but deleting
GPUCache did. Keep in mind that GPUCache could be inside a profile
folder like ~/.config/google-chrome/Profile 1/.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in
Public bug reported:
When I run sudo apt upgrade, I have this error :
package libgl1-mesa-dri 22.2.5-0ubuntu1 failed to install/upgrade:
tentative de remplacement de « /usr/lib/x86_64-linux-gnu/dri/i915_dri.so
», qui appartient aussi au paquet libgl1-amber-dri:amd64 21.3.7-0ubuntu1
ProblemType:
Specifically version 390.157-0ubuntu2 needs to be removed on i386 and
armhf
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bugs/2008434
Title:
NBS cleanup required in
Public bug reported:
NBS cleanup in lunar-proposed on i386 and armhf
old binaries left on i386: libcuda1-384, libnvidia-cfg1-390, nvidia-384,
nvidia-384-dev, nvidia-compute-utils-390, nvidia-dkms-390, nvidia-driver-390,
nvidia-headless-390, nvidia-headless-no-dkms-390,
Confirming this report on:
Ubuntu 22.04 Host with:
Lenovo Server
Dual 16 Core CPUs (with hyperthreading == 64 CPUS)
384GB RAM
Ubuntu 22.04
Libvirt 8.0.0
QEMU API 8.0.0
Hyervisor QEMU 6.2.0
Ubuntu 22.04 Desktop Guest with:
Q35 VM with OVMF
4 x CPU
8192MB RAM
Trying to run "snap Eclipse". UI
Private bug reported:
attempting to create a desktop type instance on EC2 g4dn using:
* Ubuntu 22.04
* ubuntu-desktop
* nvidia-drivers-470
* xrdp (for testing purposes)
XServer crashes repeatedly.
Reproduction:
aws ssm query to get latest 22.04 image. you can pick region of your
choice:
Public bug reported:
This has happened more than once while using the Google Chrome Browser.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
ApportVersion: 2.20.11-0ubuntu82
Private bug reported:
Random System freeze which required a hard refresh like unplugging The
Power Totally and then restarting it
ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: xorg 1:7.7+22ubuntu2
ProcVersionSignature: Ubuntu 5.13.0-39.44-generic 5.13.19
Uname: Linux
** Summary changed:
- ftbfs with linux 5.16+
+ ftbfs with linux 5.16 & 5.17
** Description changed:
- ftbfs with linux 5.16+
+ [Impact]
- https://github.com/tseliot/nvidia-graphics-drivers/issues/44
+ * FTBFS from with 5.16 & 5.17 kernels
- Due to changes in the kernel w.r.t. stdarg.h
Public bug reported:
ftbfs with linux 5.16+
https://github.com/tseliot/nvidia-graphics-drivers/issues/44
Due to changes in the kernel w.r.t. stdarg.h and stddef.h includes.
** Affects: nvidia-graphics-drivers-390 (Ubuntu)
Importance: Undecided
Status: New
** Affects:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_39a8dbb93caf4ec889f8a1b7f69885db/bileto-4684/2021-10-12_16:41:27/impish_nvidia-
graphics-drivers-390_content.diff
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
That also does not work, due to:
/var/lib/dkms/nvidia/390.144/build/nvidia-modeset/nvidia-modeset-linux.c:72:5:
note: in expansion of macro ‘do_div’
72 | do_div(result, 100);
./include/asm-generic/div64.h:245:36: error: passing argument 1 of ‘__div64_32’
from incompatible pointer
** Patch added: "lp1946642.patch"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1946642/+attachment/5531917/+files/lp1946642.patch
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-390 in
Testing in https://bileto.ubuntu.com/#/ticket/4681
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bugs/1946642
Title:
nvidia-graphics-drivers-390 ftbfs on armhf
To manage
That failed, missed one more place. Retesting.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bugs/1946642
Title:
nvidia-graphics-drivers-390 ftbfs on armhf
To manage
** Patch added: "lp1946642.patch"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1946642/+attachment/5531904/+files/lp1946642.patch
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-390 in
Testing patch in https://launchpad.net/~ci-train-ppa-
service/+archive/ubuntu/4680
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bugs/1946642
Title:
Public bug reported:
nvidia-graphics-drivers-390 ftbfs on armhf
In file included from
/var/lib/dkms/nvidia/390.144/build/nvidia/os-interface.c:16:
/var/lib/dkms/nvidia/390.144/build/nvidia/os-interface.c: In function
‘os_flush_cpu_write_combine_buffer’:
kernel-packages is now subscribed.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to egl-wayland in Ubuntu.
https://bugs.launchpad.net/bugs/1935082
Title:
[MIR] egl-wayland
To manage notifications about this bug go to:
Symbols tracking has been added in
https://launchpad.net/ubuntu/+source/egl-wayland/1:1.1.7-2 which is not
migrating as it is stuck behind glibc
ADT test is hard to provide => functional one needs nvidia graphics
cards that are not present in ADT; and compile test is equally hard
given that it is
sshd_config is user modifyable and maintained. Some options can be
changed using dpkg-reconfigure openssh-server but otherwise changes to
it should be preserved.
Can you please provide steps to reproduce changes to sshd_config getting
lost?
--
You received this bug notification because you are
/boot/grub/grub.cfg is a generated file that must not be modified by
hand. Instead one is supposed to modify things like /etc/default/grub
/etc/default/grub.d/* /etc/grub.d/*
** Changed in: grub2 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a
Public bug reported:
Ubuntu 21.04, mesa 21.0.1-2 amd64
Upstream MR:
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9568
Graphical glitches can be seen occasionally on screen with the RX 6700
XT graphics card.
This is fixed upstream with the above merged MR, so please backport
it...
Timo, Do you have an ETA when this would be released to focal-update?
--
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/1920096
Title:
Cursor bleeds on the platform with Mali armsoc driver
Public bug reported:
I get an error when I try to shutdown via the GUI, screenshot attached.
ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: xorg 1:7.7+22ubuntu1
ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
Uname: Linux 5.11.0-17-generic x86_64
ApportVersion:
@Timo, any ETA for when this would land into Focal? thanks.
--
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/1920096
Title:
Cursor bleeds on the platform with Mali armsoc driver
To manage
Public bug reported:
The boot program is very slow.
An error dialog pops up simply stating there is a problem with the system.
If I open the details a long long list of data is shown, way above my technical
knowledge.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3.1
** Attachment added: "prevboot.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911219/+attachment/5453074/+files/prevboot.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
Public bug reported:
Also freezes when trying to open Libre Office new documents
Not sure if it is the video that is causing issues
Mouse and keyboard seems to be frozen and cant do anything without a
hard reboot
Some times the video keeps playing even if everything is frozen.
ProblemType:
We could use gfxpalyload blacklist, to mark certain nvidia cards there.
And then gfxpayload will not be set to keep, and then vt.handoff will
not be appended.
See grub-gfxpayload-lists package, and files in /usr/share/grub-
gfxpayload-lists/blacklist/
My current preference would be the gdm3 fix.
However dropping vt.handoff is not regression free it may impact
flavours that use lightdm.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bugs/1845801
Title:
[nvidia]
I found a way to enable the amdgpu support for this hardware in the
standard LTS kernel! Based on this comment on a YouTube video reviewing
this laptop:
https://www.youtube.com/watch?v=FjegdWtHuOE=UgzbtkQw4vuk6ls-
6vF4AaABAg
Add "amdgpu.exp_hw_support=1" to the kernel command line in
** Description changed:
Opening Settings -> Display and selecting an orientation other than Landscape
doesn't work.
Similarly, selecting Fractional Scaling and then picking a scale factor has
no effect.
This is a recently installed Ubuntu 20.04, fully updated, on a recently
released
** Attachment added: "This is my screen just after I slide the Fractional
Scaling slider. The icons in the left margin, and the text at the top of the
screen, have changed size (despite me not picking any new scale) and nothing
else has scaled."
** Attachment added: "This is my screen before I slide the "Fractional Scaling"
slider."
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1888088/+attachment/5393945/+files/Screenshot%20from%202020-07-18%2014-21-25%20-%20before%20fractional%20scaling.png
--
You received this bug
** Attachment added: "This is my screen after I chose "125%" as a fractional
scale, then pressed Apply. The pop-up has dimmed the underlying windows, but
you can see that the Scale setting in the underlying Displays window has
reverted to "100%", and nothing on the screen has changed its scale
Public bug reported:
Opening Settings -> Display and selecting an orientation other than Landscape
doesn't work.
Similarly, selecting Fractional Scaling and then picking a scale factor has no
effect.
This is a recently installed Ubuntu 20.04, fully updated, on a recently
released laptop/tablet
Ubuntu no longer uses vt.handover and it should not be specified at all
anymore.
We boot directly to tty1, always and everywhere, and we should not be
setting that at all.
Thus a patch changing that from 7 to 1 is not a good idea for focal+.
And I can't quite remember which releases we have
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xterm in Ubuntu.
https://bugs.launchpad.net/bugs/1878293
Title:
xterm resize is wonky
To manage notifications about this bug go to:
Public bug reported:
% lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 20.04 LTS
Release:20.04
Codename: focal
% wmctrl -m
Name: GNOME Shell
Class: N/A
PID: N/A
Window manager's "showing the desktop" mode: OFF
Terms:
window has four
Workaround exists, obviously:
Resize the xterm from the lower-right corner, or ...
after resizing (with "wonky" effects), move the xterm back where you want it.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xterm in Ubuntu.
Public bug reported:
If the "Tearfree" Xorg option for Intel graphics is turned on, painting
the default wallpaper is corrupted. See attached screenshot.
My X11 change from default for the "Tearfree" option is:
Section "Device"
Identifier "Intel Graphics"
Driver "intel"
Option
That didn't work either. Using the "intel" driver with:
Option "AccelMethod" "UXA"
still resulted in the following GPU HANG:
[drm] GPU HANG: ecode 9:0:0x85da, in compiz [3398], reason:
Hang on rcs0, action: reset
i915 :00:02.0: Resetting rcs0 after gpu hang
Well, that didn't work for very long. Disabling the acceleration of the
"intel" driver did not solve the problem for me. I tried three more
changes, described below.
(1) Next I tried going back to the "modesetting" driver but with the
acceleration disabled:
/etc/X11/xorg.conf
Section "Device"
I just hit another GPU HANG, this time with the "intel" driver instead
of the "modesetting" driver. The kernel log file (/var/log/kern.log)
shows:
Apr 6 08:59:36 tower kernel: [44387.837794]
[drm] GPU HANG: ecode 9:0:0x85da, in Xorg [1751],
I started to see the same GPU HANG error sometime this year (2020).
I am using the default "modesetting" driver with automatic configuration
and no "xorg.conf" file (/etc/X11/xorg.conf). The Xorg log file
(/var/log/Xorg.1.log) is attached.
The following error occurred on April 1, 2020, at
** Also affects: systemd via
https://github.com/systemd/systemd/issues/14322
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-qxl in Ubuntu.
The Debian update has been reverted because freerdp2 isn't in testing
and doesn't build everywhere.
Weston's RDP compositor back-end would make a number of things possible,
notably exposing a LightDM or GDM greeter on RDP. This would allow HD
tablets and Netbooks to log in remotely, e.g. via the
Yes, cannot watch video without display locking
--
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
Firefox
Public bug reported:
Please drop i386 dkms package, as there are no i386 kernel
Systems should enable amd64 archive and install amd64 kernel & the amd64
dkms package.
** Affects: nvidia-graphics-drivers-390 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug
Hi Paul,
I have also confirmed, that 5.4 kernel resolves issues:
Linux green 5.4.0-050400-generic #201911242031 SMP Mon Nov 25 01:35:10
UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
Rather than building from source I got updated kernel package via
mainline kernel build site:
Paul & Co,
I have raised as "possible" kernel fix required here:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853721
Cheers,
Zebity
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
Hi Paul,
thanks for pointing out upstream kernel update.
Where would this get pulled through into Ubuntu ?
To close this off I believe we should link to to either pending pull
request or raise as issue with Kernel to get pull request into Ubuntu
going.
This bug is currently in org, but looks
I have now done further testing and can confirm that this is more than
just upgrade issue.
I have done the following tests:
A) Fresh 19.04 Desktop Install
A.1) Boot - Ubuntu 19.04 Desktop CD-ROM image via USB - Mouse / Cursor ok
A.2) Do clean disk install of 19.04 Desktop (Minimal Install
Since Ubuntu 19.04, I can not use Ubuntu on my VMware virtual machines on my
MacBook Pro Retina (200% scaling). The desktop is white. This still occurs
under Ubuntu 19.10 (even with a clean install).
I hope this problem will be resolved quickly. I want to migrate to a newer
version than my
nd appears to be started, so not sure why I am just getting
splash and no login prompt.
Thank,
John.
--
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/1851340
Title:
Ubuntu 19.10 upgrade results in invis
UI package update and retest.
Likely will only have results later in day.
Thanks
John.
--
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/1851340
Title:
Ubuntu 19.10 upgrade results in invisible
Public bug reported:
I couldn't change brightness. Probably this bug is related to the
problem.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
Uname: Linux 5.0.0-32-generic x86_64
ApportVersion:
dding the following option to: /etc/gdm3/custom.conf
WaylandEnable=false
Regards,
John Hartley.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.1
A
48] (**) Option "fd" "49"
[ 61070.548] (II) event20 - MOSART Semi. 2.4G Keyboard Mouse Mouse: device
removed
[ 61070.548] (**) Option "fd" "41"
[ 61070.548] (II) event24 - John Pelly’s Keyboard: device removed
[ 61070.548] (**) Option "fd" "83"
Was this ever resolved? This same thing is happening to me regularly.
I'm about to give up on Ubuntu; I can't believe something so basic is
broken.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
Public bug reported:
computer takes ages to start.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-52.56-generic 4.15.18
Uname: Linux 4.15.0-52-generic i686
.tmp.unity_support_test.0:
ApportVersion: 2.20.9-0ubuntu7.6
@SRU team, actually we will cherrypick more things into systemd, to make
systemd & xkeyboard-config play nice with each other, as is destined to
be upstream and in disco.
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Also affects: xkeyboard-config (Ubuntu
Debian fixed this:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896979
xserver-xorg-video-nouveau (1:1.0.15-3) unstable; urgency=medium
* Team upload.
* Apply proposed patch to fix a null pointer dereference in
drmmode_output_dpms() (Closes: #896979).
* Cherry-pick commit
** Also affects: initramfs-tools (Ubuntu)
Importance: Undecided
Status: 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/1796822
Title:
Desktop live cd boots corrupted screen
Public bug reported:
Between linux 4.15.0-23 and 4.15.0-24, suspend/resume stopped working
correctly. After resume, the laptop panel remains blank with -24
(external monitors resume correctly). Suspend/resume worked correctly
with -23.
Ubuntu 18.04 LTS
Lenovo P50 laptop, using nouveau driver
It's not a crash or a hang. It locks in terms of the screen being blank
and the login password being required to unlock the screen. Also, I put
this glitch down to the xorg package but I could be wrong.
--
You received this bug notification because you are a member of Ubuntu-X,
which is
Public bug reported:
Computer locks after a few minutes even when Automatic Screen Lock
turned off. I've also tried Screen Lock after e.g. 30 minutes. This
happens on both a new install of 18.04 (on this computer) or after an
upgrade from 16.04 to 18.04 on another computer.
ProblemType: Bug
Now happening on clean install of Bionic.
--
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/1766558
Title:
Multiple Flashing Mouse Pointers
To manage notifications about this bug go to:
Public bug reported:
Slow loading and does not give me fill control of some options I should
have control over is there a program to check my Ubuntu installation?
washerg...@gmail.com
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu
Public bug reported:
Xorg crashes when a Lenovo P50 laptop is undocked, disconnecting it from
two external DisplayPort monitors.
This is an upstream bug which exists in the latest Git revision (ac8f7b949e50
at time of writing):
https://bugs.freedesktop.org/show_bug.cgi?id=106994
Full
Public bug reported:
Hello,
the package is missing in Bionic, so we can't get more than 640x480 in Bionic!
Please provide it.
rgds,
j
** Affects: xserver-xorg-video-mga (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of
This is now Ok without my having done anything except run Software
Update.
--
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/1766558
Title:
Multiple Flashing Mouse Pointers
To manage
Public bug reported:
When I move the mouse, multiple flashing mouse pointers appear on the
display. Sometimes they disappear in a few seconds and sometimes they
stay for minutes or until I've moved the proper pointer to another app.
This only happens when I'm using a USB SSD to boot and start
The problem also no longer occurs in Ubuntu Mate 18.04 beta 32-bit after
latest round of updates.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-libinput in Ubuntu.
https://bugs.launchpad.net/bugs/1760975
Title:
Random
The latest round of updates, including libinput 1.10.4-1, have either
solved the problem or reduced its occurrence to the level where it is no
longer frequent enough to be noticeable on Ubuntu Budgie 18.04.
--
You received this bug notification because you are a member of Ubuntu-X,
which is
The basic GNOME settings, found in
org.gnome.desktop.peripherals.touchpad, can be changed using cli or
dconf but have no effect.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-libinput in Ubuntu.
Installed GNOME shell - no change.
The hardware (Samsung n-130) cannot handle 64-bit.
On Kubuntu 18.04 beta, if tap-to-click is enabled the same behaviour
occurs: the touchpad appears to be intermittently unable to
differentiate between a single finger tap and a two finger tap when
single finger
Please note that this behaviour is not found in the Xubuntu Beta
(installed 2018-04-05) which has the same libinput (libinput-bin &
libinput10) packages as those in Ubuntu Budgie Beta 1 & 2.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
but of course the intel-gpu-tool for trusty hasn't been updated since
2014 so likely it doesn't support i7-7700 (released in 2017) as you
described. However it's the same MIMO error message I am getting. I'm
hoping the same fix will be updated to the version for trusty.
--
You received this bug
Yes I did run with sudo. The error message is different without sudo. I
think the new 14.04.5 fixed a lot of problems with the new intel cpu. At
least it fixed all my graphics card driver issue in one shot. However,
how do I find out what is supported with intel-gpu-tools?
--
You received this
I have exactly the same "Couldn't map MMIO region: Operation not
permitted" problem with Ubuntu 14.04.5 with 1.3-0ubuntu2.1 build. My CPU
is Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz on my ASUS VivoMini PC.
--
You received this bug notification because you are a member of Ubuntu-X,
which is
This issue is still present in Beta-2 (32 bit).
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-libinput in Ubuntu.
https://bugs.launchpad.net/bugs/1760975
Title:
Random right click behaviour with synaptics touchpad
To
I manage 300+ machines that run openafs that has a dkms built kernel
module like the nvidia module that needs to be built. I also manage
dozens of nvidia gpu servers where users have sudo access and can
install anything they want. Here is a snippet of what I found. Note this
is for 16.04 systems
I can't tell if it's still valid because my monitor stopped working and
had to be replaced within a month afterward, and the problem hasn't
happened since.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
I'm not sure about shipping above mentioned patch, due to:
- MODULE_LICENSE("MIT");
+ MODULE_LICENSE("GPL");
But i guess GPL is a superset of MIT
** Changed in: nvidia-graphics-drivers-304 (Ubuntu)
Assignee: (unassigned) => Canonical Kernel (canonical-kernel)
--
You received this
Don't we need to cherrypick e.g.
https://devtalk.nvidia.com/default/topic/1026876/patch-for-387-34-and-
linux-4-15-0-rc1/
into all of them? Note that we need to SRU this back to xenial too, due
to hwe stack, no?
--
You received this bug notification because you are a member of Ubuntu-X,
which
FTBFS dkms module with 4.15 kernel:
/var/lib/dkms/nvidia-304/304.137/build/nv.c:3032:5: error: implicit declaration
of function ‘init_timer’; did you mean ‘init_timers’?
[-Werror=implicit-function-declaration]
init_timer(>rc_timer);
^~
init_timers
** Changed in: nvidia-graphics-drivers-304 (Ubuntu)
Importance: High => Critical
--
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/1748000
Title:
Remove from the archive:
My 14.04 machine received the gcc update after the -116 update, just as
others have noted.
I resolved this by booting into -112 then:
sudo apt-get purge linux-headers-4.4.0-116 linux-headers-4.4.0-116-generic
sudo apt-get install linux-generic-lts-xenial
And then rebooted into -116 with
Ubuntu Bionic)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
--
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/1749199
Title:
purge conf files on removal of upstart (was session fails
** Also affects: xorg (Ubuntu)
Importance: Undecided
Status: New
** Changed in: upstart (Ubuntu Bionic)
Status: Triaged => Won't Fix
** Changed in: xorg (Ubuntu Bionic)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu-X,
1 - 100 of 1389 matches
Mail list logo
