Public bug reported:
I'm not sure how to report this really as it's not a bug but still quite
severe. Bear with me as I'm a Unity dev mainly.
Unity uses function calls to X11 for setting mouse cursor positions.
Many games use this to lock the cursor to a certain position.
With no backwards
@oibaf thanks, I reported it:
- https://gitlab.freedesktop.org/mesa/mesa/-/issues/1
(nice issue number by the way ☺️)
** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #1
https://gitlab.freedesktop.org/mesa/mesa/-/issues/1
--
You received this bug notification
I reproduce the bug with current Mesa
(d97427f41c1603db2f657b5d9c3f91a97f74b1c0) and LLVM 16.0.6. I don't know
if the bug is on drm side or on Mesa side.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
I reproduce the same issue if I just do:
```
DRI_PRIME=1 glxinfo -B
name of display: :1
```
Which means the fault happens when using the AMD FirePro S7150, NOT the
AMD Radeon PRO W7600.
Maybe for some reasons Unigine Superposition tries to use all GPUs
available?
So, the bug is now easier to
** Description changed:
When I run Unigine Superposition 1.1, it doesn't open any window and
dmesg is filled with:
```
[36881.961064] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for
command submission!
[36881.962579] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough
In the log file you may see notice of some amdgpu-pro OpenCL components
like ROCm ROCr OpenCL or Legacy Orca OpenCL, there is no amdgpu-pro
OpenGL or dkms module installed though. Removing entirely the amdgpu-pro
OpenCL packages produce the same bug anyway. The contrary would have
been surprising
Public bug reported:
When I run Unigine Superposition 1.1, it doesn't open any window and
dmesg is filled with:
```
[36881.961064] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for
command submission!
[36881.962579] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for
Public bug reported:
Only an annoying bug
I cannot remove the attached from my menu on the side panel.
Other items are removed ok.
ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.19.0-43.44-generic 5.19.17
Uname: Linux 5.19.0-43-generic
Public bug reported:
This can be verified with any OpenCL application that actually tries to
compute something (clinfo may not be enough).
A very simple application to reproduce the bug is cl-mem:
```
git clone https://github.com/nerdralph/cl-mem.git
cd cl-mem
make
./cl-mem
OpenCL build failed
Same problem on Lenovo W540 with Quadro K1100M. Upgraded to 23.04
yesterday (coming from 22.10)
If I boot with an older 5.x kernal it works. So it seems to be an issue
with the new 6.x kernal.
According to this forum post over on nvidias forum
Public bug reported:
Touching the touch screen display removes the mouse cursor. It comes back after
blindly navigating to the menu bar. This also happends randomly without
touching the touchscreen. There doesn't appear to be a trigger for the random
disappearances that is user input.
Thanks,
If you don't like that, you should (see the FAQ) avoid using Linux
console as well.
--
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/1983276
Title:
xterm processing grep color loses char at end
You might find the FAQ helpful:
https://invisible-island.net/xterm/xterm.faq.html#vt100_wrapping
--
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/1983276
Title:
xterm processing grep color
That's not a bug. Here's a cleaned-up demo for 80 columns:
echo '--
--\33[01;31m\33[KABCD\33[m\33[KE'
See for example
https://invisible-island.net/vttest/vttest-wrap.html
** Changed in: xterm (Ubuntu)
Status: New
Ok, I created this issue:
https://gitlab.freedesktop.org/drm/amd/-/issues/2088
** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #2088
https://gitlab.freedesktop.org/drm/amd/-/issues/2088
--
You received this bug notification because you are a member of Ubuntu-X,
which is
** Tags added: needs-packaging
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libwacom in Ubuntu.
https://bugs.launchpad.net/bugs/1959140
Title:
pls raise libwacom to 2.0.0 for new device support
To manage notifications about this bug go
Public bug reported:
It would be nice to have up to date libwacom in Ubuntu 22.04 to support
current hardware.
https://github.com/linuxwacom/libwacom/releases/tag/libwacom-2.0.0
** Affects: libwacom (Ubuntu)
Importance: Undecided
Status: New
** Tags: jammy
** Description
*TECHNICALLY* you aren't wrong. However, let's consider that I"ve been
around since 2009 in the Ubuntu world (2012 when I started deep diving
into it technically) and NVIDIA has *never* provided any drivers binary
or otherwise that work on non-x86 infras. I don't see any time yet that
NVIDIA is
Why is this required?
Currently, there are **no** binary drivers for NVIDIA which nvidia-
settings would work with in RISCv, based on my research, meaning that
from my POV there's no justification for making nvidia-settings work in
RISCv.
** Changed in: nvidia-settings (Ubuntu)
Status:
** Attachment added: "glitch.jpg"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1936716/+attachment/5511589/+files/glitch.jpg
--
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/1936716
Public bug reported:
There was a glitch as I was watching a youtube video that imprinted a
still image on the screen with transparent vertical stripes. Restarted
the computer and the same image was imprinted behind the GRUB boot-
loader menu during start up. Unusual behavior that continued 2-3
Since there wasn't a reply to my question since more than half a year,
I'm assuming that this does not affect upstream QEMU anymore. Thus I'm
removing upstream QEMU from this ticket now.
** No longer affects: qemu
--
You received this bug notification because you are a member of Ubuntu-X,
which
The issue was never really in xfce4-sensors-plugin, it was in nvidia-
settings. Since the FTBFS is fixed with the newer nvidia-settings, I'm
going to mark this as 'invalid' for xfce4-sensors-plugin as the FTBFS
wasn't part of the package itself but a supporting package that was
required.
**
** Changed in: nvidia-settings (Ubuntu)
Status: In Progress => Fix Committed
** Changed in: nvidia-settings (Ubuntu)
Assignee: Thomas Ward (teward) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-se
Fixed nvidia-settings uploaded to hirsute, waiting acceptance by release
team.
** Changed in: nvidia-settings (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-settings in Ubuntu.
Doing some testing as part of me being thorough to confirm the FTBFS
doesn't happen with the updated nvidia-settings present (in PPA - want
to reproduce the FTBFS first before putting the new nvidia-settings into
that PPA for testing the FTBFS)
--
You received this bug notification because you
** Changed in: nvidia-settings (Ubuntu)
Assignee: (unassigned) => Thomas Ward (teward)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-settings in Ubuntu.
https://bugs.launchpad.net/bugs/1922583
Title:
xfce4-sensors-plugin: FT
Public bug reported:
I don't know what would be useful for you
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-136.140-generic 4.15.18
Uname: Linux 4.15.0-136-generic i686
.tmp.unity_support_test.0:
ApportVersion:
also affects 20.04 as i tried once again after 2 years ...
--
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/1810913
Title:
xorg w. QXL driver crashes while using Intellij IDEA or PyCharm
Public bug reported:
When exiting fullscreen from chromium (YouTube), the clock widget in the
top bar seems stuck and only updates after being updated from the mouse
hovering over it.
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: xorg 1:7.7+19ubuntu15
ProcVersionSignature: Ubuntu
mgsloan: That's pretty awful indeed, because applying these keyboard
settings locks up all keyboard input for multiple seconds. (depending on
how many settings you need to apply)
Do I read https://bugs.freedesktop.org/show_bug.cgi?id=25262 right when
I say that this is saying that Xorg does not
following error is
still present:
thomas@deepthought2:~$ sudo /usr/bin/nvidia-settings
(nvidia-settings:7845): GLib-GObject-CRITICAL **: 09:17:21.642: g_object_unref:
assertion 'G_IS_OBJECT (object)' failed
** Message: 09:17:21.764: PRIME: No offloading required. Abort
** Message: 09:17:21.
and a re-boot
--
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/1900716
Title:
"Elan Touchpad" not working on "Asus X205TA" after upgrade to ubuntu
20.10
To manage
Hi Tobias,
I experienced exactly the same when upgrading to 20.10 on the same hardware.
This solved the problem:
sudo apt install xserver-xorg-input-synaptics
Thomas
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-libinput
Public bug reported:
while starting X11 xrandr executes commands:
xrandr --newmode "3840x2160_30.00" 338.75 3840 4080 4488 5136 2160 2163 2168
2200 -hsync +vsync
xrandr --addmode DP-1 "3840x2160_30.00"
xrandr --output DP-1 --mode "3840x2160_30.00"
while newmode, addmode work, the third
Is there still an issue left here for upstream QEMU?
** Changed in: qemu
Status: New => Incomplete
--
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/1718719
Title:
qemu can't
The PC keeps asking to first do a Ubuntu 18 upgrade, which is not possible.
Then trys to do a fix for the previous video bug. I have reverted it back a few
updates and it is running better, but will eventually request to do an update
again. I believe Ubuntu 16 is still supported if not I will
Public bug reported:
Please how can I block this upgrade on this PC? It is a 32 bit system
with dual boot Windows 7 & Linux Ubuntu 16.04. It is a Dell Optiplex
380, and runs great other then trying to deal with this fix. The Fix
will not load and slows down everything when it trys to install on
I've discovered some useful info about this bug. First, there's a forum
thread about it with lots of good info: https://ubuntu-
mate.community/t/20-04-display-issues-with-amd-gpu/21648/37
Second, a new workaround. To recap, the first workaround I found was
booting with nomodeset, but that
Today I had some more time to play around with my computer so I tried
testing your hypothesis. I rebooted into my current software
configuration with no workarounds as a control, and reproduced the bug
as expected. Then I downgraded my system to the Marco version from 19.10
(1.22.3) by downloading
Now this is where it gets weird. Since I have Ubuntu MATE, I installed
the ubuntu-desktop package to get the default GNOME environment. I kept
my display manager as LightDM in case that's relevant.
Then I rebooted and tested all 3 desktop modes with default kernel
options. As expected, MATE is
A quick update. I tested to see if kernel version affects this bug, and
it appears not to. I booted up the previous installed kernel on my
system (5.3.0-55) without the default options and got the exact same
issue. Likewise, using the old kernel with nomodeset eliminates the
corruption at the
Public bug reported:
Today I upgraded from Ubuntu MATE 19.10 to 20.04. After doing so, Ubuntu boots
normally to the display manager (login screen) as expected. But once I log in,
everything on the screen is cut up into horizontal slices, with each slice
offset farther right than the slice
Similar activity on 440 version of drivers.
--
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/1774359
Title:
could not find module by name='off'
To manage notifications
fwiw, the behavior you're describing is done in the window-manager (not xterm).
Perhaps it's got some problem to be investigated.
--
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:
A workaround is to install https://developer.nvidia.com/cuda-
downloads?target_os=Linux_arch=x86_64_distro=Ubuntu_version=1804_type=debnetwork
--
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/ubuntu/+source/linux/+bug/1822482 seems also
to be related.
--
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] Automatic
Ubuntu 20.04 would be pre-release (end of April), and as such doesn't affect
"multiple users".
If there's a valid (not created by Ubuntu) bug, it would be in Debian, since
Ubuntu provides
no improvements to any program that I work on.
--
You received this bug notification because you are a
Public bug reported:
There is a bug in mesa version 19.2.x where x>2, manifesting itself as
window contents in large windows on 4K display renders with an incorrect
vertical offset, making the desktop largely unusable for some customers.
The bug is fixed in latest 19.3 series and 20.0 rc series,
That's due to a window manager change, and since Ubuntu is a few years
behind in xterm versions, it won't be fixed in Ubuntu 18.
--
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/1860577
Title:
So...
You made me question what could have happened if the libraries were not
the cause of KDE's behavior change. You already told me you thought KDE
was involved and indeed it was. The upgrade caused a deactivation of
composition enabling at startup, with a big warning message saying that
it has
In the log "apt-upgrade-libdrm2-no-gnuplot", gnuplot has been entirely
uninstalled :(
As for libgl1-mesa-dri :
$ apt-cache policy libgl1-mesa-dri
libgl1-mesa-dri:
Installed: 19.0.2-1ubuntu1.1~18.04.1
Candidate: 19.0.2-1ubuntu1.1~18.04.1
Version table:
*** 19.0.2-1ubuntu1.1~18.04.1 500
After having gnuplot uninstalled, trying to downgrade libdrm2 is worse
than ever: apt wants to uninstall 3/4 of my desktop environment.
** Attachment added: "apt-upgrade-libdrm2-no-gnuplot"
Radeon module blacklisted: nothing changed.
$ lsmod | grep radeon
$
--
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/1829872
Title:
No more desktop effects since libdrm upgrade in Bionic
To
> did you change any settings to make it use radeon instead?
No changes since the initial installation/configuration. It (normally)
defaults to the radeon. radeon module blacklisted. I'll come back later
with results.
> and to solve the downgrade issue, try uninstalling gnuplot
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1829872/+attachment/5269247/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libdrm in Ubuntu.
It seems apport-collect cannot produce a useful result for now:
dpkg-query: no package matches libdrm
And I couldn't change the affected package to be libdrm2 instead.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libdrm in Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1829872/+attachment/5269245/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libdrm in Ubuntu.
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1829872/+attachment/5269244/+files/Lsusb.txt
--
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/1829872
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1829872/+attachment/5269246/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libdrm in Ubuntu.
apport information
** Attachment added: "xdpyinfo.txt"
https://bugs.launchpad.net/bugs/1829872/+attachment/5269254/+files/xdpyinfo.txt
--
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/1829872
apport information
** Attachment added: "Xrandr.txt"
https://bugs.launchpad.net/bugs/1829872/+attachment/5269253/+files/Xrandr.txt
--
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/1829872
> And it took almost two weeks for you to notice this after the upgrade?
No. I noticed it immediately. However, since most of the time fixes come
within
a few days, I did not report the bug at the time, thinking I wasn't the
only one
with that desktop behavior.
> note that there
apport information
** Attachment added: "XorgLogOld.txt"
https://bugs.launchpad.net/bugs/1829872/+attachment/5269252/+files/XorgLogOld.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libdrm in Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1829872/+attachment/5269250/+files/UdevDb.txt
--
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/1829872
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1829872/+attachment/5269249/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libdrm in Ubuntu.
apport information
** Attachment added: "XorgLog.txt"
https://bugs.launchpad.net/bugs/1829872/+attachment/5269251/+files/XorgLog.txt
--
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/1829872
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1829872/+attachment/5269248/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libdrm in Ubuntu.
apport information
** Tags added: apport-collected bionic ubuntu
** Description changed:
Hello.
I upgraded my system on 2019-05-09 and since then desktop effects do not work
anymore. It installed
a new libdrm stack :
$ grep -A 3 "2019-05-09 *08:53:53" /var/log/apt/history.log |
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1829872/+attachment/5269243/+files/Lspci.txt
--
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/1829872
apport information
** Attachment added: "DpkgLog.txt"
https://bugs.launchpad.net/bugs/1829872/+attachment/5269242/+files/DpkgLog.txt
--
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/1829872
Timo, indeed I enable several repositories : backports and proposed updates
among them. I like to have a system with as recent softwares as possible (at
home I use debian testing) and see if
everything is ok, report bugs when needed (like "now" ;) for this one. I'm
usually quite impressed
by
Here is the output of journalctl...
** Attachment added: "Results of "journalctl -b 0""
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1829872/+attachment/5268869/+files/journalctl-b.0.log
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed
Public bug reported:
Hello.
I upgraded my system on 2019-05-09 and since then desktop effects do not work
anymore. It installed
a new libdrm stack :
$ grep -A 3 "2019-05-09 *08:53:53" /var/log/apt/history.log | tail -n 1 | awk
-F "," '{for(i=1;i<=NF;i++){print $i}}' | grep -A1 libdrm
** Changed in: qemu
Status: Fix Committed => Fix Released
--
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/1815889
Title:
qemu-system-x86_64 crashed with signal 31 in
Nothing new comes out in the crash report.
When I visit
https://errors.ubuntu.com/user/1d81a00d35531ca846cc8b470c853c9c4cc299c3a0a42040e68da92210168a3d96818f5de95d8f7d85e66516d77e481a6259123145189d1685f6d22ac584114a
the most recent report is:
Public bug reported:
This will possibly be a duplicate of Bug #1820028
I was trying to report a frozen GUI over SSH. This is the second report
that apport-cli generated when I ran it with xdm as the target package.
The symptoms I see are that I started running a go test last night and
my GUI on
Public bug reported:
This will possibly be a duplicate of Bug #1820028 or Bug #1820029 or Bug
#1820030
I was trying to report a frozen GUI over SSH. This is the second report
that apport-cli generated when I ran it with xorg as the target package.
I made three four reports to see if different
I can confirm this bug with Manjaro (xorg-server 1.20.3-1, KDE 5.14.5)
and onboard-1.4.1-4. The Workaround 'setxkbmap de' is ok for my needs,
but I'd rather help to fix the bug...
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in
** Changed in: xserver-xorg-video-qxl (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1810913
Title:
xorg w. QXL driver crashes while using
** Changed in: xorg-server (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1810913
Title:
xorg w. QXL driver crashes while using Intellij
this is all very confusing ... i hope this is the right link.
https://errors.ubuntu.com/oops/c098662c-132a-11e9-8e47-fa163e6cac46
--
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/1810913
Public bug reported:
i try to have development VM on my home machine. everything is fine, i use
spice/QXL and virt-manager and spice agent for resizing the desktop.
surfing w. firefox is working fine and all the x apps i triad are ok.
but shortly after starting IDEA or PyCharm X crashes the
Should this also work with Kubuntu 18.04 with SDDM instead of GDM3?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-settings in Ubuntu.
https://bugs.launchpad.net/bugs/1778011
Title:
SRU: PRIME Power Saving mode draws too much power
** Changed in: xterm (Ubuntu)
Status: New => Fix Released
--
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/1236530
Title:
xterm -e ... -v causes xterm to exit
To manage notifications
updated successfully and issue solved for apps. issue was in apps like
Telegram Desktop, Back in Time, Mixxx, Firefox and some others..
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
*** This bug is a duplicate of bug 1746740 ***
https://bugs.launchpad.net/bugs/1746740
Sure. I guess I was confused or misunderstood because the last comment
in the other bug says it is closed and to make a new bug.
--
You received this bug notification because you are a member of Ubuntu-X,
Public bug reported:
Related to
https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1746740
I would like to see this fix shipped in 18.04.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libinput10 1.10.4-1
ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
Uname: Linux
Hi there,
I fear that I do not have the time to do such in-depth debugging atm. As I
said, I used the latest kernel with my previous 17.10 install without this
problem, and it occurred with the first kernel of the 18.04 release. I know
that it would be easier for you to know the specific
Tested it with 4.17.0-041700rc6-generic, the bug still exists.
** Tags added: kernel-bug-exists-upstream kernel-bug-exists-
upstream-4.17.0-041700rc6-generic
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
Hi Christopher,
ad 1: 17.10
ad 2: I cannot check that, sorry. My boot partition is so small (only 256mb,
happened when I first installed ubuntu on this machine in 2013 for whatever
reason), so i have to uninstall the older kernels immediately after updating in
order to be able to install
See photo of the screen attached.
** Attachment added: "IMG_20180514_224101.jpg"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1771204/+attachment/5139476/+files/IMG_20180514_224101.jpg
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
Public bug reported:
My laptop was running fine for years, but after the latest update to 18.04 and
the reboot there were horizontal lines everywhere. It seems like its a
regression of an older bug, because its the same bug with the same strange
behaviour as listed here:
** Changed in: xserver-xorg-video-nouveau (Ubuntu)
Status: Expired => New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-nouveau in Ubuntu.
https://bugs.launchpad.net/bugs/1675024
Title:
nouveau fails with orange
Thanks to the instructions posted by @cjjefcoat I was able to get 116 up
and running on my machine. The only difference was that after purging
the toolchain ppa I had to run update-alternatives to get gcc to point
to gcc-5.
--
You received this bug notification because you are a member of
I purged the -116 packages and then re-installed them but it didn't
help. What's worse, is that now Unity doesn't work in -112, but
fortunately my Gnome session still works fine.
Here are the commands I executed to reinstall the -116 kernel:
sudo apt-get purge linux-image-4.4.0-116-generic
sudo
Public bug reported:
Ist schon häufiger aufgetreten.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libinput-bin 1.6.3-1ubuntu1~16.04.1
ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
thank you #3
But it is more about having wayland as default and not beeing able to
use gparted withing 18.04 LTS!
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to wayland in Ubuntu.
https://bugs.launchpad.net/bugs/1744372
Title:
gparted does
I added wayland becauce there is no problem with Xorg-Windowsmanager
only with (default) wayland and the suggested workaround with xhost +
** Also affects: wayland (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu-X,
Public bug reported:
Ist schon mehrfach aufgetreten.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libinput10:amd64 1.6.3-1ubuntu1~16.04.1
ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-42-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
1 - 100 of 1620 matches
Mail list logo
