For me the issue has not occurred since I upgraded to oneiric. As I do
not run other natty systems, we can close the bug. What about the
others?
Upstream doesn't seem willing to take on this one.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
I added an upstream bug report:
https://bugzilla.gnome.org/show_bug.cgi?id=661415
** Bug watch added: GNOME Bug Tracker #661415
https://bugzilla.gnome.org/show_bug.cgi?id=661415
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to vte
Is there maybe a hidden configuration option to make evince use another
backend (if such exist). Or are there currently no dconf backends except
memory?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evince in Ubuntu.
I have the exact same issue on final here:
During installation, I set the keyboard layout to german (de:nodeadkeys)
and already noticed, that the installer also used the default mapping
(us). After reboot the keyboard layout is us.
I tried installing console-data, which fixes the problem until
I just checked version 2.30.0 of evince which was installed by
debootstrap for lucid. The error still occurs in the same way it does
with 2.28.1 of karmic. Printing to a physical device as well as printing
to a PDF file both show the same erratic behaviour.
--
When printing, the page numbers are
Public bug reported:
Binary package hint: evince
I printed from a large PDF, which has prepending pages labelled with
roman numbers (i, ii, iii, iv...). In the current-page-box in the upper
left corner the page number displayed corresponds with the number
printed on each page. When I printed out
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/41826785/Dependencies.txt
** Attachment added: KernLog.txt
http://launchpadlibrarian.net/41826786/KernLog.txt
** Attachment added: RelatedPackageVersions.txt
I just found this bug report and am affected as well. I actually used
inears, when i psyched myself by an application turning master-volume
up. I've read the first few posts of the conversation mentioned by Janne
and it seems totally unintuitive to me. Is there a way to opt in favor
of changing
gnome-keyring-daemon does not export SSH_AUTH_SOCK here at all. I
already disabled ssh-agent in Xsession.options and after that also
disabled it in xinitrc, which was trying to start it as well. After
that, when there was no ssh-agent interfering with gnome-keyring-daemon,
SSH_AUTH_SOCK was not
