Same problem. Ubuntu 18.04, LTS-13.16
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1786197
Title:
stack 1.5.1 broken on 18.04 (AesonException)
To manage notifications about this bug go to:
https:
Public bug reported:
Upgrade failure with the following error message:
package apache2 2.4.18-2ubuntu3.1 failed to install/upgrade: subprocess
installed post-installation script returned error exit status 1
1) Ubuntu release version:
Description:Ubuntu 16.04.1 LTS
Release:16.04
2)
Before you close this, please verify that the Second Life / Snowglobe
client works too, because even on Karmic Mesa bits that allowed my
example program to run correctly, the SL client still triggered this
bug. You may have to manually enable VBO from the preferences dialog to
trigger it. I can't c
I have this issue on my Acer Extensa 5635G. Looking at the Xorg.0.log,
it seems that the proper mode of 1366x768 at 60Hz is being discarded
with this motivation:
Mode is rejected: This mode's horizontal sync end (1446) exceeds the
horizontal total size (1437).
After some experimentation, the fix
I should add that the touchpad on this laptop came covered with a
sticker explicitly advertising multi-touch gestures.
--
two-finger scrolling does not work on Acer AO531h
https://bugs.launchpad.net/bugs/44
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
This bug affects my Acer Extensa 5635G-664G32Mn running up-to-date
Karmic amd64. Setting the pressure to 40 makes two-finger scrolling
work here too; i.e. running:
xinput set-int-prop "SynPS/2 Synaptics TouchPad" "Synaptics Two-Finger
Pressure" 32 40
--
two-finger scrolling does not work on Ace
Here is a small program that triggers the problem on my machine (Esprimo
U9200, Intel C2D, GMA965) running up-to-date Karmic amd64. As far as I
can tell from testing and reading the VBO spec, this should work, but
with VBO element arrays on the above machine it does not. Further
details in the he
Not sure if this is of any use, but I get this on up-to-date Karmic (as
of 2009-10-29) on a GMA965 when my OpenGL renderer attempts to draw
geometry using VBO element arrays.
Playing around with my buffer pool allocator, it seems the "target" ID
corresponds to the buffer object used for elements.
is problem, HIMO, is very important. My hd risked to be seriously damaged. I
rescued it running a small utility on the "windows side" of my notebook.
I hobe can be fixed as soon as possible.
My log files can help?
where find them?
tank you
--
Camilla (Italy)
--
USB stops working on To
