Under 14.04.2, it is completely impossible to install the OpenGL Utility
Library (GLU) development files. This is a showstopper if you do OpenGL
development make use of GLU, something that is very often the case.
In 14.04.1 this worked without a hitch, one could install libglu1-mesa-
dev
I'm seeing exactly this behaviour with nvidia-346 (from xorg-edgers,
because I urgently need libGLESv2.so which is NOT included in the
nvidia-331 packages for amd-64; a bug) and nvidia-340 (same reason) on
kernel 3.13.0-45 and Ubuntu 14.04
I can get bumblebee working on this setup, and can
On my Ubuntu 14.04 setup I am definitely seeing an interaction between
using the spread function and whether windows maximize correctly or not.
However, it is slightly different from the OP.
It very often happens that a window shows the incorrect behaviour (i.e.
maximizing does NOT merge its
I'm copying a part of my comment on bug #509180, because in fact what
I'm seeing on my systems is what's described in this bug report here.
In short, I'm also seeing the 0-length lower file on ext4 leads to IO
Error in mounted ecryptfs bug. It's truly shocking that Ubuntu 12.04
LTS is shipping
For those of you seeing specifically the 0-length lower file resulting
in IO errors in the mounted ecryptfs filesystem, please go to the report
for that: bug #957843 -- remember indicate that the bug affects you, and
to subscribe to it. (both will increase the bug heat)
--
You received this bug
It seems like this bug (also see duplicate
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/529002 ) is
unfortunately still very much present on 12.04.
$ uname -a
Linux cpbotha-e6410 3.2.0-24-generic #38-Ubuntu SMP Tue May 1 16:18:50 UTC 2012
x86_64 x86_64 x86_64 GNU/Linux
$ find
I'd like to add a hopefully useful data point.
I've installed bamfdaemon, libbamf and libbamf3-0 version 0.2.116 from
https://launchpad.net/~unity-team/+archive/staging/+packages on an up-
to-date 12.04 AMD64 installation.
1. The new bamf indeed solves the problem where I start Chrome, and then
correction: In case #2, Chrome proper is grouped incorrectly with the
FIRST started application shortcut icon, not the last.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/692462
Title:
unity
In the released 12.04, vim-gnome, started from gnome-console,
unfortunately keeps its own menubar when maximized, instead of merging
with global. Starting gvim with -f fixes this behaviour.
gvim when started from searching in the dash shows the correct
behaviour.
--
You received this bug
I'm having the same problem:
The following packages have unmet dependencies:
qt4-dev-tools: Depends: libqt4-core (= 4.3.2-0ubuntu3) but 4.3.2-0ubuntu3.1
is to be installed
E: Broken packages
in other words: ME TOO!
--
qt4-dev-tools should depend on qt4-doc otherwise the assistant do not
Whoops, please ignore my ignorant whining.
https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/162836 describes
how to fix this (the problem, not my ignorant whining, that's not
fixable!)
--
qt4-dev-tools should depend on qt4-doc otherwise the assistant do not work
I've checked and double checked, it does seem that I can suspend and
resume (with about 66.6% success rate) with the new fglrx 7.12 release.
On this HP NC 8430 with X1600 mobility, I have an up to date Gutsy
install with the latest ATI drivers installed via Envy. Setting
@David McNally:
As far as I can see from http://ati.amd.com/support/drivers/linux/linux-
radeon.html version 7.11, released on November 21 2007, is the latest.
According to a number of reports earlier on in this thread, this driver
does NOT fix the problem.
Could you double-check? Which version
@Philipp Kern: There is no open source support for the X1600.
@Timo Jyrinki: Please stop with the apologetics.
1. Desktop effects DO work on fglrx, but you have to go the Xgl+Beryl path (I
tested this on 7.04).
2. *WHO* exactly is going to stop wasting their time with workarounds and work
on
See the announcement of the Ubuntu 7.10 Release Candidate:
http://www.ubuntu.com/testing/710rc
The fact that suspends with fglrx cause hard crashes is not even
mentioned. However, intermittent lockups with i810 are mentioned,
along with a workaround.
I have the feeling that ABSOLUTELY NOBODY
I can confirm that 2D operations are somehow also affected
(significantly slower). This is yet another reason why removing the
fglrx kernel module is not really a workable solution.
--
[gutsy] Suspend to Ram does not work on Z61m
https://bugs.launchpad.net/bugs/121653
You received this bug
*** This bug is a duplicate of bug 121653 ***
https://bugs.launchpad.net/bugs/121653
** This bug has been marked a duplicate of bug 121653
[gutsy] Suspend to Ram does not work on Z61m
--
suspend/hibernate failure (gutsy and fglrx)
https://bugs.launchpad.net/bugs/134819
You received this
Terry, I like the way you think, this would definitely be the way to go!
However, I'll bet you a beer (heck, make that two if you ever end up in
my neck of the woods) that this doesn't get officially fixed before
Gutsy gets released. :) There is too little time, I've seen irc logs
where
I am seeing the same behaviour on an HP NC8430 laptop (ATI X1600, Core
Duo T2500, Gutsy Gibbon up to date on 2007-10-02, fglrx
7.1.0-8.37.6+2.6.22-12.4). Both suspend and resume don't even get to
the flashing power light (this is how my laptop shows that it's in ACPI
S3 suspend) stage, but
I understand that one is dependent on ATI for a fix. However, isn't it
wise to include at least SOME kind of workaround or documentation in
Gutsy concerning this problem? Will anyone even get around to that
seeing that this bug has been classified wishlist ?
It really makes a fantastic
This is the path I'm planning to take (seems to be the only alternative
on X1600 if you want full resolution), but as I said in my first post, I
*need* the GPU (3D acceleration) support. Also, some sane default
should be implemented, as fglrx + SLUB + suspend/hibernate guarantees a
hard crash
I can confirm this bug with a Palm Tungsten C and the Ubuntu Feisty beta
(up to date as of 2007-03-10). EToDo continues forever, the palm pilot
times out eventually. Disabling the EToDo conduit allows the sync to
complete successfully.
--
[feisty] etodo conduit times out when syncing with a
22 matches
Mail list logo
