why is this fix not released?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1540084
Title:
xfig crashes when moving a point of an arc
To manage notifications about this bug go to:
hat really failed... Oh well...
I hope that this was a useful post.
GJS
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1716184
Title:
failure of xrandr to find any outputs
To manage notificat
I got the bios upgraded, but the problem has not gone away.
I hope someone would look into this problem. The machine is usable, but I
cannot
access any display output except default, as described in the the original bug
report. I can demonstrate that the hardware is correctly working by
16.04.3 LTS
Release: 16.04
Codename: xenial
uname -a
Linux gjs-yoga 4.11.0-14-generic #20~16.04.1-Ubuntu SMP Wed Aug 9 09:06:22
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
Until recently things worked quite well. But on August 26 I got an update
from Ubuntu and
things began
:16.04
Codename: xenial
uname -a
Linux gjs-yoga 4.11.0-14-generic #20~16.04.1-Ubuntu SMP Wed Aug 9 09:06:22 UTC
2017 x86_64 x86_64 x86_64 GNU/Linux
Until recently things worked quite well. But on August 26 I got an update from
Ubuntu and
things began to decay.
In particular, I can
Having this issue for the longest time, and amazed that something basic
like this does not get solved, I have found a possible workaround that
solves this for me: Instantbird 1.0
http://www.instantbird.com/
I have sound now..
--
You received this bug notification because you are a member of
I also have a T42 and recently upgraded to 10.10 from 10.04 and had the
same problem - on resume I would have a TTY login appear, but no
recognition of the keyboard. I would hold the power button and force
the laptop to restart or shutdown.
If you follow the diagnostic process on this wiki:
Stumbled upon this thread b/o system filling up to 100% slowly without clear
reason.
I second the last report by jason, similar issue, the .xsession-errors was
huge, removed it.
Amazing this issue still exists (or reoccurs)
yet slowly but surely the filesytem fills up with a MB per 1-3
