[Bug 1506532] Re: Update to stable release 3.18.1
Ok, but then why he does not say that it is an unstable version?? https://wiki.gnome.org/Apps/Evolution I understand what you put me is the original source. I fully understand the impossibility that they can not enter now working in the sector and would not be safe to make the update now. I hope you continue updating the 16.04 And apologies for making you lose development time. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1506532 Title: Update to stable release 3.18.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1506532/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1251281] Re: gnome-session-flashback/Unity fails to start without hardware acceleration in cloud/remote environments (Forwarded-X/XRDP/VNC/NX/X2GO/Chromoting)
drhc, again, this report is closed, so commenting here is a waste of time. File a support request against whatever Ubuntu GUI you are using as already previously requested (not continue to comment here in a closed report). -- 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/1251281 Title: gnome-session-flashback/Unity fails to start without hardware acceleration in cloud/remote environments (Forwarded-X/XRDP/VNC/NX/X2GO/Chromoting) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-session/+bug/1251281/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1507218] Re: rhythmbox crashed with SIGABRT in g_assertion_message()
*** This bug is a duplicate of bug 1444580 *** https://bugs.launchpad.net/bugs/1444580 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1444580, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1507218/+attachment/4498353/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1507218/+attachment/4498355/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1507218/+attachment/4498359/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1507218/+attachment/4498360/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1507218/+attachment/4498361/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1507218/+attachment/4498362/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1507218/+attachment/4498363/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1444580 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1507218 Title: rhythmbox crashed with SIGABRT in g_assertion_message() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1507218/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1168978] Re: Evince crashes consistently, reading 50+ pages into specific PDF document
** Changed in: evince Status: Confirmed => Unknown -- 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/1168978 Title: Evince crashes consistently, reading 50+ pages into specific PDF document To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/1168978/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 438520] Re: Right Alt key is always selected under "key to choose 3rd level"
[Expired for console-setup (Ubuntu) because there has been no activity for 60 days.] ** Changed in: console-setup (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/438520 Title: Right Alt key is always selected under "key to choose 3rd level" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/438520/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1405912] Re: Evince eats all CPU and all memory
** Changed in: evince Status: New => Expired -- 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/1405912 Title: Evince eats all CPU and all memory To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/1405912/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 586528] Re: keyboard doesn't work after screensaver shuts down the monitor
@Václav Haisman, this 3 bugs where reported in 2010, i have tested this bug in 15.04 unity DE, there are no bug, if you have bug provide your steps to reproduce otherwise this will be closed on Monday. P.s. In 5 years in codebase of gnome-screensaver were a lot changes this bug seems to be fixed without marking this bug report as "closed". Don't argue if you think i'm not right, just provide steps to reproduce it, i will try this, if your steps will cause this bug, i will triagle this bug so devs can fix this. if you dont have valid steps to reproduce, there are no need to write to devs, they wouldn't fix this. Cheers. -- 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/586528 Title: keyboard doesn't work after screensaver shuts down the monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/586528/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 586528] Re: keyboard doesn't work after screensaver shuts down the monitor
@Lysenko: FFS, there was somebody else commenting on this issues this month. The bug is still the same, there is nothing else to add to this. The reproduction scenario is still the same. -- 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/586528 Title: keyboard doesn't work after screensaver shuts down the monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/586528/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1449700] Re: evince crashed with SIGSEGV in add_range()
** Changed in: evince Status: Confirmed => Incomplete -- 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/1449700 Title: evince crashed with SIGSEGV in add_range() To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/1449700/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1463326] Re: org.gnome.ScreenSaver: WARNING **: Couldn't get presence status: The name org.gnome.SessionManager was not provided by any .service files
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-screensaver (Ubuntu) Status: New => Confirmed -- 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/1463326 Title: org.gnome.ScreenSaver: WARNING **: Couldn't get presence status: The name org.gnome.SessionManager was not provided by any .service files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1463326/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1507123] [NEW] Keyboard doesn't work when screensaver shuts down the monitor
Public bug reported: The keyboard doesn't work when I return to work on the computer after a few minutes, long enough for the screen to go blank. To reproduce: Don't touch the keyboard nor mouse for a while. After the first 5 minutes, the screensaver kicks in (matrix). On minute 10, the screen goes blank. Wait a few more minutes. Move the mouse or press a key to keep working. Just type something in the window you have already opened you'll notice that the active window does not receive any keyboard input, and you can't even press alt-tab to switch to another window. Of course, i expect the keyboard to work as usual but it does not. Here, when the keyboard doesn't work, you can switch to another window using the mouse and the keyboard will return to normal. ** Affects: gnome-screensaver (Ubuntu) Importance: Undecided Assignee: Abhishek solanki (abhisheksolanki18) Status: New ** Changed in: gnome-screensaver (Ubuntu) Assignee: (unassigned) => Abhishek solanki (abhisheksolanki18) -- 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/1507123 Title: Keyboard doesn't work when screensaver shuts down the monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1507123/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 586528] Re: keyboard doesn't work after screensaver shuts down the monitor
I am on 15.04. That it does not happen to you does not mean it does not happen to others. ** Changed in: gnome-screensaver (Ubuntu) Status: Invalid => Confirmed ** Changed in: xscreensaver (Ubuntu) Status: Invalid => Confirmed -- 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/586528 Title: keyboard doesn't work after screensaver shuts down the monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/586528/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1506532] Re: Update to stable release 3.18.1
Thanks for reporting. It's probably too close to the release of 15.10 to risk introducing a new version at this point, but hopefully someone will take a look at this for the next release. I noticed that 3.18 has been packaged in Debian unstable already, so maybe it is simply a case of merging (or possibly syncing) that version to Ubuntu. (https://tracker.debian.org/pkg/evolution) ** Tags removed: evolution ** Tags added: needs-debian-merge upgrade-software-version -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1506532 Title: Update to stable release 3.18.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1506532/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 792085] Re: Automatic remount of safely removed drive
FYI --- using command line to eject the disk/partiton do work, see http://askubuntu.com/questions/422481/prevent-usb-drives-from-auto- remounting-after-remove On the other hand, I see surprising that this bug is marked Medium. For non-tech-savy users, can ends in unclean disconnect and even data-loss. Should be marked as Critical. -- 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/792085 Title: Automatic remount of safely removed drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/792085/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1390270] Re: Ubuntu 14.10 lockscreen requires password for passwordless accounts
** Changed in: gnome-screensaver (Ubuntu) Status: Confirmed => Fix Committed -- 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/1390270 Title: Ubuntu 14.10 lockscreen requires password for passwordless accounts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1390270/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1500673] Re: gdm unusable after upgrading to 15.10
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gdm (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/1500673 Title: gdm unusable after upgrading to 15.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1500673/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1506704] Re: Thin font, nautilus doesn't integrate with Unity.
Please see in the screenshot: 1. Thin font in the clock. 2. An extra button (three horizontal lines) for bringing up the Menu in Nautilus. 3. Thin font in Nautilus (filenames). 4. The correct font in System Settings. EXPECTED: A. Font in Nautilus should be the same as in System Settings. B. The Extra button in Nautilus should not be there. ** Attachment added: "Thin font in Nautilus and the clock." https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1506704/+attachment/4497544/+files/Screenshot%20from%202015-10-17%2008-55-46.png -- 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/1506704 Title: Thin font, nautilus doesn't integrate with Unity. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1506704/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1436555] Re: evince crashed with SIGSEGV in atk_object_notify_state_change()
** Changed in: evince Importance: Medium => Critical -- 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/1436555 Title: evince crashed with SIGSEGV in atk_object_notify_state_change() To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/1436555/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1440549] Re: please convert python scripts to python3
This bug was fixed in the package gconf - 3.2.6-3ubuntu5 --- gconf (3.2.6-3ubuntu5) wily; urgency=medium * Call dh_python3 with --shebang=/usr/bin/python3. LP: #1440549. -- Matthias KloseFri, 16 Oct 2015 16:34:16 +0200 ** Changed in: gconf (Ubuntu) Status: New => Fix Released -- 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/1440549 Title: please convert python scripts to python3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1440549/+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 #80) > (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? I think defaulting to verification makes sense as the "non destructive thing to do". > - Is '-c' the best option name for "don't perform certificate validation"? 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. > > We also need a man page. Yep. -- 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 #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 the other formats. I don't want pdfsig to end up in the same situation. -- 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 Adam Reichold from comment #81) > (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. If we're too picky it may just die in this branch and never be merged :D > > 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 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. I've pushed this, Adrian, Adam please suggest your improvements over it with a patch if you reached an agreement. -- 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 #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 the other formats. I don't want pdfsig to end up in the same situation. -- 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 #80) > (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? I think defaulting to verification makes sense as the "non destructive thing to do". > - Is '-c' the best option name for "don't perform certificate validation"? 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. > > We also need a man page. Yep. -- 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 740506]
(In reply to Adam Reichold from comment #81) > (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. If we're too picky it may just die in this branch and never be merged :D > > 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 #82) > > - Is '-c' the best option name for "don't perform certificate validation"? > > 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. It's vital to put thought into "naming things" before a poor decision becomes permanent because it becomes public. At the very least, "-c" suggests check and "-C" would often be the negative don't check, even if no -c option exists because it's the default. And then there's the issue Adrian raises. -- 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. I've pushed this, Adrian, Adam please suggest your improvements over it with a patch if you reached an agreement. -- 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 Albert Astals Cid from comment #82) > > - Is '-c' the best option name for "don't perform certificate validation"? > > 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. It's vital to put thought into "naming things" before a poor decision becomes permanent because it becomes public. At the very least, "-c" suggests check and "-C" would often be the negative don't check, even if no -c option exists because it's the default. And then there's the issue Adrian raises. -- 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 797485] Re: Status Bar Covers File Name at Bottom
For the love of all that's holy... Please fix this because it is driving me insane! -- 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/797485 Title: Status Bar Covers File Name at Bottom To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/797485/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1501250] Re: double clicking on a URL drops the protocol from the URL
Double click is not meant to select a URL (there's an option in the right click menu for that), and adding colon to the list of word-chars won't fix it either. E.g. if you have a URL with a trailing dot (which strictly speaking could be a part of the URL, but usually denotes the end of a sentence) then double click will select that, whereas Ctrl+click or Right click -> copy URL won't consider that to be part of the URL. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1501250 Title: double clicking on a URL drops the protocol from the URL To manage notifications about this bug go to: https://bugs.launchpad.net/vte/+bug/1501250/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 586528] Re: keyboard doesn't work after screensaver shuts down the monitor
@Václav Haisman please provide clear steps for reproduce, otherwise i will close this. Bug creator unsubscribe yesterday. If you will not, i will close this in 2 days. -- 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/586528 Title: keyboard doesn't work after screensaver shuts down the monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/586528/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1507123] Re: Keyboard doesn't work when screensaver shuts down the monitor
** Changed in: gnome-screensaver (Ubuntu) Assignee: Abhishek solanki (abhisheksolanki18) => (unassigned) -- 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/1507123 Title: Keyboard doesn't work when screensaver shuts down the monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1507123/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1441867] Re: First entered password at lockscreen is always wrong after screen was turned off after inactivity
I have tested this yesterday, and i don't have this issue, may be because i have 4 digit password on system i have tested on, and i'm entering password on numpad? gnome-screensaver: Installed: 3.6.1-0ubuntu16 Ubuntu 15.04, Unity DE -- 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/1441867 Title: First entered password at lockscreen is always wrong after screen was turned off after inactivity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1441867/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 586528] Re: keyboard doesn't work after screensaver shuts down the monitor
@Lysenko: 22 people confirmed this. There are 2 duplicates attached to this bug report and then there is #1483868 that I was requested to fill separately. Yet, you want to close this bug. Are you for real? I have nothing more to say, except expletives. -- 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/586528 Title: keyboard doesn't work after screensaver shuts down the monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/586528/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1437921] Re: gnome-disks crashed with SIGSEGV in g_dbus_object_get_interface()
I got the same issue while creating a partition on a normal sata connection. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1437921 Title: gnome-disks crashed with SIGSEGV in g_dbus_object_get_interface() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1437921/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1488469] [NEW] GIMP crashes on startup
You have been subscribed to a public bug: GIMP was functioning normally then after restart received following error launching GIMP: Gtk-Message: Failed to load module "pantheon-filechooser-module" Bus error (core dumped) gimp Also received: Gtk-Message: Failed to load module "canberra-gtk-module" (installed: libcanberra-gtk-module:i386, which resolved that error.) Recently I installed: AdbeRdr9.5.5-1_i386linux_enu.deb (if thats at all helpful). ** Affects: gimp (Ubuntu) Importance: Undecided Status: New -- GIMP crashes on startup https://bugs.launchpad.net/bugs/1488469 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gimp in Ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1507123] Re: Keyboard doesn't work when screensaver shuts down the monitor
*** This bug is a duplicate of bug 586528 *** https://bugs.launchpad.net/bugs/586528 ** This bug has been marked a duplicate of bug 586528 keyboard doesn't work after screensaver shuts down the monitor -- 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/1507123 Title: Keyboard doesn't work when screensaver shuts down the monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1507123/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 633958] Re: Topmost window "unable" to get keystrokes after unlock
*** This bug is a duplicate of bug 1483868 *** https://bugs.launchpad.net/bugs/1483868 ** This bug is no longer a duplicate of bug 586528 keyboard doesn't work after screensaver shuts down the monitor ** This bug has been marked a duplicate of bug 1483868 keyboard doesn't work after xscreensaver shuts down the monitor -- 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/633958 Title: Topmost window "unable" to get keystrokes after unlock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/633958/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1507123] Re: Keyboard doesn't work when screensaver shuts down the monitor
*** This bug is a duplicate of bug 1483868 *** https://bugs.launchpad.net/bugs/1483868 ** This bug is no longer a duplicate of bug 586528 keyboard doesn't work after screensaver shuts down the monitor ** This bug has been marked a duplicate of bug 1483868 keyboard doesn't work after xscreensaver shuts down the monitor -- 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/1507123 Title: Keyboard doesn't work when screensaver shuts down the monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1507123/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 586528] Re: keyboard doesn't work after screensaver shuts down the monitor
*** This bug is a duplicate of bug 1483868 *** https://bugs.launchpad.net/bugs/1483868 You have opened bug report #1483868 https://bugs.launchpad.net/ubuntu/+source/xscreensaver/+bug/1483868 you had been asked questions to complete your bug report, and to help find out where exactly problem is. Why you ignored it? This bug report will be closed as original reported unsubscribe, and it were reported in unsupported now Ubuntu version. If you want to add something new - modify your bug report, provide more information to help fix it. Thanks. ** Changed in: gnome-screensaver (Ubuntu) Status: Confirmed => Invalid ** Changed in: xscreensaver (Ubuntu) Status: Confirmed => Invalid ** This bug has been marked a duplicate of bug 1483868 keyboard doesn't work after xscreensaver shuts down the monitor -- 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/586528 Title: keyboard doesn't work after screensaver shuts down the monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/586528/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1251281] Re: gnome-session-flashback/Unity fails to start without hardware acceleration in cloud/remote environments (Forwarded-X/XRDP/VNC/NX/X2GO/Chromoting)
adrhc, as this report is closed, it has nothing to do with your problem. If you have an issue with RDP'ing to Ubuntu while using gnome-session- flashback, you either haven't configured it properly (more likely as I can use Windows RDC to connect to Vivid using gnome-session-flashback just fine), or you have a corner case bug (not very likely). Hence, please file a support request (not a bug report) via https://answers.launchpad.net/ubuntu/+source/gnome-panel/+addquestion . Please feel free to subscribe me to it. -- 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/1251281 Title: gnome-session-flashback/Unity fails to start without hardware acceleration in cloud/remote environments (Forwarded-X/XRDP/VNC/NX/X2GO/Chromoting) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-session/+bug/1251281/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1500671] Re: Gnome terminal crashes when double clicking profile
The problem is in gnome-terminal, affects Ubuntu and Ubuntu Gnome in 15.10 as of 17 Oct 2015. Unity is not involved. ** Also affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Changed in: unity Status: New => Invalid ** Changed in: gnome-terminal (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1500671 Title: Gnome terminal crashes when double clicking profile To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1500671/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1251281] Re: gnome-session-flashback/Unity fails to start without hardware acceleration in cloud/remote environments (Forwarded-X/XRDP/VNC/NX/X2GO/Chromoting)
Thanks, but I said nothing about gnome-session-flashback. I have no gnome-session-flashback and gnome-flashback package installed (also I know nothing about them). Instead I have the same result: "4) What happens instead is it shows a gray static screen as per attached screenshot." regardless of technical stuff behind ... -- 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/1251281 Title: gnome-session-flashback/Unity fails to start without hardware acceleration in cloud/remote environments (Forwarded-X/XRDP/VNC/NX/X2GO/Chromoting) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-session/+bug/1251281/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1497170] Re: New file creation - not opening with file editor
This bug was fixed in the package glib2.0 - 2.46.1-1 --- glib2.0 (2.46.1-1) unstable; urgency=medium [ Michael Biebl ] * Drop clean-la.mk from debian/rules, no longer required. [ Iain Lane ] * New upstream release 2.46.1 + Remove system_header pragma (should fix lack of warnings with things like g_return_if_fail) + move GStrv typedef (and auto-cleanup) from libgobject to libglib + fix order of trashing files to be closer to what is required in the specification. Namely, trashinfo files are written first. This should fix issues with the gvfs trash backend failing to correctly read the info for recently trashed files (preventing 'restore'). (Closes: #800491) (LP: #1495943) + tweak mime logic to return text/plain on all empty files instead of returning application/octet-stream. This includes files that have extensions that imply that they may be other types of files, which is a slight change of behaviour with respect to old GLib versions. (LP: #1497170) * debian/patches/0001-Revert-list-store-Fix-a-parameter-check.patch: Drop - this is applied upstream in this release. * debian/patches/0001-GDateTime-test-fix-occasional-failures.patch: Take patch from bgo#754994 to resolve intermittent test failures in the GDateTime tests. -- Iain LaneThu, 15 Oct 2015 16:08:30 +0100 ** Changed in: glib2.0 (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1497170 Title: New file creation - not opening with file editor To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1497170/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1495943] Re: gvfs-trash doesn't add "trash::" attrs to file which is moved to Trash
This bug was fixed in the package glib2.0 - 2.46.1-1 --- glib2.0 (2.46.1-1) unstable; urgency=medium [ Michael Biebl ] * Drop clean-la.mk from debian/rules, no longer required. [ Iain Lane ] * New upstream release 2.46.1 + Remove system_header pragma (should fix lack of warnings with things like g_return_if_fail) + move GStrv typedef (and auto-cleanup) from libgobject to libglib + fix order of trashing files to be closer to what is required in the specification. Namely, trashinfo files are written first. This should fix issues with the gvfs trash backend failing to correctly read the info for recently trashed files (preventing 'restore'). (Closes: #800491) (LP: #1495943) + tweak mime logic to return text/plain on all empty files instead of returning application/octet-stream. This includes files that have extensions that imply that they may be other types of files, which is a slight change of behaviour with respect to old GLib versions. (LP: #1497170) * debian/patches/0001-Revert-list-store-Fix-a-parameter-check.patch: Drop - this is applied upstream in this release. * debian/patches/0001-GDateTime-test-fix-occasional-failures.patch: Take patch from bgo#754994 to resolve intermittent test failures in the GDateTime tests. -- Iain LaneThu, 15 Oct 2015 16:08:30 +0100 ** Changed in: glib2.0 (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1495943 Title: gvfs-trash doesn't add "trash::" attrs to file which is moved to Trash To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1495943/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1488469] Re: GIMP crashes on startup
Thank you for taking the time to report this bug and helping to make Ubuntu better. I took the liberty of moving this bug report to the gimp package, since it doesn't seem to be related to radiotray. Do you consistently get this error message each time you attempt to run gimp? Also, could you please execute the following command, as it will automatically gather debugging information, in a terminal: apport-collect 1488469 When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Package changed: radiotray (Ubuntu) => gimp (Ubuntu) -- 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/1488469 Title: GIMP crashes on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1488469/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1507165] Re: file-roller crashed with SIGSEGV in g_cclosure_marshal_VOID__STRINGv()
*** This bug is a duplicate of bug 1286294 *** https://bugs.launchpad.net/bugs/1286294 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1286294, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1507165/+attachment/4498047/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1507165/+attachment/4498049/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1507165/+attachment/4498052/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1507165/+attachment/4498053/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1507165/+attachment/4498054/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1507165/+attachment/4498055/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1507165/+attachment/4498056/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1286294 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1507165 Title: file-roller crashed with SIGSEGV in g_cclosure_marshal_VOID__STRINGv() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1507165/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1505204] Re: Ubuntu 15.10 not copying files on vpn connection
After last updates This problem corrected. We can close the job Thanks Ertan ** Changed in: nautilus (Ubuntu) Status: New => Fix Released -- 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/1505204 Title: Ubuntu 15.10 not copying files on vpn connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1505204/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1479710] Re: /usr/bin/gnome-disks:11:g_dbus_object_get_interface:udisks_object_peek_drive:gdu_window_select_object:create_partition_cb:g_task_return_now
** Changed in: gnome-disk-utility Importance: Medium => Critical -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1479710 Title: /usr/bin/gnome- disks:11:g_dbus_object_get_interface:udisks_object_peek_drive:gdu_window_select_object:create_partition_cb:g_task_return_now To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-disk-utility/+bug/1479710/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs