[Bug 1644149] [NEW] Sleeping monitor rewakes and displays broken version of lock page
Public bug reported: I am running a dual monitor desktop. After I lock the system the screens go dark and then sleep. However at some point (minutes, hours?) one of the screens re-awakes and displays a broken version of the lock screen (Ubuntu logo in center, version towards the bottom). The stays displayed indefinitely until I login. I'm running Ubuntu 16.10 (installed, not an upgrade) on a desktop. Monitors are both Samsung SyncMasters 2443's and video card is "NVIDIA Corporation GF108 [GeForce GT 430]". The Primary (left) is plugged in via DVI while secondary (right) is plugged in via VGA. Resolution is 1920x1200 on both. The "bad" screen is distorted from the normal lock screen in that: (a) It is not centered (b) It is a darker blue than my actual screen background (that I see right after locking) (c) There is a white grid of dots (d) the is a black line across the screen level with the Ubuntu version. See attach photo. Expected behavior: Screen stays turned off. I previously had 16.04 on this machine, did not have this problem. Description:Ubuntu 16.10 Release:16.10 gnome-screensaver: Installed: 3.6.1-7ubuntu5 Candidate: 3.6.1-7ubuntu5 Version table: *** 3.6.1-7ubuntu5 500 500 http://nz.archive.ubuntu.com/ubuntu yakkety/main amd64 Packages 100 /var/lib/dpkg/status ** Affects: gnome-screensaver (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Photo of screens showing problem." https://bugs.launchpad.net/bugs/1644149/+attachment/4781956/+files/IMG_20161123_223111.jpg -- 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/1644149 Title: Sleeping monitor rewakes and displays broken version of lock page To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1644149/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1644149] Re: Sleeping monitor rewakes and displays broken version of lock page
Followup photo from this morning. Right hand side is the "problem" scrren that was running when I came to the computer. Left hand screen was initially off but woke up to the login/unlock screen when I pressed a key. Note colors on left are completely different (and match my normal settings) and correctly centered etc. ** Attachment added: "Photo of screens side by side" https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1644149/+attachment/4782150/+files/IMG_20161124_080643.jpg -- 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/1644149 Title: Sleeping monitor rewakes and displays broken version of lock page To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1644149/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1397614] [NEW] gnupg error message: WARNING: The GNOME keyring manager hijacked the GnuPG agent
Public bug reported: Running gnupg will generate the error message: gpg: WARNING: The GNOME keyring manager hijacked the GnuPG agent. gpg: WARNING: GnuPG will not work properly - please configure that tool to not interfere with the GnuPG system! Cause: The gnupg maintainer doesn't like GNOME keyring http://bugs.gnupg.org/gnupg/issue1656 fix: Editing or deleting /etc/xdg/autostart/gnome-keyring-gpg.desktop will probably fix the problem according to advice, but this is a little hard for an end user. Needed: Simple solution for end user Really Needed: GNOME keyring and Gnupg maintainers need to sort out their differences in a way that doesn't screw users. ** Affects: gnome-keyring (Ubuntu) Importance: Undecided Status: New -- 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/1397614 Title: gnupg error message: WARNING: The GNOME keyring manager hijacked the GnuPG agent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1397614/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1225629] Re: shotwell crashed with SIGSEGV in publishing_accounts_uoa_publisher_authenticator_on_processed()
I just had a crash. Happened the instant I tried to publish to flickr. I upgraded to 14.10 yesterday and have had several crashes since, uploads seem to work about 50% of the time. I ran with: export SHOTWELL_LOG=1 export G_MESSAGES_DEBUG=all shotwell & attached shotwell.log but not all details seem to be there. ** Attachment added: "shotwell.log from flickr uploaded crash" https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1225629/+attachment/4271026/+files/shotwell.log -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/1225629 Title: shotwell crashed with SIGSEGV in publishing_accounts_uoa_publisher_authenticator_on_processed() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1225629/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1225629] Re: shotwell crashed with SIGSEGV in publishing_accounts_uoa_publisher_authenticator_on_processed()
Forgot to post crash message. shotwell:21178): Gtk-DEBUG: Connecting to session manager *** Error in `shotwell': corrupted double-linked list: 0x0890d7d0 *** -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/1225629 Title: shotwell crashed with SIGSEGV in publishing_accounts_uoa_publisher_authenticator_on_processed() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1225629/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1225629] Re: shotwell crashed with SIGSEGV in publishing_accounts_uoa_publisher_authenticator_on_processed()
On Tue, 2 Dec 2014, Jim Nelson wrote: > The Flickr double-free crash is reported at bug #1382843 (and easily > reproduced). I don't know that it's the same as the bug reported for > this ticket, so I'm not marking as a duplicate. Looking at #1382843 this is almost certainly what I am seeing rather than this one. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/1225629 Title: shotwell crashed with SIGSEGV in publishing_accounts_uoa_publisher_authenticator_on_processed() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1225629/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1335600] [NEW] Publishing to flickr broken since api.flickr went https-only
Public bug reported: The flickr api went to https only on June 27th 2014. It appears the shotwell is still using http so "publishing" to flickr no longer works. https://code.flickr.net/2014/04/30/flickr-api-going-ssl-only-on-june- 27th-2014/ Problem appears to be present in: Shotwell 0.15.0-0ubuntu1 on Ubuntu 13.10 Shotwell 0.18.0-0ubuntu4 on Ubuntu 14.04 Error is as follows, within a second or two of hitting the "publish" button. Publishing to Flickr can't contineu because an error occurred: Service http://api.flickr.com.services/rest returned HTTP status code 403 Forbidden To Try publishing to another service select one from the above menu. I last published a week ago with no problems. ** Affects: shotwell (Ubuntu) Importance: Undecided Status: New ** Description changed: The flickr api went to https only on June 27th 2014. It appears the shotwell is still using http so "publishing" to flickr no longer works. https://code.flickr.net/2014/04/30/flickr-api-going-ssl-only-on-june- 27th-2014/ Problem appears to be present in: Shotwell 0.15.0-0ubuntu1 on Ubuntu 13.10 Shotwell 0.18.0-0ubuntu4 on Ubuntu 14.04 Error is as follows, within a second or two of hitting the "publish" button. Publishing to Flickr can't contineu because an error occurred: Service http://api.flickr.com.services/rest returned HTTP status code 403 Forbidden - To Try publishing to another service select one from the above menu. + To Try publishing to another service select one from the above menu. - I last pushing a week ago with no problems. + I last published a week ago with no problems. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/1335600 Title: Publishing to flickr broken since api.flickr went https-only To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1335600/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1335600] Re: Publishing to flickr broken since api.flickr went https-only
** Description changed: The flickr api went to https only on June 27th 2014. It appears the shotwell is still using http so "publishing" to flickr no longer works. https://code.flickr.net/2014/04/30/flickr-api-going-ssl-only-on-june- 27th-2014/ Problem appears to be present in: Shotwell 0.15.0-0ubuntu1 on Ubuntu 13.10 Shotwell 0.18.0-0ubuntu4 on Ubuntu 14.04 Error is as follows, within a second or two of hitting the "publish" button. - Publishing to Flickr can't contineu because an error occurred: + Publishing to Flickr can't continue because an error occurred: Service http://api.flickr.com.services/rest returned HTTP status code 403 Forbidden To Try publishing to another service select one from the above menu. I last published a week ago with no problems. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/1335600 Title: Publishing to flickr broken since api.flickr went https-only To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1335600/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 380863] [NEW] Some pages of document appear blank
Public bug reported: Binary package hint: evince Document I have has every page after 2nd ( first two pages are covers from separate source ) appears to be blank. Document loads correctly in acrobat and xpdf however. Error message from evince: Error (308869): 8280 extraneous bytes after segment Error (308917): 3 extraneous bytes after segment Error (308933): Unknown segment type in JBIG2 stream Error (311333): Unexpected EOF in JBIG2 stream Error (281792): 2350 extraneous bytes after segment Error (281840): 3 extraneous bytes after segment Error (281856): Unknown segment type in JBIG2 stream Error (286320): Unexpected EOF in JBIG2 stream Error (24): 1908 extraneous bytes after segment Error (288932): 3 extraneous bytes after segment Error (288948): Unknown segment type in JBIG2 stream Error (290452): Unexpected EOF in JBIG2 stream Error (297572): 6506 extraneous bytes after segment Error (297620): 3 extraneous bytes after segment Error (297636): Unknown segment type in JBIG2 stream Error (299956): Unexpected EOF in JBIG2 stream and so on. Description:Ubuntu 9.04 Release:9.04 GNOME Document Viewer 2.26.1 I cannot post document here but I'm happy to send via email. ProblemType: Bug Architecture: i386 DistroRelease: Ubuntu 9.04 ExecutablePath: /usr/bin/evince NonfreeKernelModules: nvidia Package: evince 2.26.1-0ubuntu1 ProcEnviron: SHELL=/bin/bash PATH=(custom, user) LANG=en_NZ.UTF-8 SourcePackage: evince Uname: Linux 2.6.28-11-generic i686 ** Affects: evince (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 -- Some pages of document appear blank https://bugs.launchpad.net/bugs/380863 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 380863] Re: Some pages of document appear blank
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/27195622/Dependencies.txt ** Attachment added: "ProcMaps.txt" http://launchpadlibrarian.net/27195623/ProcMaps.txt ** Attachment added: "ProcStatus.txt" http://launchpadlibrarian.net/27195624/ProcStatus.txt ** Description changed: Binary package hint: evince Document I have has each page after 2nd ( first two pages are covers from separate source ) appears to be black. - Document loads correctling in acrobat and xpdf however. Error message - from evince: + Document loads correctly in acrobat and xpdf however. Error message from + evince: Error (308869): 8280 extraneous bytes after segment Error (308917): 3 extraneous bytes after segment Error (308933): Unknown segment type in JBIG2 stream Error (311333): Unexpected EOF in JBIG2 stream Error (281792): 2350 extraneous bytes after segment Error (281840): 3 extraneous bytes after segment Error (281856): Unknown segment type in JBIG2 stream Error (286320): Unexpected EOF in JBIG2 stream Error (24): 1908 extraneous bytes after segment Error (288932): 3 extraneous bytes after segment Error (288948): Unknown segment type in JBIG2 stream Error (290452): Unexpected EOF in JBIG2 stream Error (297572): 6506 extraneous bytes after segment Error (297620): 3 extraneous bytes after segment Error (297636): Unknown segment type in JBIG2 stream Error (299956): Unexpected EOF in JBIG2 stream and so on. Description: Ubuntu 9.04 Release: 9.04 GNOME Document Viewer 2.26.1 - I can post document here but I'm happy to send via email. + I cannot post document here but I'm happy to send via email. ProblemType: Bug Architecture: i386 DistroRelease: Ubuntu 9.04 ExecutablePath: /usr/bin/evince NonfreeKernelModules: nvidia Package: evince 2.26.1-0ubuntu1 ProcEnviron: SHELL=/bin/bash PATH=(custom, user) LANG=en_NZ.UTF-8 SourcePackage: evince Uname: Linux 2.6.28-11-generic i686 ** Description changed: Binary package hint: evince - Document I have has each page after 2nd ( first two pages are covers - from separate source ) appears to be black. + Document I have has every page after 2nd ( first two pages are covers + from separate source ) appears to be blank. Document loads correctly in acrobat and xpdf however. Error message from evince: Error (308869): 8280 extraneous bytes after segment Error (308917): 3 extraneous bytes after segment Error (308933): Unknown segment type in JBIG2 stream Error (311333): Unexpected EOF in JBIG2 stream Error (281792): 2350 extraneous bytes after segment Error (281840): 3 extraneous bytes after segment Error (281856): Unknown segment type in JBIG2 stream Error (286320): Unexpected EOF in JBIG2 stream Error (24): 1908 extraneous bytes after segment Error (288932): 3 extraneous bytes after segment Error (288948): Unknown segment type in JBIG2 stream Error (290452): Unexpected EOF in JBIG2 stream Error (297572): 6506 extraneous bytes after segment Error (297620): 3 extraneous bytes after segment Error (297636): Unknown segment type in JBIG2 stream Error (299956): Unexpected EOF in JBIG2 stream and so on. Description: Ubuntu 9.04 Release: 9.04 GNOME Document Viewer 2.26.1 I cannot post document here but I'm happy to send via email. ProblemType: Bug Architecture: i386 DistroRelease: Ubuntu 9.04 ExecutablePath: /usr/bin/evince NonfreeKernelModules: nvidia Package: evince 2.26.1-0ubuntu1 ProcEnviron: SHELL=/bin/bash PATH=(custom, user) LANG=en_NZ.UTF-8 SourcePackage: evince Uname: Linux 2.6.28-11-generic i686 -- Some pages of document appear blank https://bugs.launchpad.net/bugs/380863 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 380863] Re: Some pages of document appear blank
Document attached since it seems to be required. ** Attachment added: "Sam Collins - An Attacking Repertoire for White.pdf" http://launchpadlibrarian.net/27380886/Sam%20Collins%20-%20An%20Attacking%20Repertoire%20for%20White.pdf -- Some pages of document appear blank https://bugs.launchpad.net/bugs/380863 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 380863] Re: Some pages of document appear blank
Changed to Status new since attched problem file. ** Changed in: evince (Ubuntu) Status: Incomplete => New -- Some pages of document appear blank https://bugs.launchpad.net/bugs/380863 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 380863] Re: Some pages of document appear blank
removed attached file since bug fixed and probably not the sort of thing we want to keep in the bug tracker ** Attachment removed: "Sam Collins - An Attacking Repertoire for White.pdf" https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/380863/+attachment/597937/+files/Sam%20Collins%20-%20An%20Attacking%20Repertoire%20for%20White.pdf -- Some pages of document appear blank https://bugs.launchpad.net/bugs/380863 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
