Michael Schmitz, the problem you are reporting is an upstream one. Could you
please gather the required debugging information from
https://nouveau.freedesktop.org/wiki/Bugs/ and report this to upstream via
https://bugs.freedesktop.org/enter_bug.cgi?product=xorg :
Component: Driver/nouveau
Versio
Christopher,
Am 21.05.2018 um 15:58 schrieb Christopher M. Penalver:
> Michael Schmitz:
>
> 1) To clarify, you tested the 64-bit variant (not 32-bit)?
Correct.
> 2) Is using the nv driver still a usable WORKAROUND?
>
Sorry, didn't try that (is it even possible without installing from that
im
[Expired for libinput (Ubuntu) because there has been no activity for 60
days.]
** Changed in: libinput (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libinput in Ubuntu.
https://bugs.launchpad.net/
Michael Schmitz:
1) To clarify, you tested the 64-bit variant (not 32-bit)?
2) Is using the nv driver still a usable WORKAROUND?
** Description changed:
Binary package hint: xserver-xorg-video-nouveau
Expectation: Default Xorg driver should work with no video artifacts.
Observation
Hi Christopher,
still the same problem as before.
Cheers,
Michael
Am 18.05.2018 um 16:58 schrieb Christopher M. Penalver:
> Michael Schmitz, to confirm this is still a problem in Ubuntu, could you
> please test http://cdimage.ubuntu.com/daily-live/current/ and advise to
> the results?
How can I switch to Wayland? Contrary to the articles those tell
otherwise, I have no option to select it on the login screen.
Anyway, 17.10 worked fine with Wayland, so switching back to Wayland
might probably help.
--
You received this bug notification because you are a member of Ubuntu-X,
whi
Is that fixed in 1.10.7? :)
https://lists.freedesktop.org/archives/wayland-
devel/2018-May/038187.html
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libinput in Ubuntu.
https://bugs.launchpad.net/bugs/1767559
Title:
Provide libinput 1.10.6
Please help us to progress this issue by reporting it to the libinput
developers here:
https://bugs.freedesktop.org/enter_bug.cgi?product=wayland&component=libinput
and then let us know the ID of the new bug.
** Changed in: libinput (Ubuntu)
Status: New => Incomplete
--
You received thi
This looks relevant. Xorg is saying:
[ 2402.232] (II) AIGLX: Screen 0 is not DRI2 capable
[ 2402.232] (EE) AIGLX: reverting to software rendering
Are you able to log into Wayland sessions?
** Summary changed:
- Software rendering is forced after 18.04 upgrade
+ Software rendering is forced af
This bug is closed. If you continue to experience any problems then
please open a new bug by running:
ubuntu-bug mesa
or
ubuntu-bug nvidia-graphics-drivers-390
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launch
Fix from #1767468 also doers not work for me. Intel HD 520
--
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/1752938
Title:
Upgrading Ubuntu 18.04 disables GPU hardware acceleration
To manage noti
I have the same as @shankao.
--
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/1753663
Title:
[Mesa 18.0 + nvidia-390] No 3D acceleration, using llvmpipe
To manage notifications about this bug go
Public bug reported:
I did a minimal install of Ubuntu 18.04. Initially, although apt
claimed that gparted was already installed, the binary didn't seem to
exist. I removed it and reinstalled it, but it seems to be missing
dependencies:
Running "sudo gparted":
/usr/sbin/gpartedbin: error while
** Description changed:
# Summary
* Some glyphs badly drawn at some moments.
* When happens, same glyph drawn on various windows shows same corruption.
* Problem comes and go.
-
- Cannot use nvidia proprietary driver as a workaround (does not work at
- all).
# Context
Laptop, using
gouri, to see if this is resolved in your release, could you please
update your HWE stack as per
https://wiki.ubuntu.com/Kernel/LTSEnablementStack and advise to the
results?
** Attachment removed: "panel-corrupted.png"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/+attachment/469
I just wanted to add two new notes to this bug report:
1. When I reported it, I was using a beta of 18.04, right-click didn't
work either by clicking on the area of the trackpad that is supposed to
be reserved for right-click or by using two-finger click. The former is
still true in the full rel
To add to my latest comment where I report that problem reappeared a few
times in recent days: same hardware, same usage pattern, on the very re-
installation of 16.04 that had the problem disappear (cf. #comment:77).
Software updates applied regularly since the last near-2-years. Nothing
salient w
Interestingly, thus bug started to reappear in its extreme form: a few
times in the past days, all letters disappeared in my xfce4-terminals.
Workaround was to close and reopen session.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubun
oups sorry wrong place...
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xinput in Ubuntu.
https://bugs.launchpad.net/bugs/1768169
Title:
touchscreen doesn't work properly after stylus detection
To manage notifications about this bug go to:
By disabling the Gesture parameter for my touchscreen multitouch is
working. But no more pinch to zoom or to finger to scroll ... no more
Gestures !
Both should be able to work together.
Should I open an issue ?
--
You received this bug notification because you are a member of Ubuntu-X,
which i
Anupam Datta, to advise, one may test for this in a live environment to
see if this is reproducible.
** Summary changed:
- Screen flickering, whenever went to lock, waking up creates problem.
+ [HP ENVY Notebook - 15-ae008tx] Screen flickering after screen lock timeout
** Tags added: bios-outdat
(on wayland I do get the intel drivers, but wayland has other problems)
--
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/1755097
Title:
LIBGL_ALWAYS_SOFTWARE=1 renderer used instead of Intel on Xo
I've purged nux-tools, and /etc/X11/Xsession.d/50_check_unity_support is
gone, but after a reboot, I still get
$ glxinfo | grep renderer
GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer,
GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer,
Extended renderer info (GLX_MESA_
After 16.04 this happened. Also there is no such issue with Windows 10
I can't install a new image. I need to take whole lot of back up.
--
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/1761549
Titl
product: HP ENVY Notebook (M9V81PA#ACJ)
product: 80DD
product: Intel(R) Core(TM) i7-5500U CPU @ 2.40GHz
product: 16KTF1G64HZ-1G6N1
product: 16KTF1G64HZ-1G6N1
product: Broadwell-U Host Bridge -OPI
product: HD Graphics 5500
SMBIOS 2.8 present.
55 structures occupying 2932 bytes.
Table at 0x9BE7E000.
Handle 0x, DMI type 0, 24 bytes
BIOS Information
Vendor: Insyde
Version: F.45
Release Date: 05/23/2017
Address: 0xE
Runtime Size: 128 kB
ROM Size: 6144 kB
Ch
26 matches
Mail list logo
