[Ubuntu-x-swat] [Bug 1674059] [NEW] Notebook internal screen fades on switching occasions like standby and fullscreen
Public bug reported: Since about one or two weeks, my Thinkpad T420s using Ubuntu 16.04 quite frequently shows a strange error: On some display changes, like after standby, but even when switching VLC to fullscreen (no mode change!!!) the internal screen fades slowly to a bright dirty grid pattern. It looks like the LCD screen is unpowered, while the backlight is still on. Beside the screen, the machine works as intended. Even the backlight brightness can be changed by hotkeys. Some kind of refresh, like switching virtual terminals, usually restores the display immediately. I will try to downgrade the driver about a month and see if this remedies the error. ** Affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1674059 Title: Notebook internal screen fades on switching occasions like standby and fullscreen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1674059/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1640781] [NEW] Constant surplus display device detection and switching
Public bug reported: Using a Thinpad T420s, after upgrading to Ubuntu 16.04, I sometimes encounter a heavy problem: The internal screen is frequently blanking and comes up with other resolutions. This mostly triggers after resuming from standby. Using xrandr, I figured out that there are too many display devices listed, and one of them, named VGA2, is intermittently thought to be connected, so it is automatically acitvated and the screen layout adapts, also changing the internal screen resolution (a clone view setup I guess). In reality, there are no devices, cables or adapters attached to any display output (there is only one VGA and one DisplayPort output). If bug kicks in, the computer is almost unusable, permanently switching the screen layout every few seconds. The bug cannot be undone by restarting Xorg and also holds after rebooting the machine. It can be fixed by power cycling the machine. ** Affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New ** Attachment added: "xrandr output" https://bugs.launchpad.net/bugs/1640781/+attachment/4775299/+files/xrandr.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1640781 Title: Constant surplus display device detection and switching To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1640781/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1640781] Re: Constant surplus display device detection and switching
Xorg log is also showing the repeated switching. ** Attachment added: "Xorg.0.log" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1640781/+attachment/4775301/+files/Xorg.0.log -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1640781 Title: Constant surplus display device detection and switching To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1640781/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1640781] Re: Constant surplus display device detection and switching
Here is another different xrandr output, without any changes in the real world (eg. no display devices or cables attached at all). This output was just taken seconds after the first. ** Attachment added: "Another xrandr output" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1640781/+attachment/4775300/+files/xrandr_2.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1640781 Title: Constant surplus display device detection and switching To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1640781/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1615420] [NEW] Regression: Low screen brightness after standby
Public bug reported: After updating to Ubuntu 16.04 from 14.04, on my Lenovo T420s, the screen is very dim after resuming from standby. Changing the brightness by settings or fn keys restores the correct state. This is very annoying because it is a repeating regression that happens again and again over the last years. Almost every distribution upgrade breaks the brightness after standby and took some month or even years to have it working correct again. ** Affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1615420 Title: Regression: Low screen brightness after standby To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1615420/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1447078] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1447078/+attachment/4583872/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1447078 Title: Xorg should mark damaged window areas after some timeout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1447078/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1447078] xdpyinfo.txt
apport information ** Attachment added: "xdpyinfo.txt" https://bugs.launchpad.net/bugs/1447078/+attachment/4583884/+files/xdpyinfo.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1447078 Title: Xorg should mark damaged window areas after some timeout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1447078/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1447078] xserver.errors.txt
apport information ** Attachment added: "xserver.errors.txt" https://bugs.launchpad.net/bugs/1447078/+attachment/4583886/+files/xserver.errors.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1447078 Title: Xorg should mark damaged window areas after some timeout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1447078/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1447078] drirc.txt
apport information ** Attachment added: "drirc.txt" https://bugs.launchpad.net/bugs/1447078/+attachment/4583882/+files/drirc.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1447078 Title: Xorg should mark damaged window areas after some timeout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1447078/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1447078] XorgLogOld.txt
apport information ** Attachment added: "XorgLogOld.txt" https://bugs.launchpad.net/bugs/1447078/+attachment/4583880/+files/XorgLogOld.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1447078 Title: Xorg should mark damaged window areas after some timeout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1447078/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1447078] XorgLog.txt
apport information ** Attachment added: "XorgLog.txt" https://bugs.launchpad.net/bugs/1447078/+attachment/4583879/+files/XorgLog.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1447078 Title: Xorg should mark damaged window areas after some timeout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1447078/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1447078] xserver.devices.txt
apport information ** Attachment added: "xserver.devices.txt" https://bugs.launchpad.net/bugs/1447078/+attachment/4583885/+files/xserver.devices.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1447078 Title: Xorg should mark damaged window areas after some timeout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1447078/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1447078] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1447078/+attachment/4583873/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1447078 Title: Xorg should mark damaged window areas after some timeout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1447078/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1447078] make.log.txt
apport information ** Attachment added: "make.log.txt" https://bugs.launchpad.net/bugs/1447078/+attachment/4583883/+files/make.log.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1447078 Title: Xorg should mark damaged window areas after some timeout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1447078/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1447078] Xrandr.txt
apport information ** Attachment added: "Xrandr.txt" https://bugs.launchpad.net/bugs/1447078/+attachment/4583881/+files/Xrandr.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1447078 Title: Xorg should mark damaged window areas after some timeout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1447078/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1447078] UnitySupportTest.txt
apport information ** Attachment added: "UnitySupportTest.txt" https://bugs.launchpad.net/bugs/1447078/+attachment/4583878/+files/UnitySupportTest.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1447078 Title: Xorg should mark damaged window areas after some timeout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1447078/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1447078] UdevLog.txt
apport information ** Attachment added: "UdevLog.txt" https://bugs.launchpad.net/bugs/1447078/+attachment/4583877/+files/UdevLog.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1447078 Title: Xorg should mark damaged window areas after some timeout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1447078/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1447078] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1447078/+attachment/4583876/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1447078 Title: Xorg should mark damaged window areas after some timeout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1447078/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1447078] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1447078/+attachment/4583875/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1447078 Title: Xorg should mark damaged window areas after some timeout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1447078/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1447078] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1447078/+attachment/4583874/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1447078 Title: Xorg should mark damaged window areas after some timeout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1447078/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1447078] MonitorsUser.xml.txt
apport information ** Attachment added: "MonitorsUser.xml.txt" https://bugs.launchpad.net/bugs/1447078/+attachment/4583871/+files/MonitorsUser.xml.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1447078 Title: Xorg should mark damaged window areas after some timeout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1447078/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1447078] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1447078/+attachment/4583869/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1447078 Title: Xorg should mark damaged window areas after some timeout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1447078/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1447078] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1447078/+attachment/4583870/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1447078 Title: Xorg should mark damaged window areas after some timeout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1447078/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1447078] DpkgLog.txt
apport information ** Attachment added: "DpkgLog.txt" https://bugs.launchpad.net/bugs/1447078/+attachment/4583867/+files/DpkgLog.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1447078 Title: Xorg should mark damaged window areas after some timeout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1447078/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1447078] GconfCompiz.txt
apport information ** Attachment added: "GconfCompiz.txt" https://bugs.launchpad.net/bugs/1447078/+attachment/4583868/+files/GconfCompiz.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1447078 Title: Xorg should mark damaged window areas after some timeout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1447078/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1447078] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1447078/+attachment/4583866/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1447078 Title: Xorg should mark damaged window areas after some timeout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1447078/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1447078] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1447078/+attachment/4583865/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1447078 Title: Xorg should mark damaged window areas after some timeout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1447078/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1447078] BootLog.txt
apport information ** Attachment added: "BootLog.txt" https://bugs.launchpad.net/bugs/1447078/+attachment/4583864/+files/BootLog.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1447078 Title: Xorg should mark damaged window areas after some timeout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1447078/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1447078] BootDmesg.txt
apport information ** Attachment added: "BootDmesg.txt" https://bugs.launchpad.net/bugs/1447078/+attachment/4583863/+files/BootDmesg.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1447078 Title: Xorg should mark damaged window areas after some timeout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1447078/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1447078] Re: Xorg should mark damaged window areas after some timeout
I think there is no need for additional info as there is a systemic problem by the way it usually works. However, I will add info if it helps the burocracy... ** Tags added: apport-collected trusty ubuntu ** Description changed: When applications do not respond to Xorg redraw requests (eg. a window is raised on a non compositing desktop and the applications have some computation going on, for example LibreOffice Calc) for some area of a window for some milliseconds, Xorg should fill the area with some color. Otherwise applications not serving redraw requests may expose windows showing another applications content, leading to erratic manipulation by the user into the unresponsive application, which later responds erraticallty. - For example, having LibreOffice Calc do some calculations that may take - a while, bring a browser to front, bring LibreOffice to front, still - seeing the browser with at some time LibreOffices' progress bar popping - in at the bottom. However, most of the screen may be covered by a web - page, you try to enter password at, and dang, if LibreOffice is - finished, the password actually appears visible inside the spreadsheet. + For example, having LibreOffice Calc do some calculations that may take a while, bring a browser to front, bring LibreOffice to front, still seeing the browser with at some time LibreOffices' progress bar popping in at the bottom. However, most of the screen may be covered by a web page, you try to enter password at, and dang, if LibreOffice is finished, the password actually appears visible inside the spreadsheet. + --- + .tmp.unity.support.test.0: + + ApportVersion: 2.14.1-0ubuntu3.19 + Architecture: amd64 + CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,workarounds,scale,expo,ezoom,switcher] + CompositorRunning: None + CurrentDesktop: Unity + DistUpgraded: Fresh install + DistroCodename: trusty + DistroRelease: Ubuntu 14.04 + DistroVariant: ubuntu + DkmsStatus: + bbswitch, 0.7, 3.19.0-49-generic, x86_64: installed + bbswitch, 0.7, 3.19.0-51-generic, x86_64: installed + v4l2loopback, 0.8.0: added + virtualbox, 4.3.36, 3.19.0-49-generic, x86_64: installed + virtualbox, 4.3.36, 3.19.0-51-generic, x86_64: installed + EcryptfsInUse: Yes + ExtraDebuggingInterest: Yes + GraphicsCard: + Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) +Subsystem: Lenovo Device [17aa:21d3] + NVIDIA Corporation GF119M [NVS 4200M] [10de:1056] (rev ff) (prog-if ff) + InstallationDate: Installed on 2015-11-22 (98 days ago) + InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) + MachineType: LENOVO 4173W1J + Package: xorg 1:7.7+1ubuntu8.1 + PackageArchitecture: amd64 + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-49-generic root=UUID=44f71bef-2898-4ffa-bc57-631db5e42ca7 ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 3.19.0-49.55~14.04.1-generic 3.19.8-ckt12 + Tags: trusty ubuntu + Uname: Linux 3.19.0-49-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm bumblebee cdrom dialout dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 09/14/2011 + dmi.bios.vendor: LENOVO + dmi.bios.version: 8CET49WW (1.29 ) + dmi.board.asset.tag: Not Available + dmi.board.name: 4173W1J + 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:bvr8CET49WW(1.29):bd09/14/2011:svnLENOVO:pn4173W1J:pvrThinkPadT420s:rvnLENOVO:rn4173W1J:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: + dmi.product.name: 4173W1J + dmi.product.version: ThinkPad T420s + dmi.sys.vendor: LENOVO + version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 + version.ia32-libs: ia32-libs N/A + version.libdrm2: libdrm2 2.4.64-1~ubuntu14.04.1 + version.libgl1-mesa-dri: libgl1-mesa-dri N/A + version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A + version.libgl1-mesa-glx: libgl1-mesa-glx N/A + version.xserver-xorg-core: xserver-xorg-core N/A + version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A + version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A + version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A + version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A + xserver.bootTime: Thu Feb 18 17:47:05 2016 + xserver.configfile: default + xserver.logfile: /var/log/Xorg.0.log + xserver.outputs: + + xserver.version: 2:1.17.1-0ubuntu3.1~trusty1 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1447078 Title: Xorg should mark damaged window areas after some timeout To manage
[Ubuntu-x-swat] [Bug 362359] Re: Focus gets stuck to a window - impossible to select other windows
Also happens to me on 12.04 in Gnome Classic Mode from time to time. Happens to plugged devices or integrated touchpads too. Using the context menu click and left clicks in some wild fashion may release the stuck focus, but no clear picture what event exactly releases the stuck focus. Triggering of the problem maybe involves wheel scrolling events or conetxt menu usage in some unusual combination. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/362359 Title: Focus gets stuck to a window - impossible to select other windows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/362359/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 858265] Re: No support for power management
I think it is totally ok for a driver in development to not support power management until it is done. But it IS very bad idea to ship this not-ready driver to the users for a publisher like Ubuntu that targets a general audience. It just gives a bad user experience to thousands. And Ubuntu is not ashamed of shipping proprietary binary drivers, so for the nVidia drivers this would be very useful to continue shipping the binary driver until Nouveau does power management well. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/858265 Title: No support for power management To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/858265/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 858265] Re: No support for power management
Well I think it is clearly an important issue, even if only some machines overheat to failure, almost all mobile machines with nvidia suffer from bad battery mileage and unneeded fan noise. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/858265 Title: No support for power management To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/858265/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 956071] Re: Xorg crashed with SIGSEGV in XIGetDeviceProperty()
I can confirm that 1.6.2-1ubuntu1~precise2 doesn't completely fix the bug on Lenovo T420s. While I have not seen any random crashes for some time, the touchpad can still be killed by the test described in #81. After some cycles of disabling it by hotkey with fingers on and reenabling with fingers off the pad is not working anymore. However, this procedure doesn't crash X so far, as it reliably does with ..~precise1 before. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/956071 Title: Xorg crashed with SIGSEGV in XIGetDeviceProperty() To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/956071/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 956071] Re: Xorg crashed with SIGSEGV in XIGetDeviceProperty()
If I understand the fix right, there may be a method to reliable reproduce this error with the buggy version, and thus check the fix after updating: - Put two or more fingers to the touchpad - Send the computer to standby, or disable the pad if hotkey exists with the fingers still on the pad - Remove the fingers - Resume the computer or enable the touchpad again - Place some fingers on the pad again On the first or after just a few of these cycles the computer should crash. Can anyone still affected by this bug check this out? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/956071 Title: Xorg crashed with SIGSEGV in XIGetDeviceProperty() To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/956071/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 956071] Re: Xorg crashed with SIGSEGV in XIGetDeviceProperty()
Me too had no crashes since downgrading to 1.5.99.902-ubuntu5 . For all those who also downgraded, please check again if you downgraded to that version or earlier, and that the packaged is 'locked' after the old version is forced to prevent it being upgraded again. Also there where some reports that unattended updates don't care for the lock sometimes, so it would be useful to check the version actually used on every crash. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/956071 Title: Xorg crashed with SIGSEGV in XIGetDeviceProperty() To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/956071/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 956071]
I've raised the importance as this seems to be the equivalent of a large amount of bug reports on Ubuntu via launchpad. It affects PCs of several vendors, maybe restricted to newer Intel CPU/GPUs. Main launchpad report here: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/956071 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/956071 Title: Xorg crashed with SIGSEGV in XIGetDeviceProperty() To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/956071/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1030535] Re: [Sandybridge] Xorg crashes in XIGetDeviceProperty after standby
This gives a new clue, changing my opinion that this bug is related to the intel drivers. First, there where many clues (crash happens while enumerating modelines, reported by intel users). However, if some of you agree my conclusions, we may close this bug for this package: 1) The fix linked by the comment above gives strong clue that this bug is related to the synaptics driver 2) The corrupted structure, a list node with a bad next pointer, is accessed via a list iteration as it seems, so the damage done by the synaptics driver may result in a crash anytime this list is iterated. It's maybe the intel driver that triggers this trap, but it is not it's fault then. 3) The crash with the same circumstances (some minutes after resume) also occurs directly after enabling the synaptics touchpad for some people, like in this report: http://bugs.debian.org/cgi- bin/bugreport.cgi?bug=681796 SoI add the synaptic driver package here. ** Bug watch added: Debian Bug tracker #681796 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681796 ** Summary changed: - [Sandybridge] Xorg crashes in XIGetDeviceProperty after standby + Xorg crashes in XIGetDeviceProperty after standby -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1030535 Title: Xorg crashes in XIGetDeviceProperty after standby To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1030535/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1030535] Re: Xorg crashes in XIGetDeviceProperty after standby
Assigned to the intel driver by weak guess, now there are clues for the bug originating in the synaptics driver. ** Package changed: xserver-xorg-video-intel (Ubuntu) = xserver-xorg- input-synaptics (Ubuntu) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1030535 Title: Xorg crashes in XIGetDeviceProperty after standby To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1030535/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1030535] Re: [Sandybridge] Xorg crashes in XIGetDeviceProperty after standby
Yes, the bug is usually experienced by an unexpected appearence of the login screen. However, the bug https://bugs.launchpad.net/ubuntu/+source /xorg-server/+bug/956071 is a bit unprecise because it's hijacked, it first was a result of running minecraft, but later on others 'reproduce' the bug in conicidence of standby mode, so I think there are actually two reasons. However, that bug is now related to standby mode, so there there are people working on it. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1030535 Title: [Sandybridge] Xorg crashes in XIGetDeviceProperty after standby To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1030535/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 956071] Re: Xorg crashed with SIGSEGV in XIGetDeviceProperty()
Also affects Lenovo T420s. After resuming from a longer standby period by opening the lid, this crash occurs after about a minute. I don't experienced this some weeks ago, so it may be caused by a recent update or configuration change. Maybe related to the Intel drivers. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/956071 Title: Xorg crashed with SIGSEGV in XIGetDeviceProperty() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/956071/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1030535] [NEW] [Sandybridge] Xorg crashes in XIGetDeviceProperty after standby
Public bug reported: When resuming from a longer standby, Xorg crashes after about one minute at XIGetDeviceProperty(). Full details of this bug can be seen at the report for the Xorg package: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/956071 . This was first filed for Xorg as https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/956071 , but there is a strong feeling that it is caused by the intel driver, as it seems to affect the Intel Sandybrigde platform in almost all reported cases. So I suggest to take over the importance and detail information from the Xorg bug report. ** Affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1030535 Title: [Sandybridge] Xorg crashes in XIGetDeviceProperty after standby To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1030535/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 956071] Re: Xorg crashed with SIGSEGV in XIGetDeviceProperty()
As it seems to affect the intel integrated GPUs at most reported cases, I have filed this bug against the xserver-xorg-video-intel package: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- intel/+bug/1030535 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/956071 Title: Xorg crashed with SIGSEGV in XIGetDeviceProperty() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/956071/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 626321]
That has nothing to do with gaming, even if games most often expose this behavior. If any application is dealing with unique ressources like the screen configuration, it should not be trusted in its behavior, like it is not trusted in its memory recycling. If a program quits, the kernel ensures it's memory is freed. So should X care about screen settings. The only exception would be explicit screen setting tools that still must be able to change the resolution permanently. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/626321 Title: X.org server should keep track of and restore its initial (desktop) resolution and refresh rate To manage notifications about this bug go to: https://bugs.launchpad.net/wine/+bug/626321/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 626321] Re: X.org server should keep track of and restore its initial (desktop) resolution and refresh rate
Why is this wishlist only? This is clearly a bug. It is obvious that -with exception for the desktop setting programs-, the screen resolution is a temporary ressource like screen space and memory. If I kill an application, I expect that all temporary ressources are freed reliable. Failing of doing so gives horrible usability problems. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/626321 Title: X.org server should keep track of and restore its initial (desktop) resolution and refresh rate To manage notifications about this bug go to: https://bugs.launchpad.net/wine/+bug/626321/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 858265] [NEW] Nouveau burns too much GPU power for release
Public bug reported: With Ubuntu 11.10 beta, the Lenovo T61 with Nvidia gpu chipset NV86 runs hot and has bad battery live. As 'top' shows no evidence for unusual cpu load, I tink this is due to exceptional gpu load in idle or bad gpu power management. On ubuntu versions using the nvidia binary driver the machine stays cold and fan off almost any time on idle. I know nouveau is not really finished but until it is it should not be the default driver as that would give a very bad user experience. So I'd liked to file this bug against the oneiric distribution but ended up here. ** Affects: xserver-xorg-video-nouveau (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/858265 Title: Nouveau burns too much GPU power for release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/858265/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 576621] Re: desktop resolution not restored
As this still happens in several occasions and needs a general solution independent of a single configuration or single buggy subsystems/applications, I put this to confirmed state. If not appropriate, please give a hint how such general request should be handled better. thanks Paul ** Changed in: xorg-server (Ubuntu) Status: Incomplete = Confirmed -- desktop resolution not restored https://bugs.launchpad.net/bugs/576621 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 576621] Re: desktop resolution not restored
I think no more information is needed as I filed that as a general bug with several occurences in quite different situations. Its more a we need a general solution proposal, right? -- desktop resolution not restored https://bugs.launchpad.net/bugs/576621 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-x-swat] [Bug 576621] Re: desktop resolution not restored
Hi, Bryce Harrington wrote: Hi dronus, Please run the command 'apport-collect BUGNUMBER', apport-collect says: Package xorg-server not installed and no hook available, ignoring No additional information collected. That doesn't work because the package is named xserver-xorg appearently... which is not listed on launchpad it seems... A bug too?? I like to move the bug to a package that actually exists in my system, but which one, maybe xserver-xorg-core ? thanks very much Paul -- desktop resolution not restored https://bugs.launchpad.net/bugs/576621 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 576621] [NEW] desktop resolution not restored
Public bug reported: After running some bad resolution changing fullscreen application, the user set desktop resolution is not restored on quite many occasions. This is frequent if the display changing application is terminated abnormally (crashed, killed). Several bugtrackers are full of desktop resolution wrong after running xy complaints. This cannot be blamed to bad programs any more. The resolution should be handled just like memory or file handles - if the screen posessing process gets terminated, the OS / xserver should take care of restoring the desktop. I've already filed this one at bugs.freedesktop.org, but it is declared solved there as of Thu Oct 9 22:22:53 2008 +0200. For me, it isn't. ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New -- desktop resolution not restored https://bugs.launchpad.net/bugs/576621 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 576621] Re: desktop resolution not restored
Bug 27920 at bugs.freedesktop.org -- desktop resolution not restored https://bugs.launchpad.net/bugs/576621 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
