First I tried logging out/in with extensions still enabled as a control,
and the issue has stopped happening for now.
I will keep an eye on it and try to pinpoint if something is triggering
it to start happening.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bu
I did just try disabling all extensions, and its still happening.
--
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/2107678
Title:
focus stealing prevention fails for keyboard only whe
gsconn...@andyholmes.github.io
Name: GSConnect
Description: GSConnect is a complete implementation of KDE Connect especially
for GNOME Shell with Nautilus, Chrome and Firefox integration. It does not rely
on the KDE Connect desktop application and will not work with it installed.
KDE Connect
It's not specific to Element, I can also reproduce it from Thunderbird.
I click a link in an email, try to type in Firefox and Thunderbird is
receiving the key presses.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
It was already running, clicking the link opened a new tab.
--
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/2107678
Title:
focus stealing prevention fails for keyboard only when swit
Ok, I've got this happening right now. Unfortunately I can't screenshare
as this is my work machine with private information on screen, but if
you need any other info about the apps of environment I can capture it.
I have Element and Firefox open. The caret is in the Element chat. I
click on a lin
It doesn't happen consistently so it's hard to pin down exactly when its
happening, but one of my colleagues has Element and Firefox side-by-side
on the desktop, and it happens (sometimes) when Element has focus then
he clicks on the Firefox window.
If we can replicate it more consistently, I will
I and my colleagues are experiencing this. As this is related to mutter,
it might be useful information that we are using X11 sessions rather
than Wayland.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.
Daniel
Please find attached the journal.txt file that I generated during the
Wayland session.
Thank you
Fanus
On Tue, 4 Mar 2025 at 07:35, Daniel van Vugt <2100...@bugs.launchpad.net>
wrote:
> Thanks for the bug report. While the problem is happening, please open a
> terminal and run:
>
> jo
Hi Daniel
I am currently using the computer for a project - I will do so when I get a
chance - Need to switch back to wayland first I suppose ?
As mentioned, it is working with Xorg at the moment.
Fanus
On Tue, 4 Mar 2025 at 07:35, Daniel van Vugt <2100...@bugs.launchpad.net>
wrote:
> Thanks f
Still an issue in Ubuntu 24.04.1, sheesh! FWIW, also occurs on Ubuntu
Budgie 24.04.1.
--
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/1532508
Title:
Screen contents revealed bri
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
OFFLOAD_TAR
/john@pop-os
/---
///*767 OS: Pop!_OS 22.04 LTS x86_64
//7676767676*// Kernel: 6.2.6-76060206-generic
/76767//7676767// Uptime: 2 hour
/john@pop-os
/---
///*767 OS: Pop!_OS 22.04 LTS x86_64
//7676767676*// Host: OptiPlex 7040
/76767//7676767// Kernel: 6.0.6-76060006-ge
This is still happening as of 22.10
--
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/1956248
Title:
I get two characters in Activities when I press one key for the first
key I
Public bug reported:
Adding and removing tabs can sometimes cause the window to grow and
shrink in different directions, top or bottom.
To reproduce, use gnome and have the dock at the bottom of the screen.
Open a new gnome-terminal and move the new gnome-terminal window so that
the bottom is pus
> 1. Look in /var/crash for crash files ...
I did and could not find any recent ones - most recent was over a week
ago.
> 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID
> is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Nothing there that is re
Here is the output of `journalctl -b-1 | tail` after waiting over a
minute on the blank screen and restarting. (In this case the screen
wasn't completely blank but had a non-flashing cursor in the top left
corner. It doesn't appear every time, only ~1/3 of wake from sleep
attempts.)
** Attachment
I'm surprised that anyone can change the status of the bug. Anyway I
encountered it too(#1982656)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to totem in Ubuntu.
https://bugs.launchpad.net/bugs/1971768
Title:
Totem not running on U
*** This bug is a duplicate of bug 1971768 ***
https://bugs.launchpad.net/bugs/1971768
Public bug reported:
** (totem:5488): WARNING **: 17:40:41.485: Element 'gtkglsink' is
missing, verify your installation
** (totem:5488): WARNING **: 17:40:41.485: Element 'glsinkbin' is
missing, verify yo
Night Light was previously working on my hybrid Nvidia laptop before the
recent changes that switched Wayland to X11. I manually switched back to
Wayland, but now Night Light is not working.
Why are the changes that caused these bugs not being rolled back?
--
You received this bug notification b
To clarify, all future installs with hybrid Nvidia graphics will now
default to Wayland? So users won't have to work around this issue by
manually selecting Wayland in the log in screen? Cannot expect the
average user to figure this out.
I am unclear why this bug was not rolled back once it was id
Public bug reported:
On Impish 21.10, gnome-shell freezes up when trying to login,
specifically after I have typed in my password and hit enter. I have
seen this both when logging in after the display shuts itself off after
whatever the automatic timeout is, and also after manually locking the
scr
And with Ubuntu 21.10, it's gotten worse.
The "Executable Text Files" preferences is gone. The dconfg property
executable-text-activation is gone. Double clicking still opens the file
in gedit.
But at least "run as a program" was added to the right-click menu, so
that's good, I guess?
--
You re
Also I'm not sure I agree with jdstrand's apparmor profile which
includes:
/run/snapd.socket rw,
which I don't think we want to grant to any PDF file opened with evince?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evince in U
** Attachment added: "prevboot.txt"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1912246/+attachment/5474126/+files/prevboot.txt
--
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/
** Attachment added: "lspci.txt"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1912246/+attachment/5474125/+files/lspci.txt
** Attachment removed: "prevboot.txt"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1912246/+attachment/5474124/+files/prevboot.txt
--
You received
Here's lspci
--
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/1912246
Title:
[nvidia] gnome-shell freezes randomly
To manage notifications about this bug go to:
https://bugs.launchpa
Here's lspci
--
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/1912246
Title:
[nvidia] gnome-shell freezes randomly
To manage notifications about this bug go to:
https://bugs.launchpa
Okay, so this time when it happened at Sun Mar 7 02:44 AM UTC 2021,
here are the logs. I did not find any crash files in /var/crash, and
there were no results for my whoopsie-id either.
The journalctl output is attached
** Attachment added: "prevboot.txt"
https://bugs.launchpad.net/ubuntu/+s
Here's lspci
** Attachment added: "lspci -kv"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1912246/+attachment/5471916/+files/lspci.txt
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => New
** Changed in: gnome-shell-extension-ubuntu-dock (U
Hey so sorry I missed that you wanted me to run those commands before,
but it happened again this morning and here are the requested logs and
lspci output. Note that I stripped out all the messages from snapd since
I have debug mode enabled and it's extremely noisy, but if you think
snapd could be
So I disabled both ubuntu-dock and the desktop icons extensions and
still see the freezes, here's a log of gnome-shell:
https://pastebin.ubuntu.com/p/CXCfTVtkMJ/
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
Status: Incomplete => New
** Changed in: gnome-shell (Ubuntu)
S
Public bug reported:
The symptoms here for me are exactly the same as described in
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-
icons/+bug/1912246 where after starting up my Groovy system with X11 and
proprietary NVIDIA drivers the desktop session just hangs for a minut
Unfortunately, I seem to be on that version of gnome-shell-extension-
desktop-icons and still experience the freeze when I enable the desktop
icons extension. Here's the dpkg output and gnome-shell logs:
https://pastebin.ubuntu.com/p/yqDTV5KBmC/
** Changed in: gnome-shell-extension-desktop-icons (
So indeed after enabling _only_ the Desktop Icon extension I experienced
a freeze. Here are the logs: https://pastebin.ubuntu.com/p/XwJS7N4tF5/
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bu
So after a full day of usage yesterday I did not see the freeze/crash at
all, so it does indeed appear to be caused by one of the extensions
bundled with Ubuntu. Should I try just enabling them one-by-one using
the Extensions app?
I can't remember what all Extensions are enabled by default, but I
Well for the short bit that I've been using the system after disabling
all the extensions through the Extensions app, I have not experienced
any freeze. I will report back after the end of the day if I see any
more freezes though.
Interestingly, after disabling all Extensions, I have no more dock
Hi Daniel, I disabled all of these extensions, and then rebooted the
machine and still a minute or two after logging in again experienced the
freeze. Here are the logs from gnome-shell:
https://pastebin.ubuntu.com/p/YKtMQ2qy4g/
Note, I only disabled the extensions located in ~/.local/share/gnome-
Public bug reported:
I recently upgrading from Focal to Groovy, and use proprietary NVIDIA
drivers with X11 with otherwise standard GNOME, but some extensions
installed. I see frequently errors relating to the dash-to-dock
extension which I'm not sure are related, but I also see that gnome-
shell
Any rough idea on if / when we will see this in 20.04?
--
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/1899206
Title:
Input device settings not applied on hotplug/reconnect/resume in
Public bug reported:
After installing 20.04, in the gnome control center I selected the right
mouse button to be the primary button. When I unplug the mouse and
replug it in, the right mouse button is no longer the primary button.
When I look at the gnome control center, the setting says that the
Can I add a +1 to this. Am using Gnome 3.63.3 on 20.04. The 'is ready'
notifications from 'Microsoft Teams - Preview' are numerous and
completely pointless, as more often than not, nothing noticeable has
actually happened in the application. It's extremely distracting, as I
don't know when the noti
Still affected
NVIDIA GeForce GTX 1070
Nvidia driver 440.100
$ apt-cache policy libmutter-6-0
libmutter-6-0:
Installed: 3.36.4-0ubuntu0.20.04.2
Candidate: 3.36.4-0ubuntu0.20.04.2
Version table:
*** 3.36.4-0ubuntu0.20.04.2 500
500 http://gb.archive.ubuntu.com/ubuntu focal-updates/m
Public bug reported:
With Ubuntu 20.04, GDM 3.34.1 (bundled with Focal), and the proprietary
NVIDIA drivers, I am unable to use Wayland to login, and can only use
XOrg. Debugging this a little, I found that wayland support is wholesale
disabled when proprietary NVIDIA drivers are used by this rule
Thanks folks, this works for me now as well.
--
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/1825593
Title:
Display scale not remembered when X11 Fractional Scaling is enabled
To ma
Daniel, it sounds then like you are saying this is a duplicate of
1873403?
--
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/1869042
Title:
[nvidia] fractional monitor scaling fails du
(the issues here originally were that the screens go black and that I
couldn't set the main monitor after changing scaling, for which I filed
1873266, as per your request)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubunt
** Summary changed:
- [nvidia] cannot change main monitor after setting scaling for monitors
+ [nvidia] with x11 fractional scaling enabled, cannot change main monitor
after setting scaling for monitors
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
Okay, so now looking back at this bug, I see that when I have Focal with
X11 and the 440 nvidia drivers enabled, I can set scaling to integer
multiples without problems, but enabling fractional scaling and then
using a fractional scaling results in the black screen problem mentioned
in this bug as
Daniel, I just turned off fractional scaling and I no longer have this
problem, so for me at least with nvidia drivers and focal, I don't see
this bug and instead see 1825593 as you mentioned.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscrib
Also, if I disable Fractional Scaling, it now works to use/apply these
settings in any order
--
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/1873266
Title:
[nvidia] cannot change mai
Yes, 'Fractional Scaling' is enabled, sorry I should have specified. I
am unable to actually use fractional scaling however due to
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1869042
** Changed in: mutter (Ubuntu)
Status: Incomplete => New
--
You received this bug notification b
Hi Daniel, I tried your instructions and there is no difference between
~/.config/monitors.xml and monitors-before.xml. Both files specify the
desired configuration, but upon logging in the monitors are in the wrong
configuration.
Let me know if there's anything else I can try to help debug this i
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1873266/+attachment/5356137/+files/ProcCpuinfoMinimal.txt
** Changed in: mutter (Ubuntu)
Status: Incomplete => Opinion
** Changed in: mutter (Ubuntu)
Status: Opinion => New
--
You
apport information
** Tags added: apport-collected focal package-from-proposed
** Description changed:
After booting with nvidia drivers, if I change which monitor is the main
one first, then change the scaling from 100% to 200%, it works. But
doing this in the inverse direction, by first
Daniel, I filed that issue as
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1873266
--
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/1869042
Title:
[nvidia] all monitor scalin
Public bug reported:
After booting with nvidia drivers, if I change which monitor is the main
one first, then change the scaling from 100% to 200%, it works. But
doing this in the inverse direction, by first setting the scaling and
then changing the main monitor, it fails and the screens go black.
I should point out that the behavior in comment #9 happens when I am
using the nvidia 440 drivers.
I still cannot use fractional scaling with the nvidia drivers
successfully under any ordering, but I can at least use 200% scaling if
I set it first, then set the main monitor it works.
--
You rece
Just to clarify, I still see this bug with Focal and X11 and nvidia
drivers
--
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/1292398
Title:
Second screen position isn't saved fro
It is still unfortunately happening to me, but I also have a new
permutation of this, my machine also happens to suffer from
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1292398, so when I
boot up my machine the incorrect monitor layout is present, and I find
that if I first set the main m
Is this perhaps a duplicate of
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1869750 ?
--
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/1869042
Title:
[nvidia] all monitor sca
Actually after testing this out, I was able to use fractional scaling
with X11 again by using the nouveau driver instead of the proprietary
nvidia driver, which on my machine is at nvidia-440. This is a
sufficient work-around for me, it's unfortunate I can't use the
proprietary nvidia driver with f
FWIW, if I switch to using the noveau driver and then login via Wayland,
I can enable fractional scaling through Settings and that is successful,
but unfortunately then all the text in some apps becomes rather blurry.
--
You received this bug notification because you are a member of Ubuntu
Deskto
Oddly enough I was able to get 200% scaling to work randomly by not
quite lining up all the monitors and offsetting them from each other in
the settings window.
Is there anything I could try manually to unbreak the situation or is
there a debian package I could downgrade to in order to get scaling
Attaching monitors.xml since it doesn't seem that apport picked it up
** Attachment added: "~/.config/monitors.xml from my system"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1869042/+attachment/5341610/+files/monitors.xml
--
You received this bug notification because you are a mem
Public bug reported:
After an upgrade with focal-proposed this morning, I am unable to set
any scaling for any of my monitors without the monitor turning blank for
15 seconds and reverting to 100% scaling.
I am using X11 with gnome and proprietary nvidia drivers on Focal. I
have 3 monitors attach
Just to be clear, the messages:
```
snapd.failure.service is a disabled or a static unit, not starting it.
snapd.snap-repair.service is a disabled or a static unit, not starting it.
```
are normal and harmless.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bug
Jeremy Soller's fix to edit Xwrapper seems to be good.
The edits to the gdm service cause a crash to happen on boot.
Currently using an HP Laptop with an Intel CPU and Nvidia GPU that I
believe is Optimus.
I have the proprietary Nvidia driver running on nvidia-driver-430 as of
this comment's dat
** Summary changed:
- gvfsd-http leaves a lot of sockets in CLOSE_WAIT state
+ buy adderall online overnight delivery in usa
** This bug is no longer a duplicate of bug 760344
gvfsd-http not closing tcp connections
** Description changed:
+ Order Now
+ buy Adderall online overnight delivery
This affects a new snap we uploaded with license metadata to the store
around December 2018. We uploaded the snap and used the snap store
description editor to choose "Other Open Source" software and it shows
up as "Proprietary" in gnome-software.
--
You received this bug notification because you
Public bug reported:
The icon is replaced with the default "no-icon" icon, only way to bring
it back is to use "snap revert" to revert it to version 3.28 back from
3.29.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-characters (not installed)
ProcVersionSignature: Ubuntu 4.15.0-36.3
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 of
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 out.ps
I did the -proposed version if seems to me all is good (but I'm new to
this - so take it with a grain of salt).
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1768541
Title:
I can also report that in 16.04 LTS that selecting a fixed pin is not an
option in the GUI. I originally posted a question on AskUbuntu and found
my way here.
AskUbuntu Question: https://askubuntu.com/questions/947255/missing-pin-
options-from-bluetooth-pairing-gui
I've attached an image I made c
Public bug reported:
Notice just popped up on screen, did not really notice anything
ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: libpam-gnome-keyring:amd64 3.20.0-3ubuntu2
ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
Uname: Linux 4.10.0-26-generic x86_64
ApportVersion:
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.
https://bugs.launchpad.net/bugs
(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:
verify digit
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.
https://bugs.launchpad.net/bugs/
(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 pdf d
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.
https://bu
(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 th
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.
https://b
(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 th
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
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
** Changed in: unity
Status: In Progress => Confirmed
** Changed in: unity
Assignee: Seth Johnson (sethj) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.ne
(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 chan
(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
Tit
(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 t
(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 chan
(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
Tit
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 t
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
** Branch unlinked: lp:~sethj/ubuntu/wily/unity/fix-for-1445595
--
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/1445595
Title:
Empty trash from Launcher results in Nautilus window
1 - 100 of 383 matches
Mail list logo
