This is due to this bug:
https://bugzilla.gnome.org/show_bug.cgi?id=735311
Basically, google changed the way http requests are handled. There is a
patch available for 3.10, which should work for ubuntu 14.04, here:
https://bug735311.bugzilla-
attachments.gnome.org/attachment.cgi?id=284624
Debi
I just realized that this bug was reported *before* google changed the
http handling, so the bug reporter might have been experiencing a
different problem. Nevertheless, the problem exists now.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscr
It looks like the bug I linked to above in comment #3 might be a
duplicate of a different bug in evolution-data-server. Google has
changed the way it handles http authentication, breaking online accounts
functionality.
evolution-data-server bug:
https://bugzilla.gnome.org/show_bug.cgi?id=735311
> Current kernels have KEY_MICMUTE==248, i. e. X.org should be
> perfectly able to recognize this. Apparently this was done in
> 2011 already.
248 is the first linux kernel value which X cannot handle.
The mapping is +8, so 248 ⟹ 256, which does not fix in 8 bits.
(The first 8 are reserved – fro
Most of the information I have about xfa has come from the itext list.
An example of the type of info posted there:
http://support.itextpdf.com/node/134
If there is new info since 2011/12 I’d be interested to know.
--
You received this bug notification because you are a member of Ubuntu
Deskto
It looks like the xfa situation isn’t as dire as I’d been led to
understand.
OTOH, I’m not entirely certain that the licence text in the preface of
the pdf referenced in comment #9 is GPL-compatible. Or even DFSG-
compatible.
In any case (unless Albert things otherwise), it probably should not b
> "b" == bugzilla-daemon writes:
> James, can you define the deficiencies in the spec linked from comment #9 so
> that we can understand which parts of XFA still need to be documented?
For starters www.xfa.org does not exist. And xfa.org does not have an A
or record.
-JimC
--
You r
Adobe would have to document XFA forms before this even could be
addressed.
The most up to date info I could find on that front is:
http://en.wikipedia.org/wiki/XFA#Standardization
As long as Adobe keeps XFA forms proprietary they are not potable and
livecycle and acroread are the only way t
The renderings I get from evince (master, with poppler master and
cairo master), ghostscript (9.05 and master) and mupdf (master) all
match the png you posted as attachment #62423.
I looked at the document after running it though:
:; mupdfclean -d -a Abschlussarbeit.pdf Abschlussarbeit.pdfc
to
gsd-media-keys-manager.c.rej :
--- plugins/media-keys/gsd-media-keys-manager.c 2012-04-14 11:13:20.0
+0400
+++ plugins/media-keys/gsd-media-keys-manager.c 2012-04-14 11:20:07.772836587
+0400
@@ -142,6 +144,8 @@
NotifyNotification *volume_notification;
NotifyNotification
I'm using Debian Wheezy, but I tried it on Ubuntu's 3.2.2 source package
and it failed with the same error.
I tried unpacking the package and using patch -p1 <
52_brightness_in_hardware.patch, and that didn't work.
I tried putting it in the debian/patches directory and using dpkg-buildpackage,
b
Patch didn't work for me. What gnome-settings-daemon version did you
work on? (3.2.2 here)
$ patch -p1 < ../52_brightness_in_hardware.patch
patching file data/org.gnome.settings-daemon.plugins.power.gschema.xml.in.in
patching file plugins/media-keys/gsd-media-keys-manager.c
Hunk #1 succeeded at
Thanks. I'll test this out as soon as I find time to.
--
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/527157
Title:
Brightness controls skips Levels.
To manage notific
Dmitriy: Yes it is a dirty hack :) I don't know of any other
applications that would increment the backlight up and down, and GNOME's
ability to set the brightness to a specific percentage (without going
through steps inbetween) *should* still be functional with it...although
even the unpatched g
Please note that the above patch is ONLY for those encountering this
problem and should definitely be used ONLY on an individual basis. It
will break backlight control for everyone else using GNOME 3.2.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
This patch is for GNOME 3.2 that permanently disables gnome-settings-
deamon's ability to step-up and step-down the backlight. For those who
still can't get the correct brightness steps, this is a workaround. It
works perfectly on my Lenovo Thinkpad x220.
I'm not usually a code hacker or patcher
While this bug doesn't affect solving the Sudoku puzzle, it leaves a bad
impression--especially for a newbie, who may try playing the game during
his/her initial trial of Ubuntu. After all, timing how long it took you
to solve the puzzle is 'obviously' easy. E.g., just save computer's
clock at star
17 matches
Mail list logo
