PS:
based on x11 log data (/var/log/Xorg.0.log) i tried out this:
sudo cat /dev/input/event6 | od -x
when moving the mouse new data arrived.
but no data arrived when hitting any button or when turning the mouse wheel.
checking other such input devices did not provide any
i am running a fresh install of Ubunutu 16.04.1 i386 on top of Virtual Box
5.1.6 using Win7 i386 as host.
(with FreeDos as a VB-client on the same system i have the mouse just working.)
the hosting machine is accessed via RDP.
tests with console switching did not show any improvement.
checks
this problem again confirmed for Ubuntu 16.04.1 on i386 during the
install into virtual box 5.1.6
the amount of people affected is assumed to be high and thus even if
there is a work around (but not anybody gets it fast enough how to solve
that but rather assume its just broken) it still would
just found this on the GCC thread:
Launchpad Janitor (janitor) wrote on 2018-03-19:#7
This bug was fixed in the package gcc-4.8 - 4.8.5-4ubuntu8
---
gcc-4.8 (4.8.5-4ubuntu8) bionic; urgency=medium
[ Matthias Klose ]
* Stop build gcj in current distro releases. Addresses:
switching to "beta" version of gcc (Ubuntu 7.3.0-5ubuntu1~14.04.york0) 7.3.0
and rebuilding the kernel modules in question for 4.4.0-116 seemingly did the
job.
is this really what you wanted from a good amount of the end users by
publishing those kernel?
** Summary changed:
- 4.4.0-116 Kernel
referenced by bug #1750937
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gcc-4.8 in Ubuntu.
https://bugs.launchpad.net/bugs/1749261
Title:
Add amd64/i386 retpoline support
Status in gcc-4.8 package in Ubuntu:
probably related to bug #1749261
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1750937
Title:
4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and
16.04)
having here gcc-4.8 (Ubuntu 4.8.5-2ubuntu1-~14.04.01) 4.8.5
and it does not honor either of the above listed switches but returns an error.
sounds a bit like a regression to me, a vanished feature.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
are you sure it has arrived with _some_ gcc version already.
publications indicate its very experimental still and i can not see any
of the typical switches beeing honored by the gcc versions on my
machine. (and i was able to switch them forth and back using "update-
alternatives") needless to
are you thinking of something like this?
https://launchpad.net/~jonathonf/+archive/ubuntu/gcc-7.3
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1750937
Title:
4.4.0-116
A bunch of updates went public - the AGESA component update is still due as its
pushed to the end user via the integration and qualification pipeline of the
board vendors. It got said this will take several weeks.
Maybe unrelated (but those communications channel might be worth watching for
related news):
Robert Hallock of AMD has announced a new beta driver for the chipset that
is/was available via google drive. It is said this fixes something relevant for
at least the game Destiny 2. As the test phase
AMD has pulled back their first BIOS/Microcode fix due to problems with
some boards switching down from PCI 4.0 to PCI 2.0 - the release
seemingly only went as far as the big board vendors. the board vendors
got order to not re-distribute that version in any form. sounds
reasonable to me. indeed
hey, i removed the "quiet" and did a bit of alternate outputs. the
action is 'start' for my failing 'xrdp'.
Job for xrdp.service failed because the control process exited with error code.
See "systemctl status xrdp.service" and "journalctl -xeu xrdp.service" for
details.
Could not execute
14 matches
Mail list logo
