Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: libinput (Ubuntu)
Status: New => Confirmed
--
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/1696929
T
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-shell (Ubuntu)
Status: New => Confirmed
--
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/1696929
Public bug reported:
Trackpad doesn't seem to be recognised. No multi touch or two finger
scrolling. Samsung XE700T.
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: xorg 1:7.7+16ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
Uname: Linux 4.10.0-22-generic x86_64
ApportV
Hello Timo, or anyone else affected,
Accepted mesa into zesty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/17.0.7-0ubuntu0.17.04.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://w
Oh, BTW, to be ry clear - I didn't provide (or do) any work on this
experimental (always consider it experimental) kernel - just the link to
it. I only found it through a Phoronix article and used it to test.
Thank M-bab for his hard work. :-)
--
You received this bug notification because you ar
I just checked on Phoronix, AMD's DC stack has not been accepted for
kernel 4.13 - so very unlikely to make it into Ubuntu 17.10. Maybe AMD
steps on it they get it into kernel 4.14 at the earliest. The basic
(overly simplistic) problem is how it's coded and would make it a total
nightmare for t
Whoa, hold up - it *may not* be. The kernel main line developers have
rejected the code for various reasons. Untill it's acepted mainline,
it's not a part of the kernel. Read the readme on the github site. AMD
has to make changes to DC (formerly known as DAL) to be accepted. So
anyone using the
so, even a no-change rebuild is bad... this is completely unrelated to my fix
then.
Will try to have a look tomorrow
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libepoxy in Ubuntu.
https://bugs.launchpad.net/bugs/1698233
Title:
New libepo
I removed the libepoxy0 package holds, added the LocutusOfBorg
repository, and did an apt-get update and apt-get dist-upgrade. However
my system still hung on reboot. If I did something wrong please let me
know.
Also the problem only occurs with AMDGPU-PRO, I should have been clear
about that. Unf
Public bug reported:
It happens after an update
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: xorg 1:7.7+16ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15
Uname: Linux 4.10.0-24-generic x86_64
.tmp.unity_support_test.0:
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: am
Public bug reported:
1
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: xorg 1:7.7+16ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15
Uname: Linux 4.10.0-24-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: amd64
CompositorRunning: None
Date: Wed Jun 21 00:10:12
Good news everyone!
I have been trying the kernel with amd-staging provided by
nukedathlonman and it totally works! The system boots up to a completely
functional environment at full-resolution. I've also tried Team Fortress
2 and Rocket League and it's pretty damn close to Windows performance,
so
@Timo: No, it only hangs with amdgpu-pro. I initially tried changing to
amdgpu and the issue went away. I also tried the current amdgpu-pro
17.10, which also fixed this issue. Unfortunately both drivers don't
work as they should on my system, so installing them isn't a long-term
solution for me. Bu
Public bug reported:
I'm seeing issues with artifacts on the screen.
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: xorg 1:7.7+16ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15
Uname: Linux 4.10.0-24-generic x86_64
.tmp.unity_support_test.1:
ApportVersion: 2.20.4-0ubunt
Upstream kernel test - kernel 4.12-rc6
1. Used installation basis for 4.12-rc6: ubuntu 16.04.2, kernel4.8.0-36,
no updates
Result: "boot finished" sound after 50 sec.; ssh login possible
Booting a second time, using workaround parameters nomodeset xforcevesa:
some file system error message while
Upstream kernel test - kernel 4.12-rc6
1. Used installation basis for 4.12-rc6: ubuntu 16.04.2, kernel4.8.0-36,
no updates
Test results differ from rc1:
no "boot finished" sound, no remote login (ssh).
Reboot/shutdown by SysRQ keys after about 3 minutes possible.
Upstream kernels were installe
Public bug reported:
when trying to install software updates several problems occur.
BrokenCount>0 appears in the top of the screen
The software updater gives a message:
- Check if you are using third party repositories. If so disable them, since
they are a common source of problems.
- Furtherm
** No longer affects: systemd (Ubuntu Xenial)
** No longer affects: systemd (Ubuntu Yakkety)
--
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/1590590
Title:
Touchpad not r
Should a fix for this be backported to 16.10 and 16.04?
Are there people who have the relevant hardware available, and are willing to
test the fix on both 16.10 and 16.04?
I do not have the hardware available, thus without available testers I would
not want to upload this fix.
--
You received t
@Kai-Heng
Per request in #30, I installed version 4.10. Everything seems to be
working just fine now. First Kernel outside of 4.4.72 that has worked
for me.
rodavid@rodavid-Latitude-E7250:~$ lsmod | grep i915
i915 1449984 5
i2c_algo_bit 16384 1 i915
drm_kms_helper
Public bug reported:
screen go on and out
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: xorg 1:7.7+16ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15
Uname: Linux 4.10.0-24-generic x86_64
.tmp.unity_support_test.0:
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: amd64
Co
Public bug reported:
It seem that the update software will not install and keep give me this
information. Please report this bug against the 'update-manager' package and
include the following error message:
E:The package linux-image-extra-4.8.0-53-generic needs to be reinstalled, but I
can't fi
E.g. I uploaded a libepoxy that is the same as the xenial working one, just
rebuilt on top of new dependencies.
I would like to ask you to test it, just to make sure the eventual regression
is not coming from somewhere else
(e.g. a bug in the toolchain can be spot with a no-change rebuild)
please
Interestingly, I would add a question for you:
are you available to test some ppa libepoxy versions?
I admit, you are the first one reporting this issue, with a package that has
thousand installations.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribe
this problem is happenning to me as well, not only on ubuntu vm but also on
centos vm.
restart to the vm solves the problem.
but it seems to me like a virtual box issue.
i first thought it was only inside pycharm, and tried the following workaround:
http://youtrack.jetbrains.com/issue/IDEA-78860
Does it hang without amdgpu-pro? Note that it's not shipped with ubuntu
** Changed in: libepoxy (Ubuntu)
Assignee: (unassigned) => Locutus (locutus)
** Changed in: libepoxy (Ubuntu)
Assignee: Locutus (locutus) => LocutusOfBorg (costamagnagianfranco)
** Changed in: libepoxy (Ubuntu)
26 matches
Mail list logo
