[Desktop-packages] [Bug 1280726] Re: [ivb mesa] GPU hang while playing prison architect
Hello Christopher, Thanks for the help, but I no longer have that computer, so I cannot test if the bios update fixes the problem. ** Changed in: xserver-xorg-video-intel (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1280726 Title: [ivb mesa] GPU hang while playing prison architect Status in xserver-xorg-video-intel package in Ubuntu: Invalid Bug description: I've been playing with prison architect and when trying to create a building, it crashes (reproduced two times) It was working with 13.10. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.13.2-0ubuntu4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun Feb 16 09:29:57 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: psmouse, alps-fujitsu-1.0, 3.13.0-8-generic, x86_64: installed virtualbox, 4.3.6, 3.13.0-8-generic, x86_64: installed DuplicateSignature: GPU lockup IPEHR: 0x7808000b Ubuntu 14.04 ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Fujitsu Limited. Device [10cf:16c1] InstallationDate: Installed on 2014-02-14 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140211) InterpreterPath: /usr/bin/python3.3 MachineType: FUJITSU LIFEBOOK S762 ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gpu-error-intel.py ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-8-generic.efi.signed root=UUID=8b5fc891-19a0-4908-9cc3-f35fc25b96da ro quiet splash vt.handoff=7 RelatedPackageVersions: xserver-xorg 1:7.7+1ubuntu8 libdrm2 2.4.52-1 xserver-xorg-video-intel 2:2.99.910-0ubuntu1 SourcePackage: xserver-xorg-video-intel Title: False GPU lockup IPEHR: 0x7808000b UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 10/09/2012 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.10 dmi.board.name: FJNB23A dmi.board.vendor: FUJITSU dmi.board.version: H3 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.chassis.version: LIFEBOOK S762 dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.10:bd10/09/2012:svnFUJITSU:pnLIFEBOOKS762:pvr10601186098:rvnFUJITSU:rnFJNB23A:rvrH3:cvnFUJITSU:ct10:cvrLIFEBOOKS762: dmi.product.name: LIFEBOOK S762 dmi.product.version: 10601186098 dmi.sys.vendor: FUJITSU version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu4 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.0.1-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.0.1-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sun Feb 16 09:14:39 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 474 vendor LGD xserver.version: 2:1.15.0-1ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1280726/+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 1280726] [NEW] False GPU lockup IPEHR: 0x7808000b while playing prison architect
Public bug reported: I've been playing with prison architect and when trying to create a building, it crashes (reproduced two times) It was working with 13.10. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.13.2-0ubuntu4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun Feb 16 09:29:57 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: psmouse, alps-fujitsu-1.0, 3.13.0-8-generic, x86_64: installed virtualbox, 4.3.6, 3.13.0-8-generic, x86_64: installed DuplicateSignature: GPU lockup IPEHR: 0x7808000b Ubuntu 14.04 ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Fujitsu Limited. Device [10cf:16c1] InstallationDate: Installed on 2014-02-14 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140211) InterpreterPath: /usr/bin/python3.3 MachineType: FUJITSU LIFEBOOK S762 ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gpu-error-intel.py ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-8-generic.efi.signed root=UUID=8b5fc891-19a0-4908-9cc3-f35fc25b96da ro quiet splash vt.handoff=7 RelatedPackageVersions: xserver-xorg 1:7.7+1ubuntu8 libdrm2 2.4.52-1 xserver-xorg-video-intel 2:2.99.910-0ubuntu1 SourcePackage: xserver-xorg-video-intel Title: False GPU lockup IPEHR: 0x7808000b UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 10/09/2012 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.10 dmi.board.name: FJNB23A dmi.board.vendor: FUJITSU dmi.board.version: H3 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.chassis.version: LIFEBOOK S762 dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.10:bd10/09/2012:svnFUJITSU:pnLIFEBOOKS762:pvr10601186098:rvnFUJITSU:rnFJNB23A:rvrH3:cvnFUJITSU:ct10:cvrLIFEBOOKS762: dmi.product.name: LIFEBOOK S762 dmi.product.version: 10601186098 dmi.sys.vendor: FUJITSU version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu4 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.0.1-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.0.1-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sun Feb 16 09:14:39 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 474 vendor LGD xserver.version: 2:1.15.0-1ubuntu6 ** Affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash compiz-0.9 false-gpu-hang freeze trusty ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1280726 Title: False GPU lockup IPEHR: 0x7808000b while playing prison architect Status in “xserver-xorg-video-intel” package in Ubuntu: New Bug description: I've been playing with prison architect and when trying to create a building, it crashes (reproduced two times) It was working with 13.10. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.13.2-0ubuntu4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun Feb 16 09:29:57 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: psmouse, alps-fujitsu-1.0, 3.13.0-8-generic, x86_64: installed virtualbox, 4.3.6, 3.13.0-8-generic, x86_64: installed DuplicateSignature: GPU lockup IPEHR: 0x7808000b Ubuntu 14.04 ExecutablePath:
[Desktop-packages] [Bug 1280779] [NEW] cant unlock sporadically it grays out the input field
Public bug reported: Sporadically after the screen is locked when I try to unlock it the input field looks gray and ignores any input. It happened on saucy and now also on trusty.. Tryed to hit ESC to hide and redisplay the prompt, or event suspending and waking the computer but none helps except going to a tty logging in and killing the screensaver. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-screensaver 3.6.1-0ubuntu9 ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 ApportVersion: 2.13.2-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Sun Feb 16 14:04:09 2014 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session session-name 'ubuntu' org.gnome.desktop.session idle-delay uint32 300 InstallationDate: Installed on 2014-02-14 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140211) SourcePackage: gnome-screensaver UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-screensaver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1280779 Title: cant unlock sporadically it grays out the input field Status in “gnome-screensaver” package in Ubuntu: New Bug description: Sporadically after the screen is locked when I try to unlock it the input field looks gray and ignores any input. It happened on saucy and now also on trusty.. Tryed to hit ESC to hide and redisplay the prompt, or event suspending and waking the computer but none helps except going to a tty logging in and killing the screensaver. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-screensaver 3.6.1-0ubuntu9 ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 ApportVersion: 2.13.2-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Sun Feb 16 14:04:09 2014 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session session-name 'ubuntu' org.gnome.desktop.session idle-delay uint32 300 InstallationDate: Installed on 2014-02-14 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140211) SourcePackage: gnome-screensaver UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1280779/+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 872806] Re: GIMP and unity-panel-service go mayhem while opening files
It happened to me when opened, resized, saved and closed png files in a row.. The slowness started around the 5. circle, and it gets worst and worst until I kill unity-panel-service -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/872806 Title: GIMP and unity-panel-service go mayhem while opening files Status in “gimp” package in Ubuntu: Confirmed Bug description: On my Sony Vaio VPCCA (Intel Sandy Bridge), when I select 37 JPG- images with together a size not more than 5 MB and open them with a rightclick and open with GIMP, GIMP opens them very, very slow. After having opened all pictures it takes about 30 seconds until GIMP is ready. The menus in the unity global menu don't work anymore, and I have to rightclick into an image to get the options. In the background GIMP, unity-panel-service and compiz go mayhem (see screenshot attached) and together sometimes take up over 150% CPU power. Working with images is impossible and GIMP sometimes accepts my changes of an image, sometimes not. This is very annoying!! I not sure, but this could have something to do with with unity/compiz, because I always have similar problems with other programs too. They are slow, laggy, the global menu is not working right, and sometimes the program simply crash without saying anything. On my xubuntu without compiz this stuff never happens with these programs, neither with GIMP. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/872806/+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
Re: [Desktop-packages] [Bug 160311] Re: Resizing windows by grabbing window borders is difficult
Actually the size of the shadow sounds as a good starting point! -- Eisenberger Tamás ta...@eisenberger.hu On Thu, Dec 22, 2011 at 10:07 AM, The Fiddler 160...@bugs.launchpad.netwrote: 2011/12/22 u-foka ta...@eisenberger.hu Maybe the best would be a configurable size for the hidden grab area :) Currently it's difficult to change, how I seen the size is hardcoded into the theme right? But is this really necessary? Three options: - review feedback and pick a sensible default value - add a new option to ccsm - link the actual radius with some other element that makes sense, e.g. the shadow decoration. KDE has a configurable border size somewhere in its theme options (option #2). Gnome 2 used to link the radius with the theme border (option #3). Windows and MacOS (Lion) don't have a configurable size, same as Unity (option #1). I am not sure about Gnome Shell (but the default size seems to be slightly larger than Unity). This is on of those cases where a sensible default, well, makes sense. A size of 8px or 10px would be easier to hit than 5px, without impacting usability negatively (i.e. it still falls within the visible shadow decoration, where you are unlikely to click to raise a window). It should be a relatively simple change with a negligible chance of regressions. -- You received this bug notification because you are subscribed to a duplicate bug report (638709). https://bugs.launchpad.net/bugs/160311 Title: Resizing windows by grabbing window borders is difficult To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/160311/+subscriptions -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/160311 Title: Resizing windows by grabbing window borders is difficult Status in Ayatana Design: Fix Released Status in One Hundred Paper Cuts: Fix Released Status in The Metacity Window Manager: In Progress Status in Release Notes for Ubuntu: Fix Released Status in Unity 2D: New Status in “human-gtk-theme” package in Ubuntu: Invalid Status in “light-themes” package in Ubuntu: Fix Released Status in “metacity” package in Ubuntu: Fix Released Status in “human-gtk-theme” source package in Maverick: Invalid Status in “light-themes” source package in Maverick: Triaged Status in “metacity” source package in Maverick: Triaged Bug description: * No more comments needed This should mostly be fixed for Natty and might get backported to earlier releases as well. * *Blueprint for Natty, Ubuntu 11.04: https://blueprints.edge.launchpad.net/ubuntu/+spec/packageselection- dx-n-resizing-windows Work items1 * Make sure the new resize grip fits in current applications; doesn't interfere with anything. We should make some noise about this during the Natty cycle so people keep their eyes open and file bugs. 2 * Invisible window resize area - around 3px invisible area to allow resize on all sides. * Working grip backported to gtk2 already available in ppa : https://launchpad.net/~bratsche/+archive/gtk * Workaround: Edit /usr/share/themes/Ambiance/metacity-1/metacity- theme-1.xml. Set the following values in frame_geometry_normal as desired: distance name=left_width value=3/ distance name=right_width value=3/ distance name=bottom_height value=3/ Binary package hint: metacity - The issue has been an issue for users (especially of large) screens for several releases- Trackpad users seem to be particularly impacted by this- The issue appears to have been significantly aggravated in Lucid by changing the border width from 3 pixels to 1 pixel The window borders in metacity are far too thin to be used for comfortable window resizing, and resize handles are not available in all applications (or even most). In fact, of all the windows I have open right now, not a single one of them has a resize handle. The result is that I get a lot of misses when I try to drag a window border, which usually results in my clicking on the wrong window altogether. The best fix for this usability bug is to create an invisible region around each non-maximized window about 4px thick that can be used for resizing (in addition to the visible border). Or perhaps there should be a border thickness option on the System Preferences Windows dialog (although the default thickness should still be increased considerably). Ideally all windows would also have a resize handle but I realize that these have to be application controlled (at least that seems to be the position of the metacity team). To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/160311/+subscriptions -- Mailing list: https://launchpad.net/~desktop
Re: [Desktop-packages] [Bug 160311] Re: Resizing windows by grabbing window borders is difficult
Hy! I'm a little bit afraid of a larger resize area.. If I click 10px far from a window, I probably want to raise the window below. 5-6px is ok, but more is risky, especially because that area is invisible. Eisenberger Tamás ta...@eisenberger.hu On 12/21/2011 03:56 PM, The Fiddler wrote: 2011/12/21 John Lea160...@bugs.launchpad.net @stapostol; thanks for your response, I've marked the bug as also affects unity2d. Re. the sizing of the dragable area, in WindowsXP the dragable area is 5px (but it may well be larger in Windows 7). So yes the size could be increased, but 5px also seems workable. Indeed, WinXP had 5px draggable areas - but WinXP is 10 years old now and it might not be the most suitable point of reference for modern design topics. The draggable area was increased in Vista (same as Win7) and I think I recall a msdn blog mentioning this was based on usability tests (but it's been half a decade since then and my google-fu is letting me down, so don't quote me on that). In any case, the drag area is invisible in Unity, so a potential size increase should be a relatively safe change. For those who need * significantly* larger grabable areas for accessibility reasons, another options is to use the love handles with a key combination, see http://linux-software-news-tutorials.blogspot.com/2011/06/activate- fantastic-grab-handles-in.html for details. These are indeed fantastic, maybe they merit more attention than currently given. (I love them on my laptop, but I cannot find a way to use them on my desktop). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/160311 Title: Resizing windows by grabbing window borders is difficult Status in Ayatana Design: Fix Released Status in One Hundred Paper Cuts: Fix Released Status in The Metacity Window Manager: In Progress Status in Release Notes for Ubuntu: Fix Released Status in Unity 2D: New Status in “human-gtk-theme” package in Ubuntu: Invalid Status in “light-themes” package in Ubuntu: Fix Released Status in “metacity” package in Ubuntu: Fix Released Status in “human-gtk-theme” source package in Maverick: Invalid Status in “light-themes” source package in Maverick: Triaged Status in “metacity” source package in Maverick: Triaged Bug description: * No more comments needed This should mostly be fixed for Natty and might get backported to earlier releases as well. * *Blueprint for Natty, Ubuntu 11.04: https://blueprints.edge.launchpad.net/ubuntu/+spec/packageselection- dx-n-resizing-windows Work items1 * Make sure the new resize grip fits in current applications; doesn't interfere with anything. We should make some noise about this during the Natty cycle so people keep their eyes open and file bugs. 2 * Invisible window resize area - around 3px invisible area to allow resize on all sides. * Working grip backported to gtk2 already available in ppa : https://launchpad.net/~bratsche/+archive/gtk * Workaround: Edit /usr/share/themes/Ambiance/metacity-1/metacity- theme-1.xml. Set the following values in frame_geometry_normal as desired: distance name=left_width value=3/ distance name=right_width value=3/ distance name=bottom_height value=3/ Binary package hint: metacity - The issue has been an issue for users (especially of large) screens for several releases- Trackpad users seem to be particularly impacted by this- The issue appears to have been significantly aggravated in Lucid by changing the border width from 3 pixels to 1 pixel The window borders in metacity are far too thin to be used for comfortable window resizing, and resize handles are not available in all applications (or even most). In fact, of all the windows I have open right now, not a single one of them has a resize handle. The result is that I get a lot of misses when I try to drag a window border, which usually results in my clicking on the wrong window altogether. The best fix for this usability bug is to create an invisible region around each non-maximized window about 4px thick that can be used for resizing (in addition to the visible border). Or perhaps there should be a border thickness option on the System Preferences Windows dialog (although the default thickness should still be increased considerably). Ideally all windows would also have a resize handle but I realize that these have to be application controlled (at least that seems to be the position of the metacity team). To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/160311/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe :
Re: [Desktop-packages] [Bug 160311] Re: Resizing windows by grabbing window borders is difficult
Hy! I can grab the 5px areas easily with trackball or touchpad on my T61 (14,1 1440x900), on the other hand, the 1px area is nearly impossible to catch with any display and pointing device. Eisenberger Tamás ta...@eisenberger.hu On 12/21/2011 10:53 PM, Steve Flynn wrote: On 21 December 2011 20:54, David N. Weltondavidnwel...@gmail.com wrote: Bingo! My laptop has a very high resolution screen, and this bug drives me batty. Don't the developers ever test on a system with a high resolution screen and a trackpad? Try using a trackball. Absolute nightmare. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/160311 Title: Resizing windows by grabbing window borders is difficult Status in Ayatana Design: Fix Released Status in One Hundred Paper Cuts: Fix Released Status in The Metacity Window Manager: In Progress Status in Release Notes for Ubuntu: Fix Released Status in Unity 2D: New Status in “human-gtk-theme” package in Ubuntu: Invalid Status in “light-themes” package in Ubuntu: Fix Released Status in “metacity” package in Ubuntu: Fix Released Status in “human-gtk-theme” source package in Maverick: Invalid Status in “light-themes” source package in Maverick: Triaged Status in “metacity” source package in Maverick: Triaged Bug description: * No more comments needed This should mostly be fixed for Natty and might get backported to earlier releases as well. * *Blueprint for Natty, Ubuntu 11.04: https://blueprints.edge.launchpad.net/ubuntu/+spec/packageselection- dx-n-resizing-windows Work items1 * Make sure the new resize grip fits in current applications; doesn't interfere with anything. We should make some noise about this during the Natty cycle so people keep their eyes open and file bugs. 2 * Invisible window resize area - around 3px invisible area to allow resize on all sides. * Working grip backported to gtk2 already available in ppa : https://launchpad.net/~bratsche/+archive/gtk * Workaround: Edit /usr/share/themes/Ambiance/metacity-1/metacity- theme-1.xml. Set the following values in frame_geometry_normal as desired: distance name=left_width value=3/ distance name=right_width value=3/ distance name=bottom_height value=3/ Binary package hint: metacity - The issue has been an issue for users (especially of large) screens for several releases- Trackpad users seem to be particularly impacted by this- The issue appears to have been significantly aggravated in Lucid by changing the border width from 3 pixels to 1 pixel The window borders in metacity are far too thin to be used for comfortable window resizing, and resize handles are not available in all applications (or even most). In fact, of all the windows I have open right now, not a single one of them has a resize handle. The result is that I get a lot of misses when I try to drag a window border, which usually results in my clicking on the wrong window altogether. The best fix for this usability bug is to create an invisible region around each non-maximized window about 4px thick that can be used for resizing (in addition to the visible border). Or perhaps there should be a border thickness option on the System Preferences Windows dialog (although the default thickness should still be increased considerably). Ideally all windows would also have a resize handle but I realize that these have to be application controlled (at least that seems to be the position of the metacity team). To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/160311/+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
Re: [Desktop-packages] [Bug 160311] Re: Resizing windows by grabbing window borders is difficult
Maybe the best would be a configurable size for the hidden grab area :) Currently it's difficult to change, how I seen the size is hardcoded into the theme right? Eisenberger Tamás ta...@eisenberger.hu On 12/22/2011 01:26 AM, Steve Flynn wrote: On 21 December 2011 22:27, u-fokata...@eisenberger.hu wrote: Hy! I can grab the 5px areas easily with trackball or touchpad on my T61 (14,1 1440x900), on the other hand, the 1px area is nearly impossible to catch with any display and pointing device. Alienware m15x, 1900 * 1200. If I hit the grab area first time using the touchpad it's a fluke. If I hit it with the trackball, it's only with a degree of concentration. Same laptop, same trackball and touchpad, Windows at the same rez - no problem. /shrug Been complaining about this for getting one for 2 years and it actually got resolved. Then Oneric came out and it was back to square one. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/160311 Title: Resizing windows by grabbing window borders is difficult Status in Ayatana Design: Fix Released Status in One Hundred Paper Cuts: Fix Released Status in The Metacity Window Manager: In Progress Status in Release Notes for Ubuntu: Fix Released Status in Unity 2D: New Status in “human-gtk-theme” package in Ubuntu: Invalid Status in “light-themes” package in Ubuntu: Fix Released Status in “metacity” package in Ubuntu: Fix Released Status in “human-gtk-theme” source package in Maverick: Invalid Status in “light-themes” source package in Maverick: Triaged Status in “metacity” source package in Maverick: Triaged Bug description: * No more comments needed This should mostly be fixed for Natty and might get backported to earlier releases as well. * *Blueprint for Natty, Ubuntu 11.04: https://blueprints.edge.launchpad.net/ubuntu/+spec/packageselection- dx-n-resizing-windows Work items1 * Make sure the new resize grip fits in current applications; doesn't interfere with anything. We should make some noise about this during the Natty cycle so people keep their eyes open and file bugs. 2 * Invisible window resize area - around 3px invisible area to allow resize on all sides. * Working grip backported to gtk2 already available in ppa : https://launchpad.net/~bratsche/+archive/gtk * Workaround: Edit /usr/share/themes/Ambiance/metacity-1/metacity- theme-1.xml. Set the following values in frame_geometry_normal as desired: distance name=left_width value=3/ distance name=right_width value=3/ distance name=bottom_height value=3/ Binary package hint: metacity - The issue has been an issue for users (especially of large) screens for several releases- Trackpad users seem to be particularly impacted by this- The issue appears to have been significantly aggravated in Lucid by changing the border width from 3 pixels to 1 pixel The window borders in metacity are far too thin to be used for comfortable window resizing, and resize handles are not available in all applications (or even most). In fact, of all the windows I have open right now, not a single one of them has a resize handle. The result is that I get a lot of misses when I try to drag a window border, which usually results in my clicking on the wrong window altogether. The best fix for this usability bug is to create an invisible region around each non-maximized window about 4px thick that can be used for resizing (in addition to the visible border). Or perhaps there should be a border thickness option on the System Preferences Windows dialog (although the default thickness should still be increased considerably). Ideally all windows would also have a resize handle but I realize that these have to be application controlled (at least that seems to be the position of the metacity team). To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/160311/+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 879456] Re: Typeahead functionality for nautilus is broken
The patch worked for me too, without noticeable side effects after a half hour. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/879456 Title: Typeahead functionality for nautilus is broken Status in Nautilus: New Status in “nautilus” package in Ubuntu: Confirmed Bug description: This bug is similar to: #857710 File selection by typing is buggy sometimes Description: Ubuntu 11.10 Release: 11.10 nautilus: Installed: 1:3.2.1-0ubuntu1 Candidate: 1:3.2.1-0ubuntu1 However the person that was assigned to that bug told me to file a new one because supposedly it is a different bug. I installed the nautilus 1:3.2.1-0ubuntu1 package from ubuntu proposed and all packages related and I still experience the following behavior: Expected behavior: - Open nautilus in ANY folder. - Start typing name of folder/file. - Nautilus selects folders/file matching as you type (one file at a time matching what is in the search/typeahead box). - Type backspace - Deletes the last character typed in search/typeahead box Actual Behavior - Open nautilus in ANY folder. - Start typing the name of a folder/file. - Sometimes the search box opens and sometimes it does not. (BUG) - If it does open, after a letter or two the search box disappears. (BUG) - If you change folders sometimes the box reappears as you start typing other times it disappears. (BUG) - If the box re-appears typing in Back-space does not delete the text present in the box, instead it navigates backwards (Unexpected behavior) - If it disappears It does not re-appear until you close and re-open nautilus. (BUG) This happens in ALL views (Icon, List, Compact) with or without status bar enabled (Some suggested that the status bar fixes this, it does not). The newly released packages (nautilus* 3.2.1) DO NOT fix this bug. I am on Ubuntu 11.10 64Bit Using Gnome 3.2 and Gnome Shell. Upgraded to this ubuntu since 10.04 To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/879456/+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 804946] Re: gnome-settings-daemon crashed with SIGSEGV in g_variant_unref()
Hy there! Bug 865115 was appeared the same time as this bug, can it be related? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/804946 Title: gnome-settings-daemon crashed with SIGSEGV in g_variant_unref() Status in The G Library - GLib: New Status in “glib2.0” package in Ubuntu: Triaged Status in “glib2.0” source package in Oneiric: Triaged Bug description: crashed while logging in. ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: gnome-settings-daemon 3.1.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.0-2.3-generic 3.0.0-rc4 Uname: Linux 3.0-2-generic i686 Architecture: i386 Date: Sat Jul 2 19:25:09 2011 ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon ProcEnviron: LANG=es_ES.UTF-8 SHELL=/bin/false PATH=(custom, no user) SegvAnalysis: Segfault happened at: 0xe43c73 g_variant_unref+35: lock xadd %eax,0x14(%esi) PC (0x00e43c73) ok source %eax ok destination 0x14(%esi) (0x0014) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing NULL VMA Signal: 11 SourcePackage: gnome-settings-daemon StacktraceTop: g_variant_unref (value=0x0) at /build/buildd/glib2.0-2.29.8/./glib/gvariant-core.c:617 g_settings_get_boolean (settings=0x0, key=0x810e222 enable) at /build/buildd/glib2.0-2.29.8/./gio/gsettings.c:1955 ?? () from /usr/lib/gnome-settings-daemon-3.0/liba11y-keyboard.so g_cclosure_marshal_VOID__STRING (closure=0x9794b20, return_value=0x0, n_param_values=2, param_values=0x97e2540, invocation_hint=0xb5afc5c0, marshal_data=0x0) at /build/buildd/glib2.0-2.29.8/./gobject/gmarshal.c:498 g_closure_invoke (closure=0x9794b20, return_value=0x0, n_param_values=2, param_values=0x97e2540, invocation_hint=0xb5afc5c0) at /build/buildd/glib2.0-2.29.8/./gobject/gclosure.c:771 Title: gnome-settings-daemon crashed with SIGSEGV in g_variant_unref() UpgradeStatus: Upgraded to oneiric on 2011-06-15 (17 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/804946/+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 828756] Re: getting connection is untrusted warnings
Hy! The bug was solved by the gnome-keyring 3.1.91-0ubuntu4 upgrade about a week ago, but now it's back with 3.1.92-0ubuntu1 :( What's happening? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/828756 Title: getting connection is untrusted warnings Status in “empathy” package in Ubuntu: Fix Released Status in “gnome-keyring” package in Ubuntu: Fix Released Status in “empathy” source package in Oneiric: Fix Released Status in “gnome-keyring” source package in Oneiric: Fix Released Status in “telepathy-gabble” package in Debian: Incomplete Bug description: Since updating to Oneiric, empathy is giving me connection is untrusted warning dialogs. For some reason, it's not verifying the certificate properly. For security reasons, this needs to get fixed. See attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: empathy 3.1.5-1ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-8.11-generic 3.0.1 Uname: Linux 3.0.0-8-generic x86_64 Architecture: amd64 Date: Thu Aug 18 09:36:06 2011 InstallationMedia: Ubuntu 11.04 Natty Narwhal - Alpha amd64 (20110302) ProcEnviron: PATH=(custom, user) LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: empathy UpgradeStatus: Upgraded to oneiric on 2011-08-16 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/828756/+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 792636] Re: Power section no longer allows configuration of when the lid is closed action in Oneiric
Hy! I can understand the opinion of the gnome developers (even if I can't agree with them) but as they removed the gconf keys too, that's insane :( The best way maybe would be to provide a simple gui for simple users with an advenced button in the corner (only one more item, that will never be pushed by someone who hates options) what is usefull for the users who love options.. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/792636 Title: Power section no longer allows configuration of when the lid is closed action in Oneiric Status in “gnome-control-center” package in Ubuntu: Triaged Bug description: Binary package hint: gnome-control-center In Natty I was able to configure what happens when the laptop lid was closed. Now that option doesn't exist in the power settings. I tried to set the following gconf options to nothing, but they had no immediate effect: /apps/gnome-power-manager/buttons/lid_battery /apps/gnome-power-manager/buttons/lid_ac It would be helpful to know a temporary workaround as I close my laptop all the time but I never suspend/hibernate it. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-control-center 1:3.0.2-1ubuntu4 ProcVersionSignature: Ubuntu 2.6.39-3.10-generic 2.6.39 Uname: Linux 2.6.39-3-generic x86_64 Architecture: amd64 Date: Fri Jun 3 20:06:37 2011 EcryptfsInUse: Yes InstallationMedia: Ubuntu 11.04 Natty Narwhal - Beta amd64 (20110330) ProcEnviron: LANGUAGE=en_US:en LC_COLLATE=C PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/zsh SourcePackage: gnome-control-center UpgradeStatus: Upgraded to oneiric on 2011-06-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/792636/+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
