[Bug 1467943] Re: system shutdown hangs if btrfs on file image (mounted via cifs) is mounted
I can only reach the `systemd` debug shell randomly, i.e. the system freezes either before I can press Ctrl+Alt+F9, right after it so that I can't run `journalctl -ab > /root/journal.txt` or right after running the command so that data isn't written to `/root/journal.txt` because the system can apparently only be rebooted with Ctrl+Alt+SysRq+b so that the data is never written to the filesystem (btrfs). After 5 failures at different states I couldn't recognize any pattern which causes the freeze. The start of debugging shell works consistently well if the btrfs image isn't mounted. ** Changed in: systemd (Ubuntu) Status: Expired => New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1467943 Title: system shutdown hangs if btrfs on file image (mounted via cifs) is mounted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1467943/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1502570] Re: gnome-panel indirectly installs evolution
This was actually a duplicate of bug #1381232. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in Ubuntu. https://bugs.launchpad.net/bugs/1502570 Title: gnome-panel indirectly installs evolution To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1502570/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1230169] Re: screensaver turns on while watching youtube video
I'm having a simmilar problem with yomvi player (silverlight activated with pipelight). I'm using devel repos. I'm having this problem since ubuntu 14.04 and in the end I have to disable screensaver and energy saving. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1230169 Title: screensaver turns on while watching youtube video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1230169/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 938751] Re: jpeg images are washed out or colors are skewed
I was wondering about this as well, but I figured that it doesn't seem to be a bug at all. The reason why it looks for some of you "correct" in Gimp is, because you don't have color management for your monitor enabled in the preferences (either set a specific monitor profile there, or tick the fallback option, which will make it use the color profile from the window manager). Thus, what Gimp is showing you all is the image without your monitor profile applied, while EOG always uses your monitor profile. So when the image in EOG looks dull to you, that's actually how it's supposed to look like. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/938751 Title: jpeg images are washed out or colors are skewed To manage notifications about this bug go to: https://bugs.launchpad.net/eog/+bug/938751/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 771272] Re: gnome-keyring doesn't support ecdsa or ed25519 keys
** Summary changed: - ssh-add does not handle ECDSA keys until ssh-agent exports are manually launched + gnome-keyring doesn't support ecdsa or ed25519 keys -- 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/771272 Title: gnome-keyring doesn't support ecdsa or ed25519 keys To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-keyring/+bug/771272/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1489632] Re: gedit fails to display line with > 1000000 characters
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gedit (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1489632 Title: gedit fails to display line with > 100 characters To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1489632/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1504871] [NEW] package libpam-systemd:amd64 204-5ubuntu20.14 failed to install/upgrade: subprocess installed post-installation script returned error exit status 100
Public bug reported: error ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libpam-systemd:amd64 204-5ubuntu20.14 ProcVersionSignature: Ubuntu 3.19.0-30.34~14.04.1-generic 3.19.8-ckt6 Uname: Linux 3.19.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.15 Architecture: amd64 Date: Sat Oct 10 21:11:15 2015 DuplicateSignature: package:libpam-systemd:amd64:204-5ubuntu20.14:subprocess installed post-installation script returned error exit status 100 ErrorMessage: subprocess installed post-installation script returned error exit status 100 InstallationDate: Installed on 2015-10-10 (0 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) RelatedPackageVersions: dpkg 1.17.5ubuntu5.4 apt 1.0.1ubuntu2.10 SourcePackage: systemd Title: package libpam-systemd:amd64 204-5ubuntu20.14 failed to install/upgrade: subprocess installed post-installation script returned error exit status 100 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package trusty -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1504871 Title: package libpam-systemd:amd64 204-5ubuntu20.14 failed to install/upgrade: subprocess installed post-installation script returned error exit status 100 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1504871/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1315705] Re: [Acer Aspire 5750-9668] touchpad doesn't scroll with one finger on extreme right in GNOME Flashback (Metacity)
** Tags added: wily -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in Ubuntu. https://bugs.launchpad.net/bugs/1315705 Title: [Acer Aspire 5750-9668] touchpad doesn't scroll with one finger on extreme right in GNOME Flashback (Metacity) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-panel/+bug/1315705/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1284308] Re: Can't copy files from a bluetooth device: Another operation in progress
** Tags added: wily -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1284308 Title: Can't copy files from a bluetooth device: Another operation in progress To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1284308/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 676401] Re: PDF Links not working in evince
** Tags added: wily -- 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/676401 Title: PDF Links not working in evince To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/676401/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 510376] Re: private/teletext-decoder plugin missing
The Bug exist since 5 years... no fix? Ubuntu 14.04 the same. When i'am installing the gnome-codec-install i have this error Die Parameter für die Anwendung hatten ein ungültiges Format. Bitte berichten sie den Fehler! Die Parameter waren: --transient-for=117440527 gstreamer|1.0|totem|Teletext decoder|decoder-application/x-teletext Without this package: Totempluginviewer need teletextdecoder extension -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gstreamer0.10 in Ubuntu. https://bugs.launchpad.net/bugs/510376 Title: private/teletext-decoder plugin missing To manage notifications about this bug go to: https://bugs.launchpad.net/gstreamer/+bug/510376/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1453912] Re: systemd does not unlock dm-crypt password
[Expired for systemd (Ubuntu) because there has been no activity for 60 days.] ** Changed in: systemd (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1453912 Title: systemd does not unlock dm-crypt password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1453912/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1226962] Re: Hotkeys not functional in non-latin keyboard layout
attente - Your PPA works great. I'm using alt+left Shift with no problems. Thank you very much. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1226962 Title: Hotkeys not functional in non-latin keyboard layout To manage notifications about this bug go to: https://bugs.launchpad.net/aptana-studio-installer/+bug/1226962/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1468199] Re: package gconf2 3.2.6-3ubuntu1 failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回错误状态 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gconf (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1468199 Title: package gconf2 3.2.6-3ubuntu1 failed to install/upgrade: 子进程 已安装 post- installation 脚本 返回错误状态 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1468199/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 113338] Re: Cannot close a tab in Gedit by middle clicking the tab bar
** Changed in: gedit (Ubuntu) Status: Invalid => Triaged ** Changed in: gedit (Ubuntu) Assignee: Ubuntu Desktop Bugs (desktop-bugs) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/113338 Title: Cannot close a tab in Gedit by middle clicking the tab bar To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/113338/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1500600] [NEW] Impossible to empty trash with 50000 files inside
You have been subscribed to a public bug: Xubuntu 14.04.3 with latest sec. Updates. The only way to empty trash is to use terminal. ** Affects: gvfs (Ubuntu) Importance: Undecided Status: New -- Impossible to empty trash with 5 files inside https://bugs.launchpad.net/bugs/1500600 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1500600] Re: Impossible to empty trash with 50000 files inside
** Package changed: xfdesktop4 (Ubuntu) => gvfs (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1500600 Title: Impossible to empty trash with 5 files inside To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1500600/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1504659] Re: Duplicate line for path "/var/log"
It's just a warning: the rsyslog package ships /usr/lib/tmpfiles.d/00rsyslog.conf which also ships a config for /var/log, so the one in var.conf is ignored. ** Changed in: systemd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1504659 Title: Duplicate line for path "/var/log" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1504659/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1335613] Re: Bad interaction between "code snippets" and "autocompletion plugin" in gedit
Upstream states it's fixed in newest versions ** Changed in: gedit (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1335613 Title: Bad interaction between "code snippets" and "autocompletion plugin" in gedit To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/1335613/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1226962] Re: Hotkeys not functional in non-latin keyboard layout
See http://www.whizzy.org/2015/09/big-bug-bonanza-16-04-lts/ for a sprint to fix issues in Ubuntu (targeting 16.04). Since there are patches for this and these patches work, it is important to get the issue fixed during the sprint. On Sat, Oct 10, 2015 at 10:49 AM, OrDuek <1226...@bugs.launchpad.net> wrote: > attente - > Your PPA works great. I'm using alt+left Shift with no problems. > Thank you very much. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1226962 > > Title: > Hotkeys not functional in non-latin keyboard layout > > Status in aptana-studio-installer: > New > Status in Default settings and artwork for Baltix OS: > New > Status in LibreOffice Productivity Suite: > Fix Released > Status in ibus: > New > Status in Indicator keyboard: > Fix Released > Status in Inkscape: > New > Status in monodevelop: > New > Status in mutter: > Fix Released > Status in okular: > New > Status in OpenOffice: > New > Status in sigram: > New > Status in Unity: > Fix Released > Status in gnome-settings-daemon package in Ubuntu: > Triaged > Status in gnome-terminal package in Ubuntu: > Triaged > Status in openjdk-7 package in Ubuntu: > Incomplete > Status in unity package in Ubuntu: > Triaged > Status in unity-settings-daemon package in Ubuntu: > Triaged > Status in gnome-shell package in Fedora: > Unknown > Status in openoffice package in Fedora: > Unknown > > Bug description: > New keyboard layout changer in Ubuntu 13.10 introduce old-new bug. Any > system or application hotkey witch use char (for example: ctrl+alt+t for > terminal or ctrl+t for new tab in browser) become unfunctional when > selected non-latin keyboard layout. > Hotkeys with F1-12, numbers and other non-character buttons works > perfectly. > > Window manager hotkeys not affected by this bug. All hotkeys in system > parameters->keyboard->hotkeys->windows works perfect with any keyboard > layout. > > Workaround for some system hotkeys and two layouts (english and non- > latin): rebind all hotkeys in your local layout. For example instead > of ctrl+alt+t use ctrl+alt+τ (greek tau). That hotkey still work with > english layout. If you use english and two different non-latin > layouts this workaround helps only with one of them. > > > Dear Ubuntu users and developers! > Please include the following information to your comment about non-latin > shortcuts problems: > 1. What Ubuntu version do you have (Ubuntu 13.10, Ubuntu 13.10 GNOME, > Ubuntu 14.04, Ubuntu 14.04 GNOME and so on), upgraded (describe version) or > clean installed > 2. What keyboard layout do you have > 3. What shortcut for keyboard layout switching do you use > 4. On which session you have problems - that is one from Unity, GNOME > Shell, GNOME FlashBack/Fallback (Metacity), GNOME FlashBack/Fallback > (Compiz) > 5. With which program and its version and origin (Ubuntu repositories, > PPA, non-deb binary package from some website) you have problems. > > By providing this information you can make bug-fixing much simpler and > may be faster. > > -- > For other layout switching problems introduced in Ubuntu 13.10 you can > see bug 1218322. > -- > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/aptana-studio-installer/+bug/1226962/+subscriptions > -- CONFIDENTIALITY This e-mail and any attachments are confidential and may also be privileged. If you are not the named recipient, please notify the sender immediately and do not disclose the contents to another person, use it for any purpose, or store or copy the information in any medium. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1226962 Title: Hotkeys not functional in non-latin keyboard layout To manage notifications about this bug go to: https://bugs.launchpad.net/aptana-studio-installer/+bug/1226962/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1085526]
(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 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? > > > Did i forget something? Large file support. -- 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 notifications about this bug go to: https://bugs.launchpad.net/poppler/+bug/1085526/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1085526]
(In reply to Andre Guerreiro from comment #76) > Created attachment 118745 [details] [review] > Incremental hashing + large file support > > With this patch I've implemented the incremental hashing plus the large file > support. > > This is still untested with files larger than 2GB but is correct for all the > regular test cases I gathered before. 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 stream and the handler? This should give the compiler more optimization possibilities than if it is visible in other translation units. * I think the while loop within could become a for loop for better readability with the case reduced to computing the number of bytes to read instead of two separate calls to doGetChars and updateHash. -- 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 notifications about this bug go to: https://bugs.launchpad.net/poppler/+bug/1085526/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1085526]
Created attachment 118745 Incremental hashing + large file support With this patch I've implemented the incremental hashing plus the large file support. This is still untested with files larger than 2GB but is correct for all the regular test cases I gathered before. -- 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 notifications about this bug go to: https://bugs.launchpad.net/poppler/+bug/1085526/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1085526]
(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 release. A couple of questions: - Given that we want to keep the option open for using pdfsig to perform other signature operations, should the default behavior when only a pdf file is specified be to verify the signature? Or should we just indicate whether the pdf is signed and use an option to enable verification? - Is '-c' the best option name for "don't perform certificate validation"? We also need a man page. -- 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 notifications about this bug go to: https://bugs.launchpad.net/poppler/+bug/1085526/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1085526]
(In reply to Adrian Johnson from comment #71) > (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 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? > > > > > > Did i forget something? > > Large file support. Do you think this should be a blocker for the initial release or something we can improve later? -- 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 notifications about this bug go to: https://bugs.launchpad.net/poppler/+bug/1085526/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1085526]
(In reply to Adrian Johnson from comment #78)
> I agree that the two calls to doGetChars and updateHash should be merged but
> I don't think a for loop is the best way to process loops where the
> increment is not exactly the same on each iteration. Maybe something like
> this:
>
> void FormFieldSignature::hashSignedByteRange(SignatureHandler *handler,
> Goffset start, Goffset len)
> {
> const int CHUNK_SIZE = 4096;
> unsigned char buffer[CHUNK_SIZE];
> Goffset i = 0;
> int byte_count = CHUNK_SIZE;
>
> doc->getBaseStream()->setPos(start);
> while (i < len)
> {
> if (i + CHUNK_SIZE > len)
> byte_count = len - i;
>
> doc->getBaseStream()->doGetChars(byte_count, buffer);
> handler->updateHash(buffer, byte_count);
> i += byte_count;
> }
> }
I was thinking of something like
doc->getBaseStream()->setPos(start);
for (Goffset offset = 0; offset < len; offset += CHUNK_SIZE)
{
const int byte_count = min(CHUNK_SIZE, len - offset);
doc->getBaseStream()->doGetChars(byte_count, buffer);
handler->updateHash(buffer, byte_count);
}
to make the loop more regular as we don't care if offset > len instead
of offset == len after the last iteration. (That code was not tested or
even compiled.)
> I don't mind if we fix all this later. It doesn't have to hold up the
> initial release.
Maybe if there is some external pressure to release this, but otherwise
I'd propose polishing it now, since there is a certain momentum not to
touch working code once it is released.
Best regards, Adam.
--
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 notifications about this bug go to:
https://bugs.launchpad.net/poppler/+bug/1085526/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1085526]
(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 stream and the handler? This should give the compiler
> more optimization possibilities than if it is visible in other translation
> units.
>
> * I think the while loop within could become a for loop for better
> readability with the case reduced to computing the number of bytes to read
> instead of two separate calls to doGetChars and updateHash.
I don't think there is much benefit in making that function a static. It
is not something that is called a frequently from an inner loop.
I think the function would read better as "hashSignedByteRange" as "byte
range" is the terminology used in the PDF reference section in
signatures. Instead of setting the stream offset before calling this
function it would better easier to understand the code if the function
took an offset and length.
I agree that the two calls to doGetChars and updateHash should be merged
but I don't think a for loop is the best way to process loops where the
increment is not exactly the same on each iteration. Maybe something
like this:
void FormFieldSignature::hashSignedByteRange(SignatureHandler *handler,
Goffset start, Goffset len)
{
const int CHUNK_SIZE = 4096;
unsigned char buffer[CHUNK_SIZE];
Goffset i = 0;
int byte_count = CHUNK_SIZE;
doc->getBaseStream()->setPos(start);
while (i < len)
{
if (i + CHUNK_SIZE > len)
byte_count = len - i;
doc->getBaseStream()->doGetChars(byte_count, buffer);
handler->updateHash(buffer, byte_count);
i += byte_count;
}
}
I renamed the "signed_data_buffer" to "buffer" as whenever I see
"signed" in C/C++ I think of the integer type. "unsigned char
signed_data_buffer" is confusing to read.
I would prefer the buffer be moved out to the class. It is better not to
allocate large buffers on the stack. We may later increase the buffer
size.
I don't mind if we fix all this later. It doesn't have to hold up the
initial release.
--
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 notifications about this bug go to:
https://bugs.launchpad.net/poppler/+bug/1085526/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1085526]
(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 or something > > > we can improve later? > > > > I think it should be included. > > Do you have any file like that or a way to create it so the guys can test it? I don't have a file. Bug 44085 contains a large file test case. But I don't know how to sign it. Implementing large file support is simply a case of using obj.isInt64()/ obj.getInt64() when getting the range offsets. In addition, the code should avoid reading the entire range into memory instead processing it in smaller chunks. From a quick look a the nss headers it appears to have support for incremental hashing. This is good practice even for < 2GB files as I have seen scanned PDFs that are in the 100's of MB range. I don't mind adding the getInt64() stuff myself as that is easy to do without needing to understand the rest of the code. But the incremental hashing would best be done by the original developer of the patch. So at a a minimum if we can get the incremental hashing in then I can sort out the rest of the 64-bit support. -- 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 notifications about this bug go to: https://bugs.launchpad.net/poppler/+bug/1085526/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1085526]
(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 or something > > we can improve later? > > I think it should be included. Do you have any file like that or a way to create it so the guys can test it? -- 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 notifications about this bug go to: https://bugs.launchpad.net/poppler/+bug/1085526/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1085526]
+ 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 offset and later assume it is 0? Why do we assume there are exactly two pairs. I only skimmed over the digital signatures section so maybe I missed something. -- 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 notifications about this bug go to: https://bugs.launchpad.net/poppler/+bug/1085526/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1085526]
(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, 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 notifications about this bug go to: https://bugs.launchpad.net/poppler/+bug/1085526/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1368647] Re: GPS and location detection not working on Nexus 4
GPS is still a bit "iffy" and now worse since upgrading to current build number: 23 I can no longer seem to get GPS from Nokia HERE service Nokia's GPS location service - System Settings > Security & Privacy > Location access > " Using GPS, anonymised Wi-Fi and mobile network info." is no longer accessible. and it takes a age to get GPS from sattelite Looking into the logs I see:- /var/log/upstart/ubuntu-espoo-service.log HERE binaries not found; disabling ubuntu-espoo-service stop/pre-start, process 7700 HERE binaries not found; disabling ubuntu-espoo-service stop/pre-start, process 3932 after trying to start espoo service sudo service ubuntu-espoo-service start my last /var/log/upstart/ubuntu-espoo-service.log.1.gz is from June So I guess that is the last time this was working I have tried reinstalling the latest Ubuntu Touch image but to no avail. sudo apt-get install --reinstall ubuntu-location-provider-here after making the filesystem read/write makes no difference How would one go about installing the missing HERE binaries? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1368647 Title: GPS and location detection not working on Nexus 4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1368647/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 740506]
(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 stream and the handler? This should give the compiler
> more optimization possibilities than if it is visible in other translation
> units.
>
> * I think the while loop within could become a for loop for better
> readability with the case reduced to computing the number of bytes to read
> instead of two separate calls to doGetChars and updateHash.
I don't think there is much benefit in making that function a static. It
is not something that is called a frequently from an inner loop.
I think the function would read better as "hashSignedByteRange" as "byte
range" is the terminology used in the PDF reference section in
signatures. Instead of setting the stream offset before calling this
function it would better easier to understand the code if the function
took an offset and length.
I agree that the two calls to doGetChars and updateHash should be merged
but I don't think a for loop is the best way to process loops where the
increment is not exactly the same on each iteration. Maybe something
like this:
void FormFieldSignature::hashSignedByteRange(SignatureHandler *handler,
Goffset start, Goffset len)
{
const int CHUNK_SIZE = 4096;
unsigned char buffer[CHUNK_SIZE];
Goffset i = 0;
int byte_count = CHUNK_SIZE;
doc->getBaseStream()->setPos(start);
while (i < len)
{
if (i + CHUNK_SIZE > len)
byte_count = len - i;
doc->getBaseStream()->doGetChars(byte_count, buffer);
handler->updateHash(buffer, byte_count);
i += byte_count;
}
}
I renamed the "signed_data_buffer" to "buffer" as whenever I see
"signed" in C/C++ I think of the integer type. "unsigned char
signed_data_buffer" is confusing to read.
I would prefer the buffer be moved out to the class. It is better not to
allocate large buffers on the stack. We may later increase the buffer
size.
I don't mind if we fix all this later. It doesn't have to hold up the
initial release.
--
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 to:
https://bugs.launchpad.net/evince/+bug/740506/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 740506]
(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 or something > > we can improve later? > > I think it should be included. Do you have any file like that or a way to create it so the guys can test it? -- 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 to: https://bugs.launchpad.net/evince/+bug/740506/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 740506]
(In reply to Adrian Johnson from comment #78)
> I agree that the two calls to doGetChars and updateHash should be merged but
> I don't think a for loop is the best way to process loops where the
> increment is not exactly the same on each iteration. Maybe something like
> this:
>
> void FormFieldSignature::hashSignedByteRange(SignatureHandler *handler,
> Goffset start, Goffset len)
> {
> const int CHUNK_SIZE = 4096;
> unsigned char buffer[CHUNK_SIZE];
> Goffset i = 0;
> int byte_count = CHUNK_SIZE;
>
> doc->getBaseStream()->setPos(start);
> while (i < len)
> {
> if (i + CHUNK_SIZE > len)
> byte_count = len - i;
>
> doc->getBaseStream()->doGetChars(byte_count, buffer);
> handler->updateHash(buffer, byte_count);
> i += byte_count;
> }
> }
I was thinking of something like
doc->getBaseStream()->setPos(start);
for (Goffset offset = 0; offset < len; offset += CHUNK_SIZE)
{
const int byte_count = min(CHUNK_SIZE, len - offset);
doc->getBaseStream()->doGetChars(byte_count, buffer);
handler->updateHash(buffer, byte_count);
}
to make the loop more regular as we don't care if offset > len instead
of offset == len after the last iteration. (That code was not tested or
even compiled.)
> I don't mind if we fix all this later. It doesn't have to hold up the
> initial release.
Maybe if there is some external pressure to release this, but otherwise
I'd propose polishing it now, since there is a certain momentum not to
touch working code once it is released.
Best regards, Adam.
--
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 to:
https://bugs.launchpad.net/evince/+bug/740506/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 740506]
(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 release. A couple of questions: - Given that we want to keep the option open for using pdfsig to perform other signature operations, should the default behavior when only a pdf file is specified be to verify the signature? Or should we just indicate whether the pdf is signed and use an option to enable verification? - Is '-c' the best option name for "don't perform certificate validation"? We also need a man page. -- 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 to: https://bugs.launchpad.net/evince/+bug/740506/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 740506]
(In reply to Adrian Johnson from comment #71) > (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 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? > > > > > > Did i forget something? > > Large file support. Do you think this should be a blocker for the initial release or something we can improve later? -- 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 to: https://bugs.launchpad.net/evince/+bug/740506/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 740506]
+ 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 offset and later assume it is 0? Why do we assume there are exactly two pairs. I only skimmed over the digital signatures section so maybe I missed something. -- 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 to: https://bugs.launchpad.net/evince/+bug/740506/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 740506]
(In reply to Andre Guerreiro from comment #76) > Created attachment 118745 [details] [review] > Incremental hashing + large file support > > With this patch I've implemented the incremental hashing plus the large file > support. > > This is still untested with files larger than 2GB but is correct for all the > regular test cases I gathered before. 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 stream and the handler? This should give the compiler more optimization possibilities than if it is visible in other translation units. * I think the while loop within could become a for loop for better readability with the case reduced to computing the number of bytes to read instead of two separate calls to doGetChars and updateHash. -- 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 to: https://bugs.launchpad.net/evince/+bug/740506/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 740506]
Created attachment 118745 Incremental hashing + large file support With this patch I've implemented the incremental hashing plus the large file support. This is still untested with files larger than 2GB but is correct for all the regular test cases I gathered before. -- 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 to: https://bugs.launchpad.net/evince/+bug/740506/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 740506]
(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 or something > > > we can improve later? > > > > I think it should be included. > > Do you have any file like that or a way to create it so the guys can test it? I don't have a file. Bug 44085 contains a large file test case. But I don't know how to sign it. Implementing large file support is simply a case of using obj.isInt64()/ obj.getInt64() when getting the range offsets. In addition, the code should avoid reading the entire range into memory instead processing it in smaller chunks. From a quick look a the nss headers it appears to have support for incremental hashing. This is good practice even for < 2GB files as I have seen scanned PDFs that are in the 100's of MB range. I don't mind adding the getInt64() stuff myself as that is easy to do without needing to understand the rest of the code. But the incremental hashing would best be done by the original developer of the patch. So at a a minimum if we can get the incremental hashing in then I can sort out the rest of the 64-bit support. -- 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 to: https://bugs.launchpad.net/evince/+bug/740506/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 740506]
(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, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/740506 Title: verify digital signatures To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/740506/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 740506]
(In reply to Andre Guerreiro from comment #67) > Created attachment 118449 [details] [review] > Support for adbe.pkcs7.sha1 signatures > > This patch, to be applied over the previous one, adds support for > adbe.pkcs7.sha1 signatures so now we should have a more complete coverage of > actual signed PDFs. I have a few adbe.x509.rsa_sha1 in case you need them for testing. -- 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 to: https://bugs.launchpad.net/evince/+bug/740506/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 740506]
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 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? Did i forget something? -- 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 to: https://bugs.launchpad.net/evince/+bug/740506/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 740506]
(In reply to Andre Guerreiro from comment #66) > Created attachment 118446 [details] [review] > NSS conditional build > > This patch makes the NSS dependency optional in the CMake and Autotools > build systems. Commited too to the signatureHandling branch with some minor changes on my side to have fewer -- 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 to: https://bugs.launchpad.net/evince/+bug/740506/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 740506]
(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 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? > > > Did i forget something? Large file support. -- 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 to: https://bugs.launchpad.net/evince/+bug/740506/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1085526]
(In reply to Andre Guerreiro from comment #67) > Created attachment 118449 [details] [review] > Support for adbe.pkcs7.sha1 signatures > > This patch, to be applied over the previous one, adds support for > adbe.pkcs7.sha1 signatures so now we should have a more complete coverage of > actual signed PDFs. I have a few adbe.x509.rsa_sha1 in case you need them for testing. -- 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 notifications about this bug go to: https://bugs.launchpad.net/poppler/+bug/1085526/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1085526]
(In reply to Andre Guerreiro from comment #66) > Created attachment 118446 [details] [review] > NSS conditional build > > This patch makes the NSS dependency optional in the CMake and Autotools > build systems. Commited too to the signatureHandling branch with some minor changes on my side to have fewer -- 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 notifications about this bug go to: https://bugs.launchpad.net/poppler/+bug/1085526/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1085526]
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 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? Did i forget something? -- 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 notifications about this bug go to: https://bugs.launchpad.net/poppler/+bug/1085526/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1504659] Re: Duplicate line for path "/var/log"
I understand it is a warning-- my point is that the default system shouldn't have this warning so I don't think Invalid is a proper status for this bug. Marking back to New. If after reconsidering you choose to not fix it, feel free to mark it as Won't Fix. ** Changed in: systemd (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1504659 Title: Duplicate line for path "/var/log" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1504659/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 771272] Re: ssh-add does not handle ECDSA keys until ssh-agent exports are manually launched
Bump. Same thing, still not fixed 5 years later. -- 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/771272 Title: ssh-add does not handle ECDSA keys until ssh-agent exports are manually launched To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-keyring/+bug/771272/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1502509] Re: Show disk utilization - feature request
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-system-monitor (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1502509 Title: Show disk utilization - feature request To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-system-monitor/+bug/1502509/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1502509] Re: Show disk utilization - feature request
** Description changed: - I think that it would be really good if the System Monitor displayed - disk utilization among the things it already displays. This would be - really useful in a line graph. And I have heard and seen many people - wanting a feature like this so I think that it would be a really good - new feature to implement. + It would be really good if the System Monitor displayed disk + utilization. This would be really useful in a line graph. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1502509 Title: Show disk utilization - feature request To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-system-monitor/+bug/1502509/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
