The upstream bug has a patch that has been considered to work. Can this
be targeted for Karmic?
If so, can I as a tester help in any way? I have little to none
packaging skills, but I'm willing to spend a few hours if it will mean
that this patch will make it into Karmic (assuming it's not already
** Attachment added: "upstream patch - eds part"
http://launchpadlibrarian.net/30885841/gn206061_eds.patch
--
Evolution virtual trash / "real" trash on IMAP server
https://bugs.launchpad.net/bugs/13983
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which i
** Attachment added: "upstream patch - evo part"
http://launchpadlibrarian.net/30885863/gn206061_evo.patch
--
Evolution virtual trash / "real" trash on IMAP server
https://bugs.launchpad.net/bugs/13983
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which i
Worth monitoring:
https://gitlab.gnome.org/GNOME/shotwell/issues/4
https://bugzilla.redhat.com/show_bug.cgi?id=1584876
** Bug watch added: Red Hat Bugzilla #1584876
https://bugzilla.redhat.com/show_bug.cgi?id=1584876
** Also affects: shotwell (Fedora) via
https://bugzilla.redhat.com/show
*** This bug is a duplicate of bug 518056 ***
https://bugs.launchpad.net/bugs/518056
** This bug is no longer a duplicate of bug 228077
libgtk2 immodules has cedilla disabled in en locales
** This bug has been marked a duplicate of bug 518056
cedilla appears as accented c (ć instead of ç
*** This bug is a duplicate of bug 518056 ***
https://bugs.launchpad.net/bugs/518056
** This bug has been marked a duplicate of bug 518056
cedilla appears as accented c (ć instead of ç) when typing 'c
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, w
Please see bug #228077 for information on the report upstream rejected
for gnome-control-center.
Leandro, I don't have a US keyboard anymore (nor did a read all the
comments here), but if this is still an issue, I don't think a fix will
appear anytime soon.
Good luck on this.
--
You received th
*** This bug is a duplicate of bug 1069531 ***
https://bugs.launchpad.net/bugs/1069531
** This bug has been marked a duplicate of bug 1069531
Cannot login to Empathy after setting up Google online account
--
You received this bug notification because you are a member of Ubuntu
Desktop Bug
*** This bug is a duplicate of bug 1069531 ***
https://bugs.launchpad.net/bugs/1069531
** This bug has been marked a duplicate of bug 1069531
Cannot login to Empathy after setting up Google online account
--
You received this bug notification because you are a member of Ubuntu
Desktop Bug
*** This bug is a duplicate of bug 1069531 ***
https://bugs.launchpad.net/bugs/1069531
** This bug has been marked a duplicate of bug 1069531
Cannot login to Empathy after setting up Google online account
--
You received this bug notification because you are a member of Ubuntu
Desktop Bug
** Changed in: baltix
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/12893
Title:
Shouldn't put .Trash-$USER on removable devices
To manage notific
** Changed in: gvfs (Baltix)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
https://bugs.launchpad.net/bugs/206439
Title:
smb password protected share cannot be accessed
To manage notifications a
** Changed in: gnome-power-manager (Baltix)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu.
https://bugs.launchpad.net/bugs/135548
Title:
Action on critical bat
** Changed in: nautilus (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
https://bugs.launchpad.net/bugs/165113
Title:
gksudo nautilus won't set ownership/permissions on files below
I have since removed and re-added my gtalk accounts, and have been using
the workaround of bug #1069531 as often as required (killall
signonpluginprocess).
I don't know if this bug is related to bug #1069531. Maybe they are the
duplicates?
If this bug happens to me again, I'll try to find the tim
Also happens to me sometimes on Ubuntu.
** Also affects: empathy (Ubuntu)
Importance: Undecided
Status: New
** Changed in: empathy (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to emp
This bug is more than 10 years old, and all the other projects are
marked as Fix Released, so I just closed the last one (Baltix).
If you think it's still an issue and worth investigating, feel free to
reopen the bug. If this is the case, I suggest you reopen the bug in the
upstream bug tracker, w
You can recompile evince, same version you're using without any
changes to the source. It will be recompiled to use the newest
poppler. I did this to use poppler3 in hardy without any issues.
On Mon, Jan 19, 2009 at 1:21 PM, Vincenzo Ciancia wrote:
> The point is that the backported evince (using
** Also affects: gnome-keyring (Fedora) via
https://bugzilla.redhat.com/show_bug.cgi?id=454186
Importance: Unknown
Status: Unknown
--
no ssh-agent after resume from hibernate
https://bugs.launchpad.net/bugs/268141
You received this bug notification because you are a member of Ubuntu
*** This bug is a duplicate of bug 268141 ***
https://bugs.launchpad.net/bugs/268141
** This bug has been marked a duplicate of bug 268141
no ssh-agent after resume from hibernate
--
gnome-keyring-daemon cached passwords for SSH keys not working after hibernation
https://bugs.launchpad.ne
I can confirm that hyperair's workaround works, and it's better, since
it requires no user intervention, and it's easier for newbies.
I still believe that this is a bug, not a feature, since there appears
to be no obvious way to restart the g-k-m after a hibernation/suspend,
if the mentioned optio
On Sat, Jan 31, 2009 at 6:07 AM, hyperair wrote:
> On Sat, 2009-01-31 at 05:24 +, Bug Watch Updater wrote:
>> ** Changed in: gnome-keyring
>>Status: New => Fix Released
>>
> Well, it seems upstream fixed the issue in trunk. So we just have to
> wait for the next release of gnome-keyrin
On Sun, Feb 1, 2009 at 3:51 PM, hyperair wrote:
> On Sun, 2009-02-01 at 17:42 +, Christophe Sauthier (huats) wrote:
>> Thanks for your work here. The thing is that there is already a new
>> gnome-keyring version available (2.25.5.) which FTBFS for the moment on
>> jaunty. I am currently workin
I turned on the option to beep if problem occurs, and got a beep this
morning, with the new version, so it seems it's not fixed for me, also.
--
Suspends that are longer than 6 hours will inexplicably claim to fail, but not
really fail
https://bugs.launchpad.net/bugs/242713
You received this bug
I jut did.
http://bugzilla.gnome.org/show_bug.cgi?id=571425
It would help if someone (Sebastian?) could confirm if this
functionality is also missing in newer gnome versions, since I use Hardy
and 2.22.x is rather oldish.
** Bug watch added: GNOME Bug Tracker #571425
http://bugzilla.gnome.or
I confirm the UI that asks for logout works. I tested on a laptop and a
desktop, both on up to date Hardy installs.
However it seems rather intrusive to the configuring process, since it
doesn't even let the user finish configuring the share - it leaves the
share created with default settings, whi
To other newbies around, here's the procedure I used to confirm. Steps
1-4 are not required, but I wanted to be extra careful:
1- Purge samba, samba-common, libpam-smbpass, and re-install smbclient (which
pulls samba-common).
1'- remove the sambashare group
2- Logout, login
3- Try to create a use
Of course after so many steps, and logouts, I had to make some kind of
confusion. Please disregard the part in my first comment about the
intrusiveness of the UI - the share is *not* partly created with the
0ubuntu5 package, which is exactly what the bug report is about, duh.
Also, if it wasn't cl
You got it right, both on my sugestion and in the problem with it. What
made me think about this was Colin's 29 and 30 comments. Maybe what I'm
proposing is overkill, but let me try to clarify a bit.
I think if Bug 238224 gets fixed for hardy, and a one time silent call
to gksu makes libpam-smbpas
I can't reproduce it with hardy.
[EMAIL PROTECTED]:~$ apt-cache policy openssh-server
openssh-server:
Installed: 1:4.7p1-8ubuntu1.2
Candidate: 1:4.7p1-8ubuntu1.2
Version table:
*** 1:4.7p1-8ubuntu1.2 0
500 http://br.archive.ubuntu.com hardy-updates/main Packages
500 http://
Is it possible that the reporter suffered from some miscofiguration?
If the reporter needs to use ssh keys non-interactively, he could set a
password and use a ssh-agent.
--
ssh always asks to unlock private key with no password set
https://bugs.launchpad.net/bugs/187127
You received this bug no
On Sun, 2008-11-02 at 11:28 +, Sebastien Bacher wrote:
> the bug has been fixed upstream now
>
> ** Changed in: poppler (Ubuntu)
>Status: Triaged => Fix Committed
>
In what upstream version will it appear? Will the fix be backported to
hardy and/or intrepid?
regards
FF
--
[gutsy]
Added a kernel task to the bug.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
ALT+PrtSc not recognised: breaks built-in screenshot function
https://bugs.launchpad.net/bugs/642792
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
Nigel,
has the patch been committed to the Ubuntu package? I believe at this
point, no major merges will be done, and this will have to be approved
by release teams, so "fix committed" wouldn't apply. Please correct me
if I'm mistaken.
regards
FF
On Seg, 2010-04-19 at 14:06 +, Nigel Babu wro
It looks from the patch that it requires cairo 1.8.2, so it would
require a non-trivial backport for both hardy and intrepid. Could
someone who actually understands it confirm this, and decide if this
blocks an eventual SRU?
** Summary changed:
- [gutsy] [regression] Evince has very bad quality w
Geek2theCore escreveu:
> OK... i finally found the operative bug report (the duplicate) and that
> the sound thing is actually the sound: /usr/share/gnome-power-manager
> /gpm-suspend-failure.wav which is played on an error, so I just turned
> the error sound off in the Power Manager preferences. I
I think I found out how to work around this issue. Since an empty test
account didn't show the behaviour, I decided moving my dirs and files
out of ~ until I got f-spot to work. After a while of some trial and
error, I nailed it down to ~/.gnupg.
After that, I kept trying until I pinpointed the pr
Sebastien,
upstream says the patch was reintroduced a while ago. I still have this
issue in hardy.
--
strange font behaviour - connected letters
https://bugs.launchpad.net/bugs/128074
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to poppl
Even though it's not critical, I think it's important to fix this for
hardy. It's a very bad advertising for an otherwise very good
application (evince), and degrades the visibility of Ubuntu in general
not to be able to properly handle what is expected to be a simple task,
in the view of lay peopl
Even though it's not critical, I think it's important to fix this for
hardy. It's a very bad advertising for an otherwise very good
application (evince), and degrades the visibility of Ubuntu in general
not to be able to properly handle what is expected to be a simple task,
in the view of lay peopl
Bug #20310 also links to the same upstream bug. Are this and that one
dups? (sure seems like).
If someone decides to mark that as a dupe of this one (or the other way
around), there might be interesting information there to repost here,
for a centralized view of the issue. I'll try to link the scr
*** This bug is a duplicate of bug 135548 ***
https://bugs.launchpad.net/bugs/135548
** This bug has been marked a duplicate of bug 135548
[Gutsy] Action on critical battery isn't triggered - regression
--
Power manager on "battery critical" event
https://bugs.launchpad.net/bugs/216762
Yo
*** This bug is a duplicate of bug 135548 ***
https://bugs.launchpad.net/bugs/135548
** This bug has been marked a duplicate of bug 135548
[Gutsy] Action on critical battery isn't triggered - regression
--
g-p-m does not allow using battery percentage for policy in feisty
https://bugs.lau
*** This bug is a duplicate of bug 135548 ***
https://bugs.launchpad.net/bugs/135548
** This bug has been marked a duplicate of bug 135548
[Gutsy] Action on critical battery isn't triggered - regression
--
System dies instead of Suspend for Critical Battery
https://bugs.launchpad.net/bugs
*** This bug is a duplicate of bug 135548 ***
https://bugs.launchpad.net/bugs/135548
** This bug has been marked a duplicate of bug 135548
[Gutsy] Action on critical battery isn't triggered - regression
--
System dies instead of shutting down
https://bugs.launchpad.net/bugs/41215
You rece
*** This bug is a duplicate of bug 135548 ***
https://bugs.launchpad.net/bugs/135548
** This bug has been marked a duplicate of bug 135548
[Gutsy] Action on critical battery isn't triggered - regression
--
laptop does not hibernate on low battery
https://bugs.launchpad.net/bugs/221454
You
*** This bug is a duplicate of bug 135548 ***
https://bugs.launchpad.net/bugs/135548
** This bug has been marked a duplicate of bug 135548
[Gutsy] Action on critical battery isn't triggered - regression
--
No low battery warning on Samsung X11-T5500 notebook
https://bugs.launchpad.net/bug
** Tags added: data-loss
--
[Gutsy] Action on critical battery isn't triggered - regression
https://bugs.launchpad.net/bugs/135548
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu.
--
desktop-bugs mailing li
Upstream bug report says it's solved. Why is the solution not patched in
Ubuntu?
BTW, the workaround in comment 18 works for me, on a Lenovo 3000 v100
(Ubuntu 8.04).
--
[Gutsy] Action on critical battery isn't triggered - regression
https://bugs.launchpad.net/bugs/135548
You received this bug no
I don't think this bug reflects the linked upstream bug, since both are
related to different themes. Uptream icons is probably the ones for the
"Clearlooks" theme, or similar, while Ubuntu uses the "Human" theme,
with a completely different battery icon (green instead of blue). Please
see the scree
*** This bug is a duplicate of bug 199088 ***
https://bugs.launchpad.net/bugs/199088
** This bug has been marked a duplicate of bug 199088
[Hardy] Message: "Suspend Problem. Your computer failed to suspend"
--
Get notification about sleep failed even though it seems to have gone well
aft
*** This bug is a duplicate of bug 74231 ***
https://bugs.launchpad.net/bugs/74231
** This bug has been marked a duplicate of bug 74231
Icon colour changes at inappropriate times (too early; red, yellow, green)
--
gnome power manager applet is visually misleading
https://bugs.launchpad.ne
*** This bug is a duplicate of bug 89983 ***
https://bugs.launchpad.net/bugs/89983
** This bug has been marked a duplicate of bug 89983
Feisty reports suspend failed after resuming from suspend
--
[Hardy] Message: "Suspend Problem. Your computer failed to suspend"
https://bugs.launchpad.n
*** This bug is a duplicate of bug 89983 ***
https://bugs.launchpad.net/bugs/89983
** This bug is no longer a duplicate of bug 199088
[Hardy] Message: "Suspend Problem. Your computer failed to suspend"
** This bug has been marked a duplicate of bug 89983
Feisty reports suspend failed af
This is probably a dup of bug #161216 (or the other way around). Can
someone decide and set it accordingly?
--
"Suspend failed" message gives false advice
https://bugs.launchpad.net/bugs/93281
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
** This bug has been marked a duplicate of bug 89983
Feisty reports suspend failed after resuming from suspend
--
Ubuntu reports "suspend problem", but provides no detail on what went wrong
https://bugs.launchpad.net/bugs/161216
You received this bug notification because you are a member of Ub
This is probably a dup of bug #93281 (or the other way around). Can
someone decide and set it accordingly?
** This bug is no longer a duplicate of bug 89983
Feisty reports suspend failed after resuming from suspend
--
Ubuntu reports "suspend problem", but provides no detail on what went wrong
I still get this bug in latest hardy. Here are some possibly relevant
logs of it, now it's just happened.
Any laptop-specific information needed is probably posted at bug 212660.
** Attachment added: "syslog.log"
http://launchpadlibrarian.net/16869748/syslog.log
--
Feisty reports suspend fa
** Attachment added: "messages.log"
http://launchpadlibrarian.net/16869751/messages.log
--
Feisty reports suspend failed after resuming from suspend
https://bugs.launchpad.net/bugs/89983
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
** Attachment added: "dmesg.log"
http://launchpadlibrarian.net/16869754/dmesg.log
--
Feisty reports suspend failed after resuming from suspend
https://bugs.launchpad.net/bugs/89983
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome
** Attachment added: "kern.log"
http://launchpadlibrarian.net/16869757/kern.log
--
Feisty reports suspend failed after resuming from suspend
https://bugs.launchpad.net/bugs/89983
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-p
** Attachment added: "user.log"
http://launchpadlibrarian.net/16869763/user.log
--
Feisty reports suspend failed after resuming from suspend
https://bugs.launchpad.net/bugs/89983
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-p
** Attachment added: "lsmod.log"
http://launchpadlibrarian.net/16869765/lsmod.log
--
Feisty reports suspend failed after resuming from suspend
https://bugs.launchpad.net/bugs/89983
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome
Related bugs (not dups): bug #99065 and #70752
--
no ssh-agent after resume from hibernate
https://bugs.launchpad.net/bugs/268141
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to seahorse in ubuntu.
--
desktop-bugs mailing list
desktop-b
Public bug reported:
Binary package hint: seahorse
After resume from hibernate (and not suspend) seahorse-daemon and
seahorse-agent processes are not running, and there is no other ssh-
agent available making it annoying to use ssh, and impossible to use
sftp mounts in nautilus.
Steps to reprodu
Public bug reported:
Binary package hint: libgtk2.0-0
[EMAIL PROTECTED]:~$ lsb_release -rd
Description:Ubuntu 8.04
Release:8.04
[EMAIL PROTECTED]:~$ apt-cache policy libgtk2.0-0
libgtk2.0-0:
Installed: 2.12.9-3ubuntu3
One can't use dead keys to input a c+cedilla in en_US (probably
Sebastien, I opened it in
http://bugzilla.gnome.org/show_bug.cgi?id=532204, and promptly got an
answer (notabug). I had to reopen it because I strongly disagree with
the justification given, but I won't pursue this ad infinitum.
In the event of it being denied again, can this issue be be solved in
New comment from upstream (which I find satisfactory).
Maybe then we should change the package from gtk to gnome-*?
Comment #3 from Owen Taylor(gtk+ developer, points: 25)
2008-05-08 17:44 UTC [reply]
English is also the second language of many people who ues C+acute as their
f
** Changed in: gtk+2.0 (Ubuntu)
Status: Incomplete => Invalid
** Bug watch added: GNOME Bug Tracker #333104
http://bugzilla.gnome.org/show_bug.cgi?id=333104
** Also affects: gnome-control-center via
http://bugzilla.gnome.org/show_bug.cgi?id=333104
Importance: Unknown
Status
** Changed in: gnome-control-center (Ubuntu)
Assignee: (unassigned) => Ubuntu Desktop Bugs (desktop-bugs)
Status: New => Confirmed
--
libgtk2 immodules has cedilla disabled in en locales
https://bugs.launchpad.net/bugs/228077
You received this bug notification because you are a member
** Bug watch added: Red Hat Bugzilla #432963
https://bugzilla.redhat.com/show_bug.cgi?id=432963
** Also affects: gnome-control-center (Fedora) via
https://bugzilla.redhat.com/show_bug.cgi?id=432963
Importance: Unknown
Status: Unknown
--
libgtk2 immodules has cedilla disabled in e
*** This bug is a duplicate of bug 228077 ***
https://bugs.launchpad.net/bugs/228077
** This bug has been marked a duplicate of bug 228077
libgtk2 immodules has cedilla disabled in en locales
--
It'd be nice to have some way to overwrite /etc/gtk-2.0/gtk.immodules
https://bugs.launchpad.n
** Also affects: seahorse (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
I used to have a lock icon in the notification area indicating my ssh
keyphrase is cached by the seahorse agent (I guess in feisty I still
had it). I never seen it ever since the upgrade
Positive. Check out, for example, bug #129231 I reported in the
beginning of Feisty cycle.
--
seahorse notification icon doesn't appear anymore
https://bugs.launchpad.net/bugs/273862
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to seahors
I originally reported this bug against seahorse, since it appears as
argument to ssh-agent in the processes list.
I'd like to correct the testcase. Although it happened that seahorse
died when I decided to post the bug, I cannot reproduce it, therefore
I'm forced to attribute this event to chance.
I found that to use a workaround to restart gnome-keyring-daemon from
command line in a way to reuse the existing socket: the env var
GNOME_KEYRING_TEST_PATH. This var should be set to the /tmp/keyring-
that was previously in use.
For example:
GNOME_KEYRING_TEST_PATH=/tmp/keyring-pw7JIX/
There's no command line option to pass a directory to g-k-d in runtime.
I'll open a wishlist bug to be triaged for this.
--
no ssh-agent after resume from hibernate
https://bugs.launchpad.net/bugs/268141
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Public bug reported:
Binary package hint: gnome-keyring
Currently gnome-keyring-daemon has no documented command line options.
In case the daemon dies or is t should have an option similar to ssh-
agent's '-a' option in order to revive the agent using the socket
previously created.
This function
*** This bug is a duplicate of bug 92296 ***
https://bugs.launchpad.net/bugs/92296
** This bug is no longer a duplicate of bug 20310
poor rendering
** This bug has been marked a duplicate of bug 92296
[Feisty] Low quality of text rendering in Evince
--
evince doesn't display pdf as it
*** This bug is a duplicate of bug 92296 ***
https://bugs.launchpad.net/bugs/92296
** This bug has been marked a duplicate of bug 92296
[Feisty] Low quality of text rendering in Evince
--
poor rendering
https://bugs.launchpad.net/bugs/20310
You received this bug notification because you a
Links from dup bug #138651
http://www.inference.phy.cam.ac.uk/mackay/network.pdf
http://launchpadlibrarian.net/9205489/evince-175percent.png
http://launchpadlibrarian.net/9205505/kpdf-175percent.png
http://launchpadlibrarian.net/9205536/evince-100percent.png
--
[Feisty] Low quality of text rende
I agree with Andy. It worked according to the documentation on Feisty,
but on Gutsy they don't hide anymore when clicking on the Desktop.
--
sticky notes should stay when user clicks on desktop
https://bugs.launchpad.net/bugs/61919
You received this bug notification because you are a member of Ub
You are correct, Dante, it still works as advertised. I get the expected
behaviour after clearing gnome/gconf config dot-files and reconfiguring
from scratch.
I agree it's a desirable wishlist, even though I like it the way it is.
Hope upstream gets it done by the next gnome release.
--
sticky n
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/8107923/Dependencies.txt
** Attachment added: "ProcMaps.txt"
http://launchpadlibrarian.net/8107924/ProcMaps.txt
** Attachment added: "ProcStatus.txt"
http://launchpadlibrarian.net/8107925/ProcStatus.txt
--
printout
Public bug reported:
Binary package hint: evince
This doesn't happen to acroread or kpdf. Other gtk apps that use gnome
print system (openoffice and firefox) also don't suffer, so I am
reporting on evince only.
Everytime I start evince, the "Advanced" tab in Print option in General
menu is recon
Sebastien,
If there is a fix, can I get/apply the fix or workaround still in
feisty?
--
printout mode always starts with "Normal (Color cartrigde)" only, skipping
black cartrigde completely
https://bugs.launchpad.net/bugs/120861
You received this bug notification because you are a member of Ubu
Public bug reported:
Binary package hint: evince
Hello,
in a particular PDF I have, the letters seem strangely connected, and
some appear as symbols. The same file appears nicely in xpdf and adobe
reader.
I'm including a screenshot.
How can I provide better information to get it fixed?
** Aff
I forgot to mention I'm using Feisty.
Here's the screenshot.
** Attachment added: "evince-feisty.png"
http://launchpadlibrarian.net/8561960/evince-feisty.png
--
strange font behaviour - connected letters
https://bugs.launchpad.net/bugs/128074
You received this bug notification because you ar
And here's the original file.
evince prints it ok, FWIW (except for bug #120861, but that can be
worked around).
** Attachment added: "Pybus_et_al_2000_Genetics.pdf"
http://launchpadlibrarian.net/8561964/Pybus_et_al_2000_Genetics.pdf
--
strange font behaviour - connected letters
https://bugs
Just to add that after purging and recreating all printer
configurations, I am now able to print in b&w with evince, provided
everytime I open it, I change from 'Normal Color', to 'Grayscale'.
Still annoying, but at least it works.
--
printout mode always starts with "Normal (Color cartrigde)" o
** Summary changed:
- printout mode always starts with "Normal (Color cartrigde)" only, skipping
black cartrigde completely
+ printout mode always starts with "Normal (Color cartrigde)" only, skipping
black cartridge completely
--
printout mode always starts with "Normal (Color cartrigde)" onl
91 matches
Mail list logo
