Ok still a few tests later, I can say that some documents will print
(like pdf) but only when choosing the right combination of options. It
is for example not possible to print out more than one example a time.
Other applications will not print at all like LibreOffice. It is however
still possible
After a few tests it seems that I can print to this printer from the
printing dialog. Yet, the "Print test page" from the printer setup menu
will give me the error described in the bug report.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
I am facing the same problem. However, my printer is a Toshiba E-Studio
5520C. When I try to print I get the same result as in the description.
Even with another ppd file. Could you explain what you mean by "using
manufacturers driver downloaded from internet"?
Cheers
--
You received this bug no
I found a partial fix for these symptoms: When launching xrand in a terminal I
get the following output:
xrandr: Failed to get size of gamma for output default
Screen 0: minimum 320 x 175, current 3360 x 1080, maximum 3360 x 1980
default connected 3360x1080+0+0 0mm x 0mm
1440x900 50.0
I have the same bug here with an NVidia TwinView. I Use the left-most
screen (the attached one) as my primary, the laptop screen is on the
right and used as secondary screen.
Upon setting up the TwinView works just fine. It seems that the problem
appears when the screen is locked. Upon unlocking s
1. unity --reset didn't help for me. It solved the problem for a few minutes
but then it re-appeared. Once the problem is there it is easy to reproduce the
issue.
2. Same applies for a new user. At a first glance the problem is not there but
appears after a few minutes of use. Again, once the pr
I further "investigated" this bug since it re-appeared again after a few
minutes and finally found the problem. The bug only appears if the
application covergloobus is launched. As soon as I launch covergloobus
the "bug" appears and right after exiting the application everything is
back to normal.
Ok I tried with a newly created user and the problem disappears. Now it
would be interesting to know which setting caused this buggy behavior.
For testing purpose I renamed ~/.config, did a log-out and log-in and
the problem was away. This is kinda brute force solution. But lets say
that it was the
Same bug for me. It is a fresh installation of 11.04 on a macbook pro. The
problem was not there in the beginning, but this morning nautilus crashed
suddenly heavy and i had to force shutdown (the hw-way...) the machine. Since
then I struggle with the same problem. This is really annoying since
