[Bug 861838] Re: Invisible window when launching from workspace switcher
Sorry for not updating the status earlier - this bug has been fixed by some unity update and I don't experience it any more. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/861838 Title: Invisible window when launching from workspace switcher To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/861838/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 855054] Re: [sandybridge-m-gt2] GPU lockup render.IPEHR: 0x02000002
No, I hasn't happened since then (actually it happened just once). Either it has been fixed or it's some hard-to-reproduce race condition or something similar. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/855054 Title: [sandybridge-m-gt2] GPU lockup render.IPEHR: 0x0202 To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/855054/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 797808] Re: Window auto-maximise functionality should be disabled on monitors with a resolution above 1024 x 600
Even though my resolution is over 1024 x 600 and the issue would be fixed for me, I disagree this is good solution. The reason is that when a user decides to unmaximize a window, he probably has a good reason for it and wants the window to appear the same way next time he starts the application. If you prefer to have some windows maximized on smaller screens, the windows should only *default* to maximized state when the application is launched for the very first time. If the user likes it, he keeps it that way. If he doesn't and unmaximizes the window, his decision should be respected next time the application is started. The current state also feels buggy and can lead to bad initial experience - see my comment here: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/708809/comments/21 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/797808 Title: Window auto-maximise functionality should be disabled on monitors with a resolution above 1024 x 600 To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/797808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 857799] Re: Foreground window loses focus if a background window pops up a modal dialog
Oh, you're right, I've just tested it under 10.10 (I've attached another file with pygtk example) and the same thing happens there so it isn't a regression. Strange I've never noticed it there. Still the question is whether this is a bug or a feature - for completeness I ran the test under OpenSUSE 11.2 with KDE and there's no change of focus which is the behavior I prefer. ** Attachment added: The same test using pygtk https://bugs.launchpad.net/unity/+bug/857799/+attachment/2462181/+files/test.py -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/857799 Title: Foreground window loses focus if a background window pops up a modal dialog To manage notifications about this bug go to: https://bugs.launchpad.net/compiz-core/+bug/857799/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 855054] [NEW] [sandybridge-m-gt2] GPU lockup render.IPEHR: 0x02000002
Public bug reported: Happened while browsing the web with firefox. Suddently everything (like the menu bar, launcher and window decoration) except for firefox tabs and the window with web page disappeared. When the PC's power button was pressed, a dialog with shutdown options appeared and it was possible to restart the computer normally. ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: xserver-xorg-video-intel 2:2.15.901-1ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4 Uname: Linux 3.0.0-11-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 1.23-0ubuntu1 Architecture: amd64 Chipset: sandybridge-m-gt2 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz Date: Tue Sep 20 22:36:39 2011 DistUpgraded: Log time: 2011-08-26 20:23:04.337565 DistroCodename: oneiric DistroVariant: ubuntu DuplicateSignature: [sandybridge-m-gt2] GPU lockup render.IPEHR: 0x0202 Ubuntu 11.10 ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu GpuHangFrequency: Very infrequently GpuHangReproducibility: Seems to happen randomly GpuHangStarted: I don't know GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21ce] InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Alpha amd64 (20110803.1) InterpreterPath: /usr/bin/python2.7 MachineType: LENOVO 41786NG ProcCmdline: /usr/bin/python /usr/share/apport/apport-gpu-error-intel.py ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-11-generic root=UUID=9c19aa40-5ce3-4be6-8e4e-7703f5912065 ro quiet splash vt.handoff=7 RelatedPackageVersions: xserver-xorg 1:7.6+7ubuntu7 libdrm2 2.4.26-1ubuntu1 xserver-xorg-video-intel 2:2.15.901-1ubuntu2 SourcePackage: xserver-xorg-video-intel Title: [sandybridge-m-gt2] GPU lockup render.IPEHR: 0x0202 UpgradeStatus: Upgraded to oneiric on 2011-09-12 (8 days ago) UserGroups: dmi.bios.date: 07/29/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 83ET63WW (1.33 ) dmi.board.asset.tag: Not Available dmi.board.name: 41786NG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr83ET63WW(1.33):bd07/29/2011:svnLENOVO:pn41786NG:pvrThinkPadT420:rvnLENOVO:rn41786NG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 41786NG dmi.product.version: ThinkPad T420 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.5.94+bzr2803-0ubuntu5 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.26-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 7.11-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 7.11-0ubuntu3 version.xserver-xorg: xserver-xorg 1:7.6+7ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.0-1ubuntu13 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20110811.g93fc084-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.15.901-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110411+8378443-1 ** Affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash compiz-0.9 freeze oneiric ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/855054 Title: [sandybridge-m-gt2] GPU lockup render.IPEHR: 0x0202 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/855054/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 855054] Re: [sandybridge-m-gt2] GPU lockup render.IPEHR: 0x02000002
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/855054 Title: [sandybridge-m-gt2] GPU lockup render.IPEHR: 0x0202 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/855054/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 708809] Re: The Automaximize windows in Unity value is too low
I find the automaximize feature very annoying too. The problem is that Unity tries to do something smart which in many cases isn't correct. 1. First, the user is surprised that the window is maximized because when he closed it, it wasn't maximized. This feels to him like a bug. 2. Second, when he realizes this is a feature, he is surprised because the automaximize happens only sometimes. It's not obvious that the size of the window influences the automaximize feature. This is again perceived as a bug. 3. Third, there are cases when you don't want to have the window maximized for some reason (the application's window is used together with other windows and you want to see the other windows too) but it gets maximized every time you start the application. This is HIGHLY annoying. It feels like you don't have the control over the computer but the computer has control over you (my usual feeling from Windows). Moreover, I don't completely understand what this feature tries to achieve. Sure, on small monitors you want to start applications maximized but you have to do it only once - as windows remember their sizes, the application will always start maximized later on. I don't think the single press of the maximize button justifies the annoyance above. Conclusion: in my opinion, this feature shouldn't be on by default. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/708809 Title: The Automaximize windows in Unity value is too low To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/708809/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 550218] Re: xserver crashes when closing application using clutter
I'm experiencing the very same problem with my Lenovo R61 notebook and 64bit Lucid. (Unfortunatelly with apport-collect I keep getting No additional information collected message with anything being uploaded so I'll try to describe my configuration and how to reproduce the bug manually.). This is what Xorg says about my graphics card: (--) PCI:*(0:0:2:0) 8086:2a02:17aa:20b5 Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller rev 12, Mem @ 0xf810/1048576, 0xe000/268435456, I/O @ 0x1800/8 This is how to reproduce the bug: 1. Install all required development packages to be able to build clutter. 2. Download and build clutter 1.2.4. 3. Go to tests/interactive and run some of the tests, i.g. test-viewport. 4. Run and close the test repeatably - Xorg will crash eventually when closing the window. (It seems that the probability of crash is higher just after the system boot. But maybe it's my impression only.) Not sure if it's related, but I also get the following message in the console after executing the test: do_wait: drmWaitVBlank returned -1, IRQs don't seem to be working correctly. Try adjusting the vblank_mode configuration parameter. I have also tested this with desktop PC using Nvidia proprietary drivers and wasn't able to reproduce this behaviour. -- xserver crashes when closing application using clutter https://bugs.launchpad.net/bugs/550218 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
