Thanks, JFBucas, adding this line fixed it for me!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/904001
Title:
Can't start evince over SSH tunnel X session
Status in “evince”
*** This bug is a duplicate of bug 904001 ***
https://bugs.launchpad.net/bugs/904001
** This bug has been marked a duplicate of bug 904001
Can't start evince over SSH tunnel X session
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
Unfortunately, the CUPS developers - if there indeed are any - do not
give a shit. The command line tools are brain dead by design, the
documentation is inaccurate, there are essentially no error checking or
reporting, and it has been this way since the inception.
Here's a bug from 2006 - guess
Seems like a good idea that would take slightly less than six years to
fix:
http://www.cups.org/str.php?L1781+P0+S-2+C0+I0+E0+M20+Q1781
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
Interestingly, I generated two PDFs with xelatex, identical except for
including a PNG image. Both documents look okay in Evince, but the one
with the image prints the reverse (even numbered) pages upside down.
Unfortunately, I can't attach the documents here, but contact me
privately (ketil a
I should add to the above that the incorrect version also has
substantially inferior font rendering - downright ugly.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/461918
Title:
I can't believe this is still in. Is CUPS unused in enterprise
environments?
In my opinion, CUPS is good infrastructure, but it needs a bit of love
with documentation and user interaction and so on. Which it somehow
isn't getting, and it puzzles me why - most other system critical stuff
seems
Pidgin has been working for me (with the env variable workaround for MS
servers), but now suddenly it fails to display a window. Debug (-d) and
strace seem to indicate the program is otherwise working. When I
Ctrl-C, the window appears to flicker on screen before terminating.
While it is
I saw this, but removing .purple/prefs.xml fixed it (i.e. it displayed
the window again when I started pidgin, but of course I lost a bunch of
my preferences.)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pidgin in Ubuntu.
Removing .purple/prefs.xml fixed it for me.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pidgin in Ubuntu.
https://bugs.launchpad.net/bugs/879950
Title:
pidgin not showing up
Status in “pidgin” package in Ubuntu:
Confirmed
Or, just changing the
prefs name='blist' [...]
pref name='list_visible' type='bool' value='0'/
from '0' to '1' also brought the window back. I guess this is a
Gnomism, Pidgin isn't expected to work without some supporting things
running alongside it, panels or whatever, so it starts up
I stumbled into the same thing: When specifying 'nomodeset' as a kernel
parameter on an Intel i915 system (built in HD4400 graphics), I
sometimes used to get a black screen in 13.09. In 14.04, the system
would come up, but limited to 1024x768 resolution, and the monitor would
be undetected (named
I don't know if it is relevant here, but I got the same response from
xrandr (about gamma), and also struggled with wrong resolutions. For me,
the cause was the 'nomodeset' kernel parameter, this (i.e. disabling
kernel modesetting) caused the i915 graphics driver to fail, and the
vesa driver to be
Is this an issue on a supported release? If so, please reopen this
report, attach a document this is reproducible with (not post a URL),
and execute the following at a terminal:
I am unable to test this. For printing, I have to specify a different
user name (in .cups/client.conf), and as
> Do you still see a problem related to the one that you reported in a
> currently supported version of Ubuntu?
Thanks for following up! I don't use Shotwell any more, if nobody else
corroborates the report, I suggest you just can close it.
-k
--
If I haven't seen further, it is by standing in
Ubuntu 19.10, using Xmonad as my window manager, and noticed the same
thing. Just confirming Darko's observation above - uninstalling
libreoffice-gtk3 and restarting lowriter appears to have restored the
menus (using some small font, but I only have FHD resolution, so fine
with me).
--
You
16 matches
Mail list logo
