This still happens in Ubuntu 14.04 LTS: My wife got a brand new Apple iPod nano
touch as a birthday present.
Rhythmbox says when trying to initialize the device: "Unsupported checksum
type".
The device is visible though and it is possible to browse the directory
structure in file manager.
Is t
Today I installed the 10.4-beta1 64 bit on a test machine.
Steps to repoduce: install on computer with NVidia graphics card. Install
nvidia driver.
Select Preferences->Appearance->Visual Effects. Switch from None to Normal.
Compiz
gets started but the gnome-appearance-properties process freez
Hi Craig,
from the information you submitted it is not obvious, which version of
Ubuntu and more precisely which version of libpoppler you used.
>From the Ghostscript version 8.62 I guess it is 8.10 (Intrepid).
eog uses libpoppler which suffered from this now fixed bug.
Did you install the fixe
to get these client system back online in
acceptable time, pressing the hard reset switch was often the only
choice I had. This was with SuSE Linux, Red Hat, Debian and Ubuntu
systems in several different versions.
> If you do fill a new bug report, please let me know.
> Thanks in advance,
di
version
ii libpoppler3 0.8.7-1ubuntu0.1
installed. That solved the problem with printing larger images for me.
Thanks again!
Regards, Peter
--
Peter Funk, ✉Oldenburger Str.86, D-2 Ganderkesee
office: ArtCom GmbH, ✉Haferwende 2, D-28357 Bremen, Germany
tel:+49-421-20
Today I tried to print two 3449x2480 JPEG images using gthumb.
This failed with a very similar error
"Error: /limitcheck in --array--" printed instead of the images.
Printing same sized images used to work on Hardy on the same printer.
The file that ended up in the /var/spool/cups directory now
** Also affects: gthumb
Importance: Undecided
Status: New
--
Array too big when printing large image
https://bugs.launchpad.net/bugs/311982
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to poppler in ubuntu.
--
desktop-bugs mai
The problem (umount of a NFS volume of a disappeared NFS server is stuck in the
kernel)
has nothing to do with a particular filemanager. This is only one possibility
where the
symptoms of the problem surface.
I think this problem should be reported as a bug in the package nfs-common or
the
L
