[Desktop-packages] [Bug 1625773] [NEW] Segfault when using -w / --window to screenshot current window.
Public bug reported: The gnome-screenshot program segfaults every time, when I try to capture the current window with `gnome-screenshot -w`. Taking an area screenshot with `gnome-screenshot -a`, and taking a full desktop screenshot with `gnome-screenshot` works, but taking a current window screenshot with `gnome-screenshot -w` segfaults every time. Adding delay with `-d ` and capturing pointer or not with `-p` has no effect. This may be the same bug as https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/81817 although that one is closed long ago. The relationship is that I'm using gnome-screenshot inside the XMonad window manager, a non-standard window manager. Stack trace: $ gdb gnome-screenshot GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.04) 7.11.1 [...] Reading symbols from gnome-screenshot...(no debugging symbols found)...done. (gdb) core-file core warning: core file may not match specified executable file. [New LWP 25469] [New LWP 25472] [New LWP 25470] [New LWP 25471] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `gnome-screenshot -d 3 -w -p'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x0040dbb5 in ?? () [Current thread is 1 (Thread 0x7f3b4c841a40 (LWP 25469))] (gdb) where #0 0x0040dbb5 in ?? () #1 0x0040e1ea in ?? () #2 0x00408bc1 in ?? () #3 0x00408df9 in ?? () #4 0x7f3b4a5afac3 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f3b4a5af05a in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f3b4a5af400 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7f3b4a5af4ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x7f3b4ab76cdd in g_application_run () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #9 0x00408385 in ?? () #10 0x7f3b49a84830 in __libc_start_main (main=0x408320, argc=5, argv=0x7fff78989e68, init=, fini=, rtld_fini=, stack_end=0x7fff78989e58) at ../csu/libc-start.c:291 #11 0x004083c9 in ?? () System information: $ lsb_release -rd Description:Ubuntu 16.04.1 LTS Release:16.04 $ apt-cache policy gnome-screenshot gnome-screenshot: Installed: 3.18.0-1ubuntu2 Candidate: 3.18.0-1ubuntu2 Version table: *** 3.18.0-1ubuntu2 500 500 http://vault.galois.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status ** Affects: gnome-screenshot (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Core dump." https://bugs.launchpad.net/bugs/1625773/+attachment/4744505/+files/core -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screenshot in Ubuntu. https://bugs.launchpad.net/bugs/1625773 Title: Segfault when using -w / --window to screenshot current window. Status in gnome-screenshot package in Ubuntu: New Bug description: The gnome-screenshot program segfaults every time, when I try to capture the current window with `gnome-screenshot -w`. Taking an area screenshot with `gnome-screenshot -a`, and taking a full desktop screenshot with `gnome-screenshot` works, but taking a current window screenshot with `gnome-screenshot -w` segfaults every time. Adding delay with `-d ` and capturing pointer or not with `-p` has no effect. This may be the same bug as https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/81817 although that one is closed long ago. The relationship is that I'm using gnome-screenshot inside the XMonad window manager, a non- standard window manager. Stack trace: $ gdb gnome-screenshot GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.04) 7.11.1 [...] Reading symbols from gnome-screenshot...(no debugging symbols found)...done. (gdb) core-file core warning: core file may not match specified executable file. [New LWP 25469] [New LWP 25472] [New LWP 25470] [New LWP 25471] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `gnome-screenshot -d 3 -w -p'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x0040dbb5 in ?? () [Current thread is 1 (Thread 0x7f3b4c841a40 (LWP 25469))] (gdb) where #0 0x0040dbb5 in ?? () #1 0x0040e1ea in ?? () #2 0x00408bc1 in ?? () #3 0x00408df9 in ?? () #4 0x7f3b4a5afac3 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f3b4a5af05a in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f3b4a5af400 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7f3b4a5af4ac in g_main_context_iteration () from
[Desktop-packages] [Bug 1286430] Re: Suspend option when lid closed greyed out in Power Settings
I added the workaround referenced by https://bugs.launchpad.net/ubuntu/+source/gnome-power- manager/+bug/1286430/comments/8 to the bug description at the top. ** Description changed: + Workaround + == + + Based on https://bugs.launchpad.net/ubuntu/+source/gnome-power- + manager/+bug/1286430/comments/8. + + 1. Install the dconf-editor command if necessary: + + $ sudo apt-get install dconf-tools + + 2. Run dconf-editor and select + + org gnome settings-daemon plugins power + + 3. Set lid-close-ac-action and lid-close-battery-action to + suspend. + + The suspend option will now be selected in the Power Settings. It's + still greyed out, so if you change it to e.g. nothing you have to use + dconf-editor again to change it back to suspend. + + + Bug description + === + :~$ lsb_release -rd Description: Ubuntu Trusty Tahr (development branch) Release: 14.04 erich@erich-Aspire-5334:~$ apt-cache policy gnome-power-manager gnome-power-manager: - Installed: 3.8.2-1ubuntu2 - Candidate: 3.8.2-1ubuntu2 - Version table: - *** 3.8.2-1ubuntu2 0 - 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages - 100 /var/lib/dpkg/status + Installed: 3.8.2-1ubuntu2 + Candidate: 3.8.2-1ubuntu2 + Version table: + *** 3.8.2-1ubuntu2 0 + 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages + 100 /var/lib/dpkg/status If this is the incorrect package, please redirect. In power options for When the lid is closed no option is given except for Do Nothing. Suspend is there, but unselectable. Suspend should be a selectable option on laptop computers. As expected, closing laptop lid merely locks the screen. However, since Suspend cannot be selected, the option to suspend upon lid closing is unavailable. Expected: Suspend option selectable. Happened: Suspend option not selectable. Specs: Acer Aspire 5334, 4GB RAM, 320 GB HDD, Intel Celeron 2.0 Ghz. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-power-manager 3.8.2-1ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-13.33-generic 3.13.5 Uname: Linux 3.13.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Feb 28 19:34:27 2014 InstallationDate: Installed on 2014-02-28 (0 days ago) InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Release amd64 (20131017) ProcEnviron: - TERM=xterm - PATH=(custom, no user) - XDG_RUNTIME_DIR=set - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm + PATH=(custom, no user) + XDG_RUNTIME_DIR=set + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: gnome-power-manager UpgradeStatus: Upgraded to trusty on 2014-02-28 (0 days ago) - --- + --- ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-02-28 (0 days ago) InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Release amd64 (20131017) NonfreeKernelModules: wl Package: gnome-power-manager 3.8.2-1ubuntu2 PackageArchitecture: amd64 ProcEnviron: - TERM=xterm - PATH=(custom, no user) - XDG_RUNTIME_DIR=set - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm + PATH=(custom, no user) + XDG_RUNTIME_DIR=set + LANG=en_US.UTF-8 + SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.13.0-13.33-generic 3.13.5 Tags: trusty Uname: Linux 3.13.0-13-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-02-28 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1286430 Title: Suspend option when lid closed greyed out in Power Settings Status in gnome-power-manager package in Ubuntu: Confirmed Bug description: Workaround == Based on https://bugs.launchpad.net/ubuntu/+source/gnome-power- manager/+bug/1286430/comments/8. 1. Install the dconf-editor command if necessary: $ sudo apt-get install dconf-tools 2. Run dconf-editor and select org gnome settings-daemon plugins power 3. Set lid-close-ac-action and lid-close-battery-action to suspend. The suspend option will now be selected in the Power Settings. It's still greyed out, so if you change it to e.g. nothing you have to use dconf-editor again to change it back to suspend. Bug description === :~$ lsb_release -rd Description: Ubuntu Trusty Tahr (development branch) Release: 14.04 erich@erich-Aspire-5334:~$ apt-cache policy gnome-power-manager gnome-power-manager: Installed: 3.8.2-1ubuntu2 Candidate: 3.8.2-1ubuntu2 Version table: *** 3.8.2-1ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status If this
[Desktop-packages] [Bug 1423847] Re: Evince print blank pages for landscape pdfs when auto rotate and center is chosen
Will the fix be coming to 14.10? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1423847 Title: Evince print blank pages for landscape pdfs when auto rotate and center is chosen Status in Evince document viewer: Fix Released Status in evince package in Ubuntu: Fix Released Bug description: The title says it all. The document is printed if the auto-rotate and center is unchecked but of course that's not a solution since the image is cropped. I also tried printing to a pdf file, the resulting pdf seems correct but fails to print just the same. Printing from okular works fine although for some reason dual sided printing is greyed out (it used to work fine with evince before on my Laserjet 2055d). The problem seems known upstream (see https://bugzilla.gnome.org/show_bug.cgi?id=739723) I added a file exhibiting the problem. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: evince 3.14.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Feb 20 10:53:30 2015 InstallationDate: Installed on 2014-01-15 (400 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) ProcEnviron: LANGUAGE=fr_FR:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: Upgraded to utopic on 2015-02-15 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/1423847/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 694910] Re: Regression: patch to bug 539477 breaks Super+P keybindings
This is *really* annoying and confusing. Mod+p is a standard binding in xmonad. Mod4 is the common choice for Mod. Why should I have to change my xmonad configuration because some feature I don't care about or use wants that binding? And at minimum, why can't I disable this binding? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/694910 Title: Regression: patch to bug 539477 breaks Super+P keybindings Status in Gnome Settings Daemon: Won't Fix Status in “gnome-settings-daemon” package in Ubuntu: Confirmed Bug description: Binary package hint: gnome-settings-daemon The current patch to bug 539477 breaks the super+p keybinding for all user applications when running gnone-settings-daemon. This behavior is hard-coded, not discoverable, and not configurable. The workaround is to disable parts of xrandr such that screen switching is no longer possible. The patch has been checked in and released as a bugfix to Ubuntu 10.10, causing regressions in several applications. For more details, see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/539477/ particularly https://bugs.launchpad.net/ubuntu/+source/linux/+bug/539477/comments/68 and immediately above. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/694910/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
