does it right (tested with the same file). Any ideas what
couldbe wrong?
Ciao, Stormking
--
No subpixel rendering
https://bugs.launchpad.net/bugs/80921
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu
@Tobias Wolf
I installed the latest patched versions of libpoppler, libcairo and
evince from your PPA but evince still does not use subpixels. Are there
any config files I need to edit or something?
--
No subpixel rendering
https://bugs.launchpad.net/bugs/80921
You received this bug
It's enabled, by default. To disable it, you can:
- set 'unix extensions = no' in smb.conf on the server
or
- add 'nounix' to the mount options on the client
or
- set '/proc/fs/cifs/LinuxExtensionsEnabled' to '0' on the client.
--
Creating a file on a mounted samba share creates thousands
I have a very similar problem when using a samba share.
The remote folder is mounted via fstab. When Unix Entensions are
enabled, creating a new empty file via the nautilus context menu results
in thousands of new files (I haven't counted, I allways killed nautilus
after a while).
But that's not
Public bug reported:
Binary package hint: gvfs
The remote folder is mounted via fstab. Creating a new empty file via
the nautilus context menu results in thousands of new files (I haven't
counted, I allways killed nautilus after a while).
But that's not the main problem because I don't create
It's a simple samba share physically located on my old 300MHz desktop
computer that I now use as a file server. The share is mounted on my
laptop via fstab using cifs. Both machines are running Ubuntu 9.04.
Samba (on the server) is 3.3.2.
Triggering the bug is done by mounting the share with Unix
@gator:
For the white noise to disappear, you just need to turn the brighness
down by 4-5% (on the XVideo overlay, not your TV). It's there because TV
standards seem to have slightly less brightness levels than RGB, so
everything brighter than the brightest allowed color produces errors.
Maybe
*** This bug is a duplicate of bug 284408 ***
https://bugs.launchpad.net/bugs/284408
es, it is on all the necessary peoples' radars. However the ball is in
ATI's park now.
Yeah, I was afraid of that. Last time there was a showstopper bug in the
driver, it took them two years to fix it.
Please confirm that you are testing with the 8-11 driver from
intrepid-proposed not the 8-10.
I tested the 8.11 driver, yesterday. I used the installer from the AMD
website. The error is still the same.
I got a Mobility Radeon 9700.
--
r3xx Hardware does not work with fglrx [EPR#257839]
*** This bug is a duplicate of bug 284408 ***
https://bugs.launchpad.net/bugs/284408
Still the same with fglrx 8.11 (8.552).
dmesg gives:
[ 1137.291557] [fglrx] Maximum main memory to use for locked dma buffers: 1169
MBytes.
[ 1137.293424] [fglrx:drm_alloc] *ERROR* [driver] Allocating 0
And? What happens next? Will someone from Ubuntu call ATI or will we
have to wait till november?
--
Unable to load module fglrx: cannot allocate memory
https://bugs.launchpad.net/bugs/283836
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Me too! On a Mobility Radeon 9700.
After reading about an X Server 1.5 compatible fglrx beta being
available in Intrepid, I finally ugraded my system (I always do a few
weeks before the official launch). Stupid me. How could I *not* assume
that ATI would mess up support for my Mobility Radeon?
12 matches
Mail list logo
