Public bug reported:
```
GNU Image Manipulation Program version 2.10.36
git-describe: GIMP_2_10_36
Build: unknown rev 0 for linux
# C compiler #
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-linux-gnu/13/lto-wrapper
Changing units helped. Thanks
** Changed in: gnome-system-monitor (Ubuntu)
Status: Incomplete => Invalid
** Information type changed from Public to Private
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-system-monitor
Public bug reported:
Gnome System Monitor has been incorrectly showing the amount of RAM for
some time (months?). Based on the system logs, I was able to determine
that Gnome System Monitor has not been updated recently. So where is the
incorrect data coming from?
Gnome System Monitor:
RAM: 33.5
I am attaching the logs.
** Attachment added: "journal.txt"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2000835/+attachment/5639364/+files/journal.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
So you can minimize this window and then have working Unity. If you
close it, your session ends.
This window belongs to a process of
/usr/libexec/gnome-session-failed
** Attachment added: "jammy-error-moved-aside.png"
Confirm (in KVM machines) that Unity works fine from gdm3 under Impish,
but a fresh VM of Jammy doesn't work with either lightdm or gdm for me.
I get to see a quick glimpse of the Unity desktop, then this fullscreen
splash error shows up
"Oh no! Something has gone wrong.
A problem has occurred
Is this a `gnome-session` issue? The source sayeth (@ gnome-
session/main.c:422)
/* From 3.14 GDM sets XDG_CURRENT_DESKTOP. For compatibility with
* older versions of GDM, other display managers, and startx,
* set a fallback value if we don't find it set.
*/
(In reply to Jeremy Bicha from comment #4)
> The first 2 did not work for me but the 3rd did.
>
> iris
>
> $ MESA_LOADER_DRIVER_OVERRIDE=iris yelp
> EGLDisplay Initialization failed: EGL_NOT_INITIALIZED
> Cannot create EGL context: invalid display (last error: EGL_SUCCESS)
> Unsupported
OK I found a way to fix it @ package time! I previously built webkitgtk
with -DENABLE_X11_TARGET=OFF. I tried building with
-DENABLE_X11_TARGET=ON (since this is the major difference between my
build and the gnome-build-meta build, aside from Mesa version), and now
it works properly
Seems like
I don't compile WebKit w/ X11 support so I can't tell you if running
epiphany w/ GDK_BACKEND=x11 helps anything
---
I do not see those EGL errors when I run epiphany on the host. However,
if I run the Epiphany flatpak with FLATPAK_GL_DRIVERS=host, I get
EGLDisplay Initialization failed:
Okay, ever since I installed this bug fix, my mouse has been playing up.
First, dragging and dropping across windows exhibited errant behaviour,
such as dropping the dragging item in between box borders. Now, every
once in a while, my mouse's primary buttons switch. The original issue
has been
@Marco thank you for your post regarding the test packages (comment
#50). This has almost solved the problem for me. I still get enlarged
text at the decryption password screen. Not a problem for me, but maybe
the information will help you guys.
--
You received this bug notification because you
Public bug reported:
```
GNU Image Manipulation Program version 2.10.14
git-describe: GIMP_2_10_12-511-ga4f55d6c7e
C compiler:
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/7/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none
I did just want to add that it seems the update has affected the mouse
as well. Transitions between windows seems to occasionally disable the
mouse click momentarily. This is an issue in dragging and dropping,
which will occasionally cut out or display unpredictable behavior. I am
fairly certain
I did just want to add that it seems the update has affected the mouse
as well. Transitions between windows seems to occasionally disable the
mouse click momentarily. This is an issue in dragging and dropping,
which will occasionally cut out or display unpredictable behaviour. I am
fairly certain
Thankyou Konrad, your comment #17, has solved this issue for me. I did
not hold the package at 6-0, though. Personal preference, but I feel
that accidentally updating and breaking it again is a simple fix, while
having a hold on a package that you have to remember to unhold could sit
in the
Hello Akhil
Thankyou for this suggestion and the time you have put in. I tried this,
and a few other workarounds from a few other forums, and they have all
failed for me. The only solution has been to roll back the recently
updated 'libmutter' package, as per comment #17 in
0.walbert - where did you place these commands? I'm a little new to this
and I have been having the same problem.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1892521
Title:
UI
Hi, Upgraded an old desktop from 19.10 to 20.04 and hit this graphics
display issue. I also have the same graphics card:
>From lspci:
03:00.0 VGA compatible controller: NVIDIA Corporation G73 [GeForce 7600 GT]
(rev a1)
Is there any workaround I can perform to make this desktop usable? Other
This bug is still happening .. it really does render this whole
package unworkable .. its equivalent to the computer not working at
all. At least that way you know your data isn't being corrupted. I'm
appalled at the cavalier attitude this bug is being treated...other
end itus ... I
Incidentally this bug has been happening and someone suggested updating
Mutter to the latest version.
I had to install mutter to then update it to try and fix it .. so now
there are bugs due to software that was never installed in the first
place !!!
--
You received this bug notification
This is still happening despite the Ubuntu 20.04LTS installation being
fully patched using Liveupdate as at 25 May 2020.
In LibreOffice I have to hit Cntrl C repeatedly (more than 2 times or
click the copy icon sometimes 9 times or more to get some data and
this is just staying within
** Attachment added: "list_devices"
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1839010/+attachment/5281528/+files/list_devices
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in
Here are the logs:
** Attachment added: "journal"
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1839010/+attachment/5281525/+files/journal
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center
Public bug reported:
I previously had Windows 10 on my protab laptop. After wiping the hard
drive and installing Ubuntu 19.04 on the device, the touchpad ceases to
respond at all. I am using an external mouse currently.
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: gnome-control-center
Public bug reported:
I recently installed Ubuntu 19.04 on this protab laptop. In the settings
menu the sound output shows a headphone and a multichannel output
option. There is no sound coming out of either system, despite there
being sound detection demonstrated in the sound bars in the output
The issue persists on 19.04.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1778011
Title:
SRU: PRIME Power Saving mode draws too much power
To manage notifications about this bug
Public bug reported:
Brightness level can't be changed from keyboard with the Fn key and the
corresponding designated key. Other functions like changing volumes
involving the Fn key work perfectly. The only way I can change
brightness is from the status bar.
Current OS: Ubuntu 19.04 Disco Dingo
After seeing Alex's post, I tried installing 410.104-0ubuntu0~18.10.1 from
ppa:graphics-drivers.
Using 4.18.0-16-generic kernel.
I find that when I use Intel profile, powertop reports the nvidia card as 0%
active, and the setting in Tunables shows up as Good.
However, /proc/acpi/bbswitch
> * If I understand correctly, the bug does not occur in Ubuntu 18.10.
The user can switch seamlessly between using the Intel or the Nvidia
discrete graphics card. Is this correct?
@jespestana
No, this bug is affecting me on 18.10.
--
You received this bug notification because you are a member
I am facing the same issue in Ubuntu 18.10. The super key randomly stops
working and I loose control of all windows except for the active window,
which in some cases also stops working and cannot even do clicks there.
The workaround I found is to close all windows, lock the screen and the
problem
I can confirm that installing nvidia-390 through the Ubuntu driver dialog, and
then using nvidia-settings or prime-select to set intel keeps the nvidia card
on for me on my GeForce 840M laptop.
I can also confirm Installing bbswitch-dkms and turning it off through bbswitch
works.
--
You
Problem is caused by _cairo_path_fixed_stroke_extents() returning wrong
extents.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/1300659
Title:
printed pdf file lacks item boxes
To
Created attachment 125087
Debug patch
This patch shows the problem is caused by
_cairo_path_fixed_stroke_extents().
If the operation is changed to a fill (change line 259 in the PDF from
"S" to "f") the box appears in the output.
--
You received this bug notification because you are a member
Created attachment 125086
Reduced test case
Reduced test case. This PDF strokes a single path of one of the boxes in
the original PDF. The original PDF draws the boxes with the fill-stroke
operator "B". I've replaced it with a stroke "S".
To reproduce:
pdftocairo -ps reduced-test-case.pdf
During upgrade from 17.10 to 18.04 this happened to me
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to desktop-file-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1725121
Title:
package desktop-file-utils 0.23-1ubuntu3 failed to
Previous upgrades 16.04,16.10,17.04,17.10. Current 17.10 to 18.04
To get past the upgrade error , (Not sure if this is correct) but this
is what I did
sudo apt-get remove libp11-kit-gnome-keyring
I had previously additionally installed MATE desktop, so to avoid any conflicts
I removed it too.
The upgrade threw this error and the upgrade did not complete
KeyError: '0604-libp11-kit-gnome-keyring'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/packaging_impl.py", line 126, in
_apt_pkg
I had the same issue. In my case it turned out that gnome-control-center
had been uninstalled. I'm not sure why, but reinstalling fixed it.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
I have reported the bug on Gnome Bugzilla.
https://bugzilla.gnome.org/show_bug.cgi?id=791583
** Tags added: asked-to-upstream
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
I have reported the bug on Gnome Bugzilla.
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1726538
** Bug watch added: GNOME Bug Tracker #791583
https://bugzilla.gnome.org/show_bug.cgi?id=791583
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
Fixed with Ubuntu 17.10.
** Changed in: gnome-session (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1712080
Title:
wayland:
I had the same problem with Intel + AMD tandem on a desktop. I solved it
by adding in /etc/environment:
MUTTER_ALLOW_HYBRID_GPUS=1
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
Public bug reported:
I use a docking station to which I have connected 2 screens: first one
directly through the display port, second through DVI connector (from
which signal passes DVI-HDMI converter and finally to the screen). In
default gnome session, the two extra screens are set in their
** Also affects: lightdm (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1508146
Title:
alt + left/right arrows switch
Also see Bug #520546.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1508146
Title:
alt + left/right arrows switch between tty consoles, cannot disable
To manage
On Linux Mint 18.2 (based on Ubuntu 16.04) I don't experience the issue
when using mdm as X display manager instead of lightdm.
So this has something to do with lightdm ?!!
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell
A workaround that I found on reddit:
https://www.reddit.com/r/archlinux/comments/5620sf/alt_rightleft_arrow_keys_switching_to_virtual/d8g6ux5/
I created /etc/X11/xorg.conf.d/60-dontvtswitch.conf with the following
contents:
$ cat /etc/X11/xorg.conf.d/60-dontvtswitch.conf
Section "ServerFlags"
A workaround that I found on reddit:
https://www.reddit.com/r/archlinux/comments/5620sf/alt_rightleft_arrow_keys_switching_to_virtual/d8g6ux5/
I created /etc/X11/xorg.conf.d/60-dontvtswitch.conf with the following
contents:
$ cat /etc/X11/xorg.conf.d/60-dontvtswitch.conf
Section "ServerFlags"
That was running under Windows 8.1.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gimp in Ubuntu.
https://bugs.launchpad.net/bugs/556670
Title:
Can't click on UI elements in gimp (intermittent)
To manage notifications about this
I had this, but it was with my mouse. Don't know why, but I had to go
into Edit > Preferences > Input Devices > Reset Saved Input Device
Settings to Default Values.
Seems that that part of the configuration got corrupted somehow.
--
You received this bug notification because you are a member
Public bug reported:
Using the network manager to set my OpenVPN I have a DNS leak after
connecting to my secured network which also provides Internet
connection.
I think solution is here: http://www.ubuntubuzz.com/2015/09/how-to-fix-
openvpn-dns-leak-in-linux.html
However, I didn't find in the
Same issue in Ubuntu 17.04 (Unity)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1453655
Title:
desktop icons disappear on Ubuntu 15.04 when clicking Open Dropbox
folder
To
Public bug reported:
On the resources tab, the most recent part of the monitoring graphs are
out of view. I am referring to the right side of the graph.
The problem becomes more prominent when the window is small
horizontally. As I scale it up horizontally, I can see more recent
measurements,
Public bug reported:
Thw way to reproduce:
Open an attached example_file.pdf file.
Press CTRL+F
Try to type something (in my case the field is insensitive, I can only paste
some string).
The same problem with page and zoom fields.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: evince
Created attachment 120924
Check in ranges in ByteRange array v2
- renamed isInteger() to isIntOrInt64()
- added and use getIntOrInt64()
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evince in Ubuntu.
(In reply to Albert Astals Cid from comment #120)
> Ok, good, so Adrian can you commit your patch?
Pushed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/1085526
Title:
ubuntu
Created attachment 120924
Check in ranges in ByteRange array v2
- renamed isInteger() to isIntOrInt64()
- added and use getIntOrInt64()
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to poppler in Ubuntu.
(In reply to Albert Astals Cid from comment #120)
> Ok, good, so Adrian can you commit your patch?
Pushed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to poppler in Ubuntu.
https://bugs.launchpad.net/bugs/740506
Title:
ver
I don't think we need to check if the byte range covers the entire
document. Our job, when verifying the signature, is to use the byte
ranges provided in the signature dictionary. It is up to the pdf
producer to ensure the byte range covers the entire document (excluding
the signature value).
All
I don't think we need to check if the byte range covers the entire
document. Our job, when verifying the signature, is to use the byte
ranges provided in the signature dictionary. It is up to the pdf
producer to ensure the byte range covers the entire document (excluding
the signature value).
All
(In reply to Albert Astals Cid from comment #114)
> I'm not very convinced by the naming of
> GBool isInteger() { return type == objInt || type == objInt64; }
> what do you think of
> isIntOrInt64() ?
I prefer a single word instead of isXXXorYYY() but I can appreciate that
isInteger() could
Created attachment 120889
Check in ranges in ByteRange array
This is an alternative to the patch in comment 108. It checks all ranges
in the ByteRange array.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to poppler in Ubuntu.
(In reply to Andre Guerreiro from comment #105)
> Created attachment 120434 [details] [review]
> Improve robustness of SignatureHandler::validateCertificate
>
> This patch adds additional NULL-checking in
> SignatureHandler::validateCertificate() which avoids segfault for some
> signatures like
(In reply to Albert Astals Cid from comment #114)
> I'm not very convinced by the naming of
> GBool isInteger() { return type == objInt || type == objInt64; }
> what do you think of
> isIntOrInt64() ?
I prefer a single word instead of isXXXorYYY() but I can appreciate that
isInteger() could
(In reply to Andre Guerreiro from comment #105)
> Created attachment 120434 [details] [review]
> Improve robustness of SignatureHandler::validateCertificate
>
> This patch adds additional NULL-checking in
> SignatureHandler::validateCertificate() which avoids segfault for some
> signatures like
Created attachment 120889
Check in ranges in ByteRange array
This is an alternative to the patch in comment 108. It checks all ranges
in the ByteRange array.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evince in Ubuntu.
I suggest we change the pdfsig "-c" switch to "-nocert". We can easily
add a single character option if we find it is needed. But we can't get
rid of it if we later regret it.
I'm still waiting for an answer to comment 79.
--
You received this bug notification because you are a member of Ubuntu
(In reply to Andre Guerreiro from comment #97)
> Quoting from ISO 32000-1 section 12.8.1:
> "This range should be the entire file, including the signature dictionary
> but excluding the signature value itself (the Contents entry). Other ranges
> may be used but since they do not check for all
(In reply to Andre Guerreiro from comment #100)
> Created attachment 119283 [details] [review]
> Manpage improvement
Pushed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/1085526
(In reply to Albert Astals Cid from comment #96)
> As said please let's not spend too much time on arguing over switch names,
> if you really really want -nocert, just push a patch to the
> signatureHandling branch that switches to it.
Done. I've also added a man page. If any further information
(In reply to Andre Guerreiro from comment #100)
> Created attachment 119283 [details] [review]
> Manpage improvement
Pushed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to poppler in Ubuntu.
https://bugs.launchpad.net/bugs/740506
(In reply to Andre Guerreiro from comment #97)
> Quoting from ISO 32000-1 section 12.8.1:
> "This range should be the entire file, including the signature dictionary
> but excluding the signature value itself (the Contents entry). Other ranges
> may be used but since they do not check for all
I suggest we change the pdfsig "-c" switch to "-nocert". We can easily
add a single character option if we find it is needed. But we can't get
rid of it if we later regret it.
I'm still waiting for an answer to comment 79.
--
You received this bug notification because you are a member of Ubuntu
(In reply to Albert Astals Cid from comment #96)
> As said please let's not spend too much time on arguing over switch names,
> if you really really want -nocert, just push a patch to the
> signatureHandling branch that switches to it.
Done. I've also added a man page. If any further information
(In reply to Markus Kilås from comment #88)
> I found a workaround for my build issue by creating symlinks:
> /usr/include/nspr -> /usr/include/nspr4
> /usr/inclyde/nss -> /usr/include/nss3
Are you using configure or cmake? The nss pkgconfig file should contain
the correct include path.
--
You
What is the output of "pkg-config --cflags nss"?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/1085526
Title:
ubuntu pdf doc viewer will not let me sign a document
To manage
What is the output of "pkg-config --cflags nss"?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to poppler in Ubuntu.
https://bugs.launchpad.net/bugs/740506
Title:
verify digital signatures
To manage notifications about this bug go
(In reply to Markus Kilås from comment #88)
> I found a workaround for my build issue by creating symlinks:
> /usr/include/nspr -> /usr/include/nspr4
> /usr/inclyde/nss -> /usr/include/nss3
Are you using configure or cmake? The nss pkgconfig file should contain
the correct include path.
--
You
(In reply to Albert Astals Cid from comment #82)
> Honestly i don't think spending much time on discussing the option name
> makes much sense, we just need to document it properly and that's it.
I raised this issue because pdfimages uses -j for jpeg but -png, -jp2,
-jbig2, -tiff, and -ccitt for
(In reply to Albert Astals Cid from comment #82)
> Honestly i don't think spending much time on discussing the option name
> makes much sense, we just need to document it properly and that's it.
I raised this issue because pdfimages uses -j for jpeg but -png, -jp2,
-jbig2, -tiff, and -ccitt for
(In reply to Martin McDowell from comment #8)
> It has been a year since a last post of this bug but I am still getting this
> problem in October 2015. I have Ubuntu 14.04. The PDF is viewed in the
> default Evince document viewer 3.10.3
The fix is in poppler 0.28 released in Nov 2014.
--
You
(In reply to Albert Astals Cid from comment #70)
> So we have two things missing, right?
> * Enabling the use of other keystores
> * The name of the pdfsigverify tool
>
>
> I think the enabling the use of other keystores is important but maybe not
> critical for the first release.
>
> For the
(In reply to Albert Astals Cid from comment #70)
> For the pdfsigverify it seems we kind of agreeed on the compromise to call
> it pdfsig that only does verification right now but in the future may
> suppport signing?
This is the only thing left that I think needs fixing before the initial
(In reply to Adam Reichold from comment #77)
> Some minor suggestions:
>
> * The naming of BLOCK_SIZE and block_len in hashSignedDataBlock seems
> misleading to me, maybe CHUNK_SIZE and block_len?
>
> * The method hashSignedDataBlock could probably be replaced by a static
> function taking the
(In reply to Albert Astals Cid from comment #74)
> (In reply to Adrian Johnson from comment #73)
> > (In reply to Albert Astals Cid from comment #72)
> > > > Large file support.
> > >
> > > Do you think this should be a blocker for the initial release
+ r_values[0] = r2.isInt64() ? r2.getInt64() : r2.getInt();
+ r_values[1] = r3.isInt64() ? r3.getInt64() : r3.getInt();
+ r_values[2] = r4.isInt64() ? r4.getInt64() : r4.getInt();
According the PDF Reference, the ByteRange array contains pairs of
(offset,length).
Why do we ignore the first
(In reply to Albert Astals Cid from comment #72)
> > Large file support.
>
> Do you think this should be a blocker for the initial release or something
> we can improve later?
I think it should be included.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
(In reply to Adam Reichold from comment #77)
> Some minor suggestions:
>
> * The naming of BLOCK_SIZE and block_len in hashSignedDataBlock seems
> misleading to me, maybe CHUNK_SIZE and block_len?
>
> * The method hashSignedDataBlock could probably be replaced by a static
> function taking the
(In reply to Albert Astals Cid from comment #70)
> For the pdfsigverify it seems we kind of agreeed on the compromise to call
> it pdfsig that only does verification right now but in the future may
> suppport signing?
This is the only thing left that I think needs fixing before the initial
+ r_values[0] = r2.isInt64() ? r2.getInt64() : r2.getInt();
+ r_values[1] = r3.isInt64() ? r3.getInt64() : r3.getInt();
+ r_values[2] = r4.isInt64() ? r4.getInt64() : r4.getInt();
According the PDF Reference, the ByteRange array contains pairs of
(offset,length).
Why do we ignore the first
(In reply to Albert Astals Cid from comment #74)
> (In reply to Adrian Johnson from comment #73)
> > (In reply to Albert Astals Cid from comment #72)
> > > > Large file support.
> > >
> > > Do you think this should be a blocker for the initial release
(In reply to Albert Astals Cid from comment #72)
> > Large file support.
>
> Do you think this should be a blocker for the initial release or something
> we can improve later?
I think it should be included.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
(In reply to Albert Astals Cid from comment #70)
> So we have two things missing, right?
> * Enabling the use of other keystores
> * The name of the pdfsigverify tool
>
>
> I think the enabling the use of other keystores is important but maybe not
> critical for the first release.
>
> For the
(In reply to Andre Guerreiro from comment #63)
> I also thought of adding the feature to pdfinfo but it seems wrong to mix up
> something which performs various computations and relies on external state
> (NSS cert DB) to pdfinfo which just reads metadata from the file itself.
pdfinfo already
(In reply to Andre Guerreiro from comment #63)
> I also thought of adding the feature to pdfinfo but it seems wrong to mix up
> something which performs various computations and relies on external state
> (NSS cert DB) to pdfinfo which just reads metadata from the file itself.
pdfinfo already
I don't think NSS should be mandatory. It is not required for rendering
PDFs. configure/cmake should include NSS in the "building poppler with
support for" summary.
> byte_range->arrayGet(1, );
> byte_range->arrayGet(2, );
> byte_range->arrayGet(3, );
>
> unsigned int signed_data_len =
I don't think NSS should be mandatory. It is not required for rendering
PDFs. configure/cmake should include NSS in the "building poppler with
support for" summary.
> byte_range->arrayGet(1, );
> byte_range->arrayGet(2, );
> byte_range->arrayGet(3, );
>
> unsigned int signed_data_len =
Are you guys talking about the issue on NFS filesystems or local disks?
There have been two independent issues, the NFS issue was fixed in
around gvfs_1.17 while the other issue was fixed around gvfs_1.22.
NFS issue: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=624507
local issue:
I'm not sure that removing this functionality is a good idea. Can't we
just add an option to findText to enable a looser search and leave it to
the front ends to decide if/how to expose this option.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
1 - 100 of 361 matches
Mail list logo
