[Ubuntu-x-swat] [Bug 1039648] Re: kvm/cirrus: X driver will not load when kernel module is loaded
This bug was fixed in the package xserver-xorg-video-cirrus - 1:1.5.1-0ubuntu2 --- xserver-xorg-video-cirrus (1:1.5.1-0ubuntu2) quantal; urgency=low * Add fix-fallback.diff from upstream git, if a kernel driver is found don't try to claim the pci device. (LP: #1039648) -- Timo Aaltonen tjaal...@ubuntu.com Wed, 22 Aug 2012 10:42:50 +0300 ** Changed in: xserver-xorg-video-cirrus (Ubuntu) Status: Triaged = Fix Released -- 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/1039648 Title: kvm/cirrus: X driver will not load when kernel module is loaded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1039648/+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 990436] Re: Xorg with fglrx on ATI HD3650 crashes with Illegal instruction
Same problem on nforce2 motherboard, AGP Radeon HD 4650. My config: - Graphics: Radeon HD 4650 AGP - CPU: AMD Athlon 2400+ (2.0 GHz, 32 bits) - Chipset: nForce 2 - RAM: 1 GB DDR-SDRAM - Version kernel-3.2.0-29 - Ubuntu version: XUbuntu 12.04 (32 bits) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/990436 Title: Xorg with fglrx on ATI HD3650 crashes with Illegal instruction To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/990436/+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 927168] Re: compiz crashed with SIGSEGV in drisw_update_tex_buffer() from ... from __glXBindTexImageEXT() from TfpTexture::enable() from enableFragmentOperationsAndDrawGeometry()
Seems with the introduction of LLVMpipe support in Ubuntu 12.10, this bug is now happening to a lot more people than it was in 12.04. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/927168 Title: compiz crashed with SIGSEGV in drisw_update_tex_buffer() from ... from __glXBindTexImageEXT() from TfpTexture::enable() from enableFragmentOperationsAndDrawGeometry() To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/927168/+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 1039684] Re: nvidia.icd file is not present in nvidia-current 64bits. Fail to load opencl (like darktable)
Same bug in archlinux : https://bugs.archlinux.org/task/31034?string=openclproject=1type%5B0%5D=sev%5B0%5D=pri%5B0%5D=due%5B0%5D=reported%5B0%5D=cat%5B0%5D=status%5B0%5D=openpercent%5B0%5D=opened=dev=closed=duedatefrom=duedateto=changedfrom=changedto=openedfrom=openedto=closedfrom=closedto= -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/1039684 Title: nvidia.icd file is not present in nvidia-current 64bits. Fail to load opencl (like darktable) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1039684/+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 95444] Re: No Screen Backlight Control; Notebooks (Vaio, Macbook, HP/Compaq, Samsung, Zepto et al.) with Nvidia Geforce8/Geforce9/Quadro series graphics
The SIGSEGV is being tracked in bug #1039916 Nvidia driver causing SIGSEGV in nvclock and smartdimmer. That bug affects the Fix released status of this bug since this work- around no longer functions. I've nominated this bug for Precise and Quantal, but any fix of the SIGSEGV issue will be done in bug #1039916. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-180 in Ubuntu. https://bugs.launchpad.net/bugs/95444 Title: No Screen Backlight Control; Notebooks (Vaio, Macbook, HP/Compaq, Samsung, Zepto et al.) with Nvidia Geforce8/Geforce9/Quadro series graphics To manage notifications about this bug go to: https://bugs.launchpad.net/hal/+bug/95444/+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 1039938] [NEW] [xorg-edgers] glitches in kde panel during scolling in e.g. firefox
Public bug reported: since one version before xserver-xorg-video-intel - 2:2.20.4+git20120821.4ee2e227-0ubuntu0sarvatt I obtain glitches in the kde panel having blur effect enabled during scrolling through a website in firefox. I am using Kubuntu Quantal with xorg-edgers ppa enabled. After a ppa- purge all went fine again. Hardware: Lenovo Thinkpad X220 with SandyBridge: qdbus org.kde.kwin /KWin supportInformation KWin Support Information: The following information should be used when requesting support on e.g. http://forum.kde.org. It provides information about the currently running instance, which options are used, what OpenGL driver and which effects are running. Please post the information provided underneath this introductory text to a paste bin service like http://paste.kde.org instead of pasting into support threads. == Options === focusPolicy: 0 nextFocusPrefersMouse: false clickRaise: true autoRaise: false autoRaiseInterval: 0 delayFocusInterval: 0 shadeHover: false shadeHoverInterval: 250 tiling: false tilingLayout: 0 tilingRaisePolicy: 0 separateScreenFocus: false activeMouseScreen: false placement: 4 focusPolicyIsReasonable: true borderSnapZone: 10 windowSnapZone: 10 centerSnapZone: 0 snapOnlyWhenOverlapping: false showDesktopIsMinimizeAll: false rollOverDesktops: true focusStealingPreventionLevel: 1 legacyFullscreenSupport: false operationTitlebarDblClick: commandActiveTitlebar1: 0 commandActiveTitlebar2: 30 commandActiveTitlebar3: 2 commandInactiveTitlebar1: 4 commandInactiveTitlebar2: 30 commandInactiveTitlebar3: 2 commandWindow1: 7 commandWindow2: 8 commandWindow3: 8 commandWindowWheel: 31 commandAll1: 10 commandAll2: 3 commandAll3: 14 keyCmdAllModKey: 16777251 showGeometryTip: false electricBorders: false electricBorderDelay: 150 electricBorderCooldown: 350 electricBorderPushbackPixels: 1 electricBorderMaximize: true electricBorderTiling: true borderlessMaximizedWindows: false killPingTimeout: 5000 hideUtilityWindowsForInactive: true inactiveTabsSkipTaskbar: false autogroupSimilarWindows: false autogroupInForeground: true compositingMode: 1 useCompositing: true compositingInitialized: true hiddenPreviews: 1 unredirectFullscreen: false glSmoothScale: 1 glVSync: true xrenderSmoothScale: false maxFpsInterval: 17 refreshRate: 0 vBlankTime: 6144 glDirect: true glStrictBinding: true glStrictBindingFollowsDriver: true Compositing === Qt Graphics System: raster Compositing is active Compositing Type: OpenGL OpenGL vendor string: Intel Open Source Technology Center OpenGL renderer string: Mesa DRI Intel(R) Sandybridge Mobile x86/MMX/SSE2 OpenGL version string: 3.0 Mesa 8.1-devel Driver: Intel GPU class: SandyBridge OpenGL version: 3.0 Mesa version: 8.1 X server version: 1.12.99 Linux kernel version: 3.5 Direct rendering: yes Requires strict binding: yes GLSL shaders: yes Texture NPOT support: yes OpenGL 2 Shaders are used Loaded Effects: --- kwin4_effect_zoom kwin4_effect_login kwin4_effect_slidingpopups kwin4_effect_wobblywindows kwin4_effect_coverswitch kwin4_effect_translucency kwin4_effect_screenshot kwin4_effect_cube kwin4_effect_boxswitch kwin4_effect_desktopgrid kwin4_effect_dialogparent kwin4_effect_taskbarthumbnail kwin4_effect_presentwindows kwin4_effect_blur kwin4_effect_logout kwin4_effect_dashboard kwin4_effect_outline kwin4_effect_startupfeedback Currently Active Effects: - kwin4_effect_translucency kwin4_effect_blur ** 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/1039938 Title: [xorg-edgers] glitches in kde panel during scolling in e.g. firefox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1039938/+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 1032573] Re: Xorg crashing 5 minutes after resume with segmentation fault
Has anyone any hints on this? It is really obnoxious. I *think* it happens when using nautilus, but I cannot be sure. Some hints on how to debug? -- 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/1032573 Title: Xorg crashing 5 minutes after resume with segmentation fault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1032573/+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 1039970] [NEW] failed to install quantal alternate iso : xserver-xorg-video-all : Depends: xserver-xorg-video-modesetting but it is not installable
You have been subscribed to a public bug: Build : quantal alternate amd64 | i386 20120822 Link to the test: https://jenkins.qa.ubuntu.com/view/Quantal/view/ISO%20Testing%20Dashboard/job/quantal-alternate-amd64_default/ https://jenkins.qa.ubuntu.com/view/Quantal/view/ISO%20Testing%20Dashboard/job/quantal-alternate-i386_default/116/ Log: Aug 22 07:53:16 in-target: Some packages could not be installed. This may mean that you have Aug 22 07:53:16 in-target: requested an impossible situation or if you are using the unstable Aug 22 07:53:16 in-target: distribution that some required packages have not yet been created Aug 22 07:53:16 in-target: or been moved out of Incoming. Aug 22 07:53:16 in-target: The following information may help to resolve the situation: Aug 22 07:53:16 in-target: Aug 22 07:53:16 in-target: The following packages have unmet dependencies: Aug 22 07:53:16 in-target: xserver-xorg-video-all : Depends: xserver-xorg-video-modesetting but it is not installable Aug 22 07:53:16 in-target: E Aug 22 07:53:16 in-target: : Aug 22 07:53:16 in-target: Unable to correct problems, you have held broken packages. Aug 22 07:53:16 in-target: Aug 22 07:53:16 in-target: debconf (developer): -- PROGRESS SET 800 Aug 22 07:53:16 debconf: -- PROGRESS SET 800 Aug 22 07:53:16 in-target: debconf (developer): PROGRESS SET 800 Aug 22 07:53:16 debconf: -- 0 OK Aug 22 07:53:16 in-target: debconf (developer): 0 OK Aug 22 07:53:16 in-target: debconf (developer): -- 0 OK Aug 22 07:53:16 in-target: tasksel: aptitude failed (100) Aug 22 07:53:16 debconf: -- GET mirror/protocol Aug 22 07:53:16 debconf: -- 0 http Aug 22 07:53:16 debconf: -- GET mirror/http/proxy Aug 22 07:53:16 debconf: -- 0 http://192.168.123.1:3142 Aug 22 07:53:16 debconf: -- GET debconf/priority Aug 22 07:53:16 debconf: -- 0 critical Aug 22 07:53:16 debconf: -- GET debian-installer/locale Aug 22 07:53:16 debconf: -- 0 en_US.UTF-8 Aug 22 07:53:17 debconf: -- PROGRESS INFO pkgsel/progress/cleanup Aug 22 07:53:17 debconf: -- 0 OK Aug 22 07:53:17 debconf: -- PROGRESS STOP Aug 22 07:53:17 debconf: -- 0 OK Aug 22 07:53:17 main-menu[1736]: WARNING **: Configuring 'pkgsel' failed with error code 1 Aug 22 07:53:17 debconf: -- GET debconf/priority Aug 22 07:53:17 debconf: -- 0 critical Aug 22 07:53:17 main-menu[1736]: WARNING **: Menu item 'pkgsel' failed. Aug 22 07:53:17 debconf: -- SETTITLE debian-installer/pkgsel/title Aug 22 07:53:17 debconf: -- 0 OK Aug 22 07:53:17 debconf: -- CAPB ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: iso-testing qa-daily-testing quantal rls-q-incoming -- failed to install quantal alternate iso : xserver-xorg-video-all : Depends: xserver-xorg-video-modesetting but it is not installable https://bugs.launchpad.net/bugs/1039970 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg 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 1039970] Re: failed to install quantal alternate iso : xserver-xorg-video-all : Depends: xserver-xorg-video-modesetting but it is not installable
Not an installer bug. xserver-xorg-video-modesettings needs to be moved to main; I don't know whether it needs an MIR since I haven't been keeping track of that. ** Package changed: debian-installer (Ubuntu) = xorg (Ubuntu) -- 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/1039970 Title: failed to install quantal alternate iso : xserver-xorg-video-all : Depends: xserver-xorg-video-modesetting but it is not installable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1039970/+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 1039970] Re: failed to install quantal alternate iso : xserver-xorg-video-all : Depends: xserver-xorg-video-modesetting but it is not installable
Moved to main (see #ubuntu-release). ** Changed in: xorg (Ubuntu) Status: New = Fix Released -- 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/1039970 Title: failed to install quantal alternate iso : xserver-xorg-video-all : Depends: xserver-xorg-video-modesetting but it is not installable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1039970/+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 982471]
I can't figure out how to run openbve using the deb packages. I see a screen with empty lists for choosing a route and train add-on, and a grayed-out start button. -- 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/982471 Title: [i965] Xorg freeze after starting OpenBVE [IPEHR: 0x54f08006] To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/982471/+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 982010]
Can't reproduce on my G45 system. Can you try again with a current stack? (Also, does just opening mean no farther than the first menu screen?) -- 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/982010 Title: [gm45] GPU lockup render.IPEHR: 0x78080003 To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/982010/+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 982010] Re: [gm45] GPU lockup render.IPEHR: 0x78080003
** Changed in: xserver-xorg-video-intel Status: Confirmed = Incomplete -- 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/982010 Title: [gm45] GPU lockup render.IPEHR: 0x78080003 To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/982010/+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 521877]
The correct DPI is needed for legibility when the same user uses the same font size settings on multiple monitors. When the user sets the base font size to be legible in on 1 monitor and then goes to another which has a higher (true) DPI he will get poorly legible fonts. The correct DPI is needed for WYSIWYG, which is a holy grail of desk top publishing (DTP). X Windows applications increasingly aspire to be suitable for DTP. Look into the future. Monitors have not attained the highest useful DPI. This is only going to become a more pronounced deficiency as monitors increase in DPI. In fact, I suspect that monitor DPI has been somewhat held back by lack of proper support for automatically setting DPI. If current common monitors were completely adequate, we would not care about antialiasing or font hinting so much. 1200DPI or higher is found in printers and I am inclined to think it is not completely a marketing gimmick. 96DPI printers are practically nonexistant. I used to make fun of how MS Windows could not manage to set the DPI correctly automatically, unlike my Xorg, to friends and co-workers. No one attempted to rebut it. Instead of being compatible with old versions of MS Windows better is compatible with reality. Playing a hoax on programmers by default is a bad thing. -- 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/521877 Title: [gm45] wrong screen size detected on X200s To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/521877/+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 521877]
Please use the correct dpi by default. -- 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/521877 Title: [gm45] wrong screen size detected on X200s To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/521877/+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 521877]
Is this bug fixed in a newer release? A fix would be using the original behaviour or providing an option to revert to the original behaviour. I got a new monitor with 109 DPI yesterday and started to struggle with too small font sizes. I was not aware of this bug because my old monitor had approximately 96 dpi. In my opinion it is a wrong decision to not use the correct dpi of the device. This is the best choice one can make to get readable fonts. If one wants to consider the different viewing distance for projectors then the distance should be added as an additional option to the projector or to the X server such that the effective DPI can be calculated. Using a fixed value of 96 is plain wrong. It is also a problem that each tool starts to mess with the DPI settings: - X ignores the correct setting and uses 96 DPI - Firefox has its own DPI emulation - KDE has a setting for the DPI it should assume - For Scribus and Gimp one has to set the correct DPI in the settings. Relying on the server is no longer possible. - The latex beamer package assumes that slides are 15cm x 10cm to account for the larger viewing distance with projectors. Instead of having a simple central spot of DPI configuration the user has to cope with increased complexity. I also think that the website argument is not relevant. I've used a notebook for several years with 144 DPI. This was before the discussed changes and X used the correct DPI value. Some websites had problems with too small graphical elements compared to the font but I cannot remember that this made a website completely unusable. It scares me to imagine how the fonts would look like with 96 DPI on such a device. Finally I could always show Windows users that with X11 WYSIWYG is possible out-of-the-box while on their system the printout does not match the shown contents. With the introduction of this bug this is no longer possible. -- 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/521877 Title: [gm45] wrong screen size detected on X200s To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/521877/+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 521877]
(In reply to comment #55) Please use the correct dpi by default. If it doesn't, it's usually: 1-your distro's fault, or 2-your hardware's fault, or 3-your use of unequal DPI multiple displays, which is a complicated problem for X to deal with X automagic configuration will fall back to 96 if there's a problem with your hardware supplying the info automagic needs to work, while many distros force 96, in part because it makes web browsers behave like Windows on a not insignificant number of web sites, and in another part because DTEs are behind the development curve on adapting fonts, icons and initial window sizes to high DPI displays. Resolution independence is needed, but not available, either from most web sites, or most DTE components. OTOH, as long as you're sticking to one display, you can force correct DPI via xrandr, xorg.conf.d/, xorg.conf, xinitrc, proprietary nvidia driver and/or several other documented ways if bothered by inaccurate automagic or distro forcing. If your distro maker is forcing 96, complain to it. Just because xorg.conf is not used by default does not mean you cannot use it to enjoy accurate DPI. -- 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/521877 Title: [gm45] wrong screen size detected on X200s To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/521877/+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 521877]
(In reply to comment #56) (In reply to comment #55) Please use the correct dpi by default. If it doesn't, it's usually: 1-your distro's fault, or 2-your hardware's fault, or 3-your use of unequal DPI multiple displays, which is a complicated problem for X to deal with X automagic configuration will fall back to 96 if there's a problem with your hardware supplying the info automagic needs to work, [...] Isn't this bug precisely about X.org *always ignoring* the hardware DPI value from the EDID? (as per comment #5 and comment #6 and commit http://cgit.freedesktop.org/xorg/xserver/commit/?id=fff00df94d7ebd18a8e24537ec96073717375a3f ) -- 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/521877 Title: [gm45] wrong screen size detected on X200s To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/521877/+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 521877]
Created attachment 43316 Xorg.0.log from server 1.9.3 using 86x86 DPI on i845G (In reply to comment #57) Isn't this bug precisely about X.org *always ignoring* the hardware DPI value from the EDID? There may have been a time when that was the case, but this was filed by an Intel video user long before KMS was required by the Intel driver. Obviously from the attachment, using no xorg.conf, xrandr, xorg.conf.d/ or anything else to force DPI, always is not the much more recent case. Display used is 20 4:3 1400x1050 Viewsonic several years old. -- 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/521877 Title: [gm45] wrong screen size detected on X200s To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/521877/+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 521877]
(In reply to comment #58) There may have been a time when that was the case, but this was filed by an Intel video user long before KMS was required by the Intel driver. Obviously from the attachment, using no xorg.conf, xrandr, xorg.conf.d/ or anything else to force DPI, always is not the much more recent case. Display used is 20 4:3 1400x1050 Viewsonic several years old. From your own log: [35.477] (**) intel(0): Display dimensions: (410, 310) mm [35.477] (**) intel(0): DPI set to (86, 86) ... [35.914] (II) intel(0): Setting screen physical size to 370 x 277 Which means: $ qalc '1400 / (370 mm to inch)' 1400 / (370 * millimeter) = approx. 96.108108 / in $ qalc '1050 / (277 mm to inch)' 1050 / (277 * millimeter) = approx. 96.281588 / in Wanna' bet 'xdpyinfo | grep reso' on your machine shows resolution:96x96 dots per inch ? :) Regards, Andrei P.S. I get the same resizing to 96 dpi with latest Xorg + nouveau from Debian unstable, so this is not limited to intel -- 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/521877 Title: [gm45] wrong screen size detected on X200s To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/521877/+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 521877]
Created attachment 43320 86 DPI screenshot What do I win? :-) -- 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/521877 Title: [gm45] wrong screen size detected on X200s To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/521877/+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 521877]
(In reply to comment #60) Created an attachment (id=43320) [details] 86 DPI screenshot What do I win? :-) AFAIK this issue affects RandR 1.2 capable drivers only, and unless I'm mistaken MGA is not such a driver. -- 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/521877 Title: [gm45] wrong screen size detected on X200s To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/521877/+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 521877]
(In reply to comment #60) Created an attachment (id=43320) [details] 86 DPI screenshot What do I win? :-) You posted a log with intel, but your screenshot says mga... Regards, Andrei -- 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/521877 Title: [gm45] wrong screen size detected on X200s To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/521877/+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 521877]
The bug is marked general, not Intel. Various comments spoke of at least one other chip prior to my MGA comment 58. Before your comment 58 reached my eyes, I had to put that Intel host aside to work on the MGA host, so I used that to demonstrate what I wrote in comment 58, that always is incorrect. That said, I reread comment 6, which does indicate manual intervention via config file or xrandr is normally required to achieve accurate DPI, normal meaning ATI, Intel or NVidia, chips that have current version xrandr-supported drivers. -- 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/521877 Title: [gm45] wrong screen size detected on X200s To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/521877/+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 521877]
(In reply to comment #63) The bug is marked general, not Intel. Various comments spoke of at least one other chip prior to my MGA comment 58. Before your comment 58 reached my eyes, I had to put that Intel host aside to work on the MGA host, so I used that to demonstrate what I wrote in comment 58, that always is incorrect. Fair enough. That said, I reread comment 6, which does indicate manual intervention via config file or xrandr is normally required to achieve accurate DPI, normal meaning ATI, Intel or NVidia, chips that have current version xrandr-supported drivers. I don't want to push too much, but up until now all feedback to this bug has been (or at least this is how it reads to me): - autodetection of DPI is deprecated - 96 dpi ought to be enough for anybody :) Does this mean you agree that under normal circumstances the DPI should be the one detected from EDID and 96 is just a fall-back value in case auto-detection fails? Because I don't believe anyone here disagrees 96 should be uses as *fall-back*, we just don't want it *overriding* correctly auto-detected values. Thanks for reading, Andrei -- 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/521877 Title: [gm45] wrong screen size detected on X200s To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/521877/+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 521877]
Guess this is an invite to leave for Wayland or whatever. My current screen is 96 dpi (give or take a pixel) so I could care less but the moment I switch to a display with different resolution I will have to put up with this Xorg's insanity as well. If Xorg is going to be bug-compatible with Windows, and only Windows default settings, not Windows preinstalled by system integrators on all laptops with hi-res screens we can as well run ReactOS. The user experience will, again, be terrible, much worse than Windows. You should also add some (*((int (*)())0))(); to make it feel more like badly configured Windows. If you are really concerned that DPI alone is not doing the right thing then you should add a mechanism to adjust it per display type, not just flat force everything to some random bogus value. Eg. if you had a statistical study that says that people usually sit at a distance from LVDS which is about 2/3 the distance to TMDS then *leave the detected DPI alone* and add a *magnification factor* of 0.66 which modifies the reported DPI to be 0.66 of the actual DPI. Everyone can easily set to 1 if they want DTP-correct display and tune to a value that suits better their use of the system. This *also* handles displays that have non-square pixels correctly. You need a correct baseline to magnify from to get a magnification factor, not a brain damage factor. You can use the same magnification factor to set the resolution of something you think is a TV to flat 96dpi and still preserve the option to easily revert to the actual reported DPI. -- 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/521877 Title: [gm45] wrong screen size detected on X200s To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/521877/+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 521877]
Okay, I meant to post this a while ago and forgot, but the recent churn has reminded me to do so. I'll start with the tl;dr: I don't think this bug matters anymore. It's been over a year since this bug was opened, and during that time I've come to the conclusion that one should simply *always* specify DisplaySize in xorg.conf. This bug does not affect any setups that have a DisplaySize for each monitor: the only issue is DPI computation for monitors that have no DisplaySize. Lets look at the situation beforn and after the change: With the old behaviour, computing the resolution from the EDID works only if your monitor doesn't lie about its size (which happens far more often than it should). Otherwise, you have to set DisplaySize. With the new behaviour, things work fine as long as 96dpi is correct for your monitor. Otherwise, you have to set DisplaySize. So regardless of which way we pick, some people need to add DisplaySize directives to their xorg.conf. We could probably argue all day about which way is better, but I recommend a much simpler solution: grab a ruler and put DisplaySize directives in your xorg.conf. This bug was only a problem because the change broke working server configurations (this sort of issue seems to happen all the time with the X.org server). While breaking working setups is bad, I suspect that the vast majority of people who ran into problems because of this bug have long since updated their xorg.conf. At this point, changing it back will probably break just as many setups for marginal utility. -- 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/521877 Title: [gm45] wrong screen size detected on X200s To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/521877/+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 521877]
Let me disagree: I keep using my laptop either on a 17 monitor, or on a 21 monitor, or on the internal LVDS. In both 17 and 21 monitor cases, I do want 100% zoom to really mean 100% zoom, so I need correct DPI. Your reasoning leads to having to modify xorg.conf each time I switch, which means twice per day in my case... -- 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/521877 Title: [gm45] wrong screen size detected on X200s To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/521877/+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 521877]
--- Comment #67 from Samuel Thibault samuel.thiba...@ens-lyon.org
2011-02-13 14:27:50 PST ---
In both 17 and 21 monitor cases, I do want 100% zoom to really mean 100%
zoom, so I need correct DPI.
No, you need whatever app you're using to get the info about screen size
from somewhere it has a decent chance of being correct (randr), instead
of Display{Height,Width}MM.
--
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/521877
Title:
[gm45] wrong screen size detected on X200s
To manage notifications about this bug go to:
https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/521877/+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 521877]
(In reply to comment #67) Let me disagree: I keep using my laptop either on a 17 monitor, or on a 21 monitor, or on the internal LVDS. In both 17 and 21 monitor cases, I do want 100% zoom to really mean 100% zoom, so I need correct DPI. I don't understand what you mean by 100% zoom, but I understand the need for correct DPI. Your reasoning leads to having to modify xorg.conf each time I switch, which means twice per day in my case... We can assign monitor sections per-connector for randr-1.2 drivers, so we can easily arrange for the LVDS to always be right (since you presumably never change which monitor is attached to it). So in the case where monitors are swapped regularly, I guess this still is a problem. I still think that changing the default behaviour now is a bad idea. So let's get a server option to enable autodetection. I think someone posted a patch for that earlier... -- 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/521877 Title: [gm45] wrong screen size detected on X200s To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/521877/+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 521877]
Why should it have to care about screen size? 100% zoom is supposed to be app DPI matches screen DPI, it has nothing to do with the whole screen. -- 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/521877 Title: [gm45] wrong screen size detected on X200s To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/521877/+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 521877]
(In reply to comment #66) Okay, I meant to post this a while ago and forgot, but the recent churn has reminded me to do so. I'll start with the tl;dr: I don't think this bug matters anymore. It's been over a year since this bug was opened, and during that time I've come to the conclusion that one should simply *always* specify DisplaySize in xorg.conf. This bug does not affect any setups that have a DisplaySize for each monitor: the only issue is DPI computation for monitors that have no DisplaySize. Lets look at the situation beforn and after the change: With the old behaviour, computing the resolution from the EDID works only if your monitor doesn't lie about its size (which happens far more often than it should). Otherwise, you have to set DisplaySize. Yes, only when your screen is broken. With the new behaviour, things work fine as long as 96dpi is correct for your monitor. Otherwise, you have to set DisplaySize. Which is not the case about half of the time, and is becoming increasigly rare. So regardless of which way we pick, some people need to add DisplaySize directives to their xorg.conf. We could probably argue all day about which way is better, but I recommend a much simpler solution: grab a ruler and put DisplaySize directives in your xorg.conf. I don't want to measure my screen every time I install Xorg somewhere. This bug was only a problem because the change broke working server configurations (this sort of issue seems to happen all the time with the X.org server). While breaking working setups is bad, I suspect that the vast majority of people who ran into problems because of this bug have long since updated their xorg.conf. At this point, changing it back will probably break just as many setups for marginal utility. If the screen lies then you are free to take it and beat some of the manufacturer staff with it until they fix it. I suggest somebody with a 120+ dpi screen burns a bag of Xorg CDs an beats some Xorg developer with it until they fix the X server since they don't seem to respond to logical reasoning. -- 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/521877 Title: [gm45] wrong screen size detected on X200s To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/521877/+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 521877]
(In reply to comment #50) We need an xorg.conf flag -- for example, NVIDIA has UseEDIDDpi. Definitely. Is it that hard to implement? -- 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/521877 Title: [gm45] wrong screen size detected on X200s To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/521877/+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 521877]
(In reply to comment #72) (In reply to comment #50) We need an xorg.conf flag -- for example, NVIDIA has UseEDIDDpi. Definitely. Is it that hard to implement? No. A patch was attached to this report a year ago. -- 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/521877 Title: [gm45] wrong screen size detected on X200s To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/521877/+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 521877]
Created attachment 45751 120 DPI full 1600x1200 desktop screenshot This demonstrates the current state of elevated actual DTE DPI affairs, as of the release of openSUSE 11.4 about 5 weeks ago. Video chip is rv380. Driver is radeon. 120 DPI is achieved exclusively via DisplaySize in xorg.conf. Note that all apps are using the same font for the UI (urlbars, main menu), but that web browser viewports are of two schools: 1-Those forcing 96 DPI (WebKit in Google Chrome 7.0.517.44 and Epiphany 2.30.6, Opera 11.01) 2-Those using the DTE's DPI. (Gecko pre-rv2.0 in Firefox 3.6.16, KHTML in Konqueror 4.6) Note that Gecko rv2+ also forces to 96 in the usual cases, but provides a workaround (mozmm) that allows pages to size to match DTE DPI, which http://fm.no-ip.com/Auth/Font/font-vera.html in the screenshots does, and means all of Firefox 3.x, SeaMonkey 2.0.x, Firefox 4.x SeaMonkey 2.1x will render it the same if the DTE DPI is 96 or above. -- 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/521877 Title: [gm45] wrong screen size detected on X200s To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/521877/+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 521877]
Created attachment 45875 setting DisplaySize -- 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/521877 Title: [gm45] wrong screen size detected on X200s To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/521877/+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 521877]
(In reply to comment #74) Created an attachment (id=45751) [details] 120 DPI full 1600x1200 desktop screenshot This demonstrates the current state of elevated actual DTE DPI affairs, as of the release of openSUSE 11.4 about 5 weeks ago. Video chip is rv380. Driver is radeon. 120 DPI is achieved exclusively via DisplaySize in xorg.conf. Note that all apps are using the same font for the UI (urlbars, main menu), but that web browser viewports are of two schools: Thanks, I can confirm this with nouveau. However, as one can see in my attachment this has to be set for every monitor and then the correct Monitor section associated with the output. Kind of complicated if you often switch monitors... Wouldn't it make more sense to have a UseEDIDDpi option as already suggested above (and already used by nvidia)? Thanks, Andrei -- 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/521877 Title: [gm45] wrong screen size detected on X200s To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/521877/+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 521877]
Retitling this bug, since it affects current X servers as well, though possibly only randr-1.2-capable drivers as mentioned in comment 63 and the immediately preceding comments. This needs fixing. Each time I set up a new system, I end up with incredibly tiny fonts, and I end up having to manaully fix (and hardcode) the DPI to use the correctly autodetected value. The server already has a flag to override DPI with a constant value (namely -dpi). It doesn't need a flag to go back to autodetection, because it needs to do that by default. Nothing needs the X server to hardcode 96 DPI; browsers can already do that if they want to. (Chrome already does so, in a misguided attempt to force a constant ratio between px and pt across all websites. Firefox still seems to respect the system DPI by default, AFAICT.) Meanwhile, having the correct DPI makes fonts have reasonable sizes, and makes 100% zoom in various applications (such as evince) match the physical dimensions of a page. -- 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/521877 Title: [gm45] wrong screen size detected on X200s To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/521877/+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 521877]
(In reply to comment #77) (Chrome already does so, in a misguided attempt to force a constant ratio between px and pt across all websites. Chrome does because it's built on WebKit, where 96 as the only possibility is the traditional Macintosh way, which became also the Internet Explorer default behavior back in v7 or v8. Firefox still seems to respect the system DPI by default, AFAICT.) Since 2010/08/18 in https://bugzilla.mozilla.org/show_bug.cgi?id=537890 it only does so in the UI, not in web page content, where it now copies the IE, Chrome and Safari insanity. You can see the impact by using it to view both http://fm.no-ip.com/Auth/dpi-screen-windowg.html (old edition that worked as expected before that fix), and http://fm.no- ip.com/Auth/dpi-screen-window.html (modified version that can be accurate only in Geckos, Konq, and most old browsers). Its behavior can be impacted by two hidden preferences, layout.css.dpi (integer) layout.css.devPixelsPerPx (a string parsed as a float), the former of which defaults to -1, and the latter to 1.0. -- 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/521877 Title: [gm45] wrong screen size detected on X200s To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/521877/+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 521877]
Take it from a typographer http://www.alistapart.com/articles/realfontsontheweb We have a world of display devices that have standardized to report their exact resolution, the space it occupies, and thus the pixels per inch, a key to moving text typography forward. Who wants to break the news to him? Welcome to the past Mr. David Berlow. -- 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/521877 Title: [gm45] wrong screen size detected on X200s To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/521877/+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 521877]
(In reply to comment #27)
On Tue, Feb 16, 2010 at 10:58:07PM -0800, bugzilla-dae...@freedesktop.org
wrote:
--- Comment #26 from Andrey Rahmatullin w...@altlinux.org 2010-02-16
22:58:04 PST ---
(In reply to comment #20)
It was chosen in order to make display of web pages using Xorg more
consistent
with the way they get displayed on Windows, which by default assumes 96.
Is it an official position of X.org developers? Is it documented anywhere?
Sure, consider it an official position. I don't think it's
unreasonable. Especially if you assume that lower-DPI displays are
likely to be higher-resolution and thus physically huge, meaning that
people sit further away from them, and that displays with a meaningfully
higher DPI are almost always found in phones (as well as some laptops)
these days, meaning that people hold them a great deal closer to their
face.
I do agree that being able to configure the reported DPI (or just Option
DontForce96DPI) would be entirely useful, but I can't see us changing
anything in the near future, particularly if it breaks web page display.
Saying 'well, don't go to that website then' isn't helpful to anyone at
all, and makes us look like we value strict technical correctness ('but
don't you know what the true definition of a point is?!?') over an
actual working system. While we do value strict technical correctness,
we don't value it to the point of crippling everything else.
Why are you trying to fix browser bugs in X?
If you want to fake the DPI to 96, that should be a configuration in
XRandr, or something, that people can easily disable, but it would be a
workaround, not a fix.
Setting a fixed DPI is completely and totally the wrong thing to do.
Say, my laptop's display has a DPI of 142, and then I plug my display of
101 DPI, the fonts will look completely different, and I would be forced
to change the font settings (if there are any).
Do you seriously think that people changing their font settings each
time they plug/unplug external displays is ideal?
--
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/521877
Title:
[gm45] wrong screen size detected on X200s
To manage notifications about this bug go to:
https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/521877/+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 521877]
Please add an option (command-line or config file) to make the X server stop lying about the physical DPI of the display device. I understand all the arguments for pegging DPI at 96, but *I* still want my X server to report the actual DPI as read from the EDID. Maybe add an -autodpi command-line option? Or support -dpi auto with 96 being the default. -- 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/521877 Title: [gm45] wrong screen size detected on X200s To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/521877/+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 521877]
I'm seeing this bug too with nouveau driver. I've set DisplaySize to 474 296. At first it looks okay: [ 45437.510] (**) NOUVEAU(0): Display dimensions: (474, 296) mm [ 45437.510] (**) NOUVEAU(0): DPI set to (90, 90) and sets it to 96 dpi... [ 45437.530] (II) NOUVEAU(0): Setting screen physical size to 444 x 277 environment: Gentoo x86_64 Linux 3.0.4 Xorg Server 1.11.0 Nouveau DDX driver from GIT. -- 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/521877 Title: [gm45] wrong screen size detected on X200s To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/521877/+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 521877]
Created attachment 51062 X log from 1.11.0 -- 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/521877 Title: [gm45] wrong screen size detected on X200s To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/521877/+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 521877]
I'm seeing this bug too with the nouveau driver: [ 745.858] (**) NOUVEAU(0): Display dimensions: (330, 210) mm [ 745.858] (**) NOUVEAU(0): DPI set to (129, 127) ... [ 745.892] (II) NOUVEAU(0): Setting screen physical size to 444 x 277 I noticed this after switching from the proprietary nvidia driver, and this is a *huge* regression for me. X should *not* try to fix bugs in some programs by lying to all of them. Right now I'm using xrandr --fbmm from my .xinitrc, but this is just an ugly hack -- I'll probably get back to nvidia next time I have to plug my laptop to a projector. Environment: Arch Linux x86_64, Linux 3.0.4, xorg-server 1.11.0. -- 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/521877 Title: [gm45] wrong screen size detected on X200s To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/521877/+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 521877]
Was it really fixed??? I can't find any related fixed in git's master. -- 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/521877 Title: [gm45] wrong screen size detected on X200s To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/521877/+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 521877]
PLEASE stop reopening or discussing this in here. This is not a proper place for such discussion - this is not a forum or mailing list but bug reporting software and xorg developers concluded this is NOT A BUG. If you really want some changes in DPI area then please discuss it through proper channels like xorg@ mailing list (http://lists.freedesktop.org/mailman/listinfo/xorg) first. Thank you. -- 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/521877 Title: [gm45] wrong screen size detected on X200s To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/521877/+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 521877]
I've created feature request to add patch from comment 17: https://bugs.freedesktop.org/show_bug.cgi?id=41115 -- 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/521877 Title: [gm45] wrong screen size detected on X200s To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/521877/+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 521877]
However you look at it this is a bug. Xorg changed from working to bogus and broken behaviour. -- 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/521877 Title: [gm45] wrong screen size detected on X200s To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/521877/+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 521877]
(In reply to comment #20) It was chosen in order to make display of web pages using Xorg more consistent with the way they get displayed on Windows, which by default assumes 96. It's called bug compatibility, and there's a knob in a browser for that already. -- 1400x1050@122, 1600x1200+1920x1080@varied -- 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/521877 Title: [gm45] wrong screen size detected on X200s To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/521877/+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]
sorry, still can't reproduce this and I can't see any change between 902 and 1.6.2 that could have introduced this bug. Are you still on server 1.12.1.902 or have you updated the server as well? -- 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 have upgraded xorg server quite a while ago and it had not resolved the issue at that time. Just for the completness: /var/log/dpkg.log.1:2012-07-03 09:53:04 status installed xserver-xorg:amd64 1:7.6+13 /var/log/dpkg.log.1:2012-07-03 09:53:04 status installed xorg:amd64 1:7.6+13 /var/log/dpkg.log.1:2012-07-11 14:56:36 status installed xserver-xorg-core:amd64 2:1.12.1.902-1 /var/log/dpkg.log.1:2012-07-11 16:22:02 status installed xserver-xorg-video-vesa:amd64 1:2.3.1-1+b1 /var/log/dpkg.log.1:2012-07-11 16:22:02 status installed xserver-xorg-video-intel:amd64 2:2.19.0-4 /var/log/dpkg.log.1:2012-07-11 16:22:02 status installed xserver-xorg-video-fbdev:amd64 1:0.4.2-4+b3 /var/log/dpkg.log.1:2012-07-11 16:22:02 status installed xserver-xorg-video-dummy:amd64 1:0.3.5-2+b1 /var/log/dpkg.log.1:2012-07-11 16:22:02 status installed xserver-xorg-video-apm:amd64 1:1.2.3-3 /var/log/dpkg.log.1:2012-07-11 16:22:02 status installed xserver-xorg-input-void:amd64 1:1.4.0-1+b1 /var/log/dpkg.log.1:2012-07-11 16:22:02 status installed xserver-xorg-input-synaptics:amd64 1.6.2-1 /var/log/dpkg.log.1:2012-07-11 16:22:02 status installed xserver-xorg-input-evdev:amd64 1:2.7.0-1+b1 /var/log/dpkg.log.1:2012-07-11 16:22:02 status installed xserver-xorg:amd64 1:7.7+1 /var/log/dpkg.log.1:2012-07-11 16:22:02 status installed xorg:amd64 1:7.7+1 /var/log/dpkg.log.1:2012-07-11 16:22:02 status installed xserver-xorg-dev:amd64 2:1.12.1.902-1 /var/log/dpkg.log.1:2012-07-11 16:22:02 status installed xorg-dev:all 1:7.7+1 /var/log/dpkg.log.1:2012-07-16 11:43:34 status installed xserver-xorg-core-dbg:amd64 2:1.12.1.902-1 /var/log/dpkg.log.1:2012-07-16 11:43:34 status installed xserver-xorg-video-intel-dbg:amd64 2:2.19.0-4 /var/log/dpkg.log.1:2012-07-21 15:35:55 status installed xserver-xorg-core:amd64 2:1.12.3-1 /var/log/dpkg.log.1:2012-07-21 15:35:55 status installed xserver-xorg-core-dbg:amd64 2:1.12.3-1 /var/log/dpkg.log.1:2012-07-21 15:35:55 status installed xserver-xorg-dev:amd64 2:1.12.3-1 /var/log/dpkg.log.1:2012-07-25 09:18:55 status installed xserver-xorg-dev:amd64 2:1.12.3-1 /var/log/dpkg.log.1:2012-07-25 09:18:55 status installed xserver-xorg-core:amd64 2:1.12.3-1 /var/log/dpkg.log.1:2012-07-25 09:18:57 status installed xserver-xorg-core-dbg:amd64 2:1.12.3-1 /var/log/dpkg.log.1:2012-07-25 09:19:58 status installed xserver-xorg-dev:amd64 2:1.12.3-1 /var/log/dpkg.log.1:2012-07-25 09:19:58 status installed xserver-xorg-core:amd64 2:1.12.3-1 /var/log/dpkg.log.1:2012-07-25 09:20:00 status installed xserver-xorg-core-dbg:amd64 2:1.12.3-1 /var/log/dpkg.log.1:2012-07-26 20:15:33 status installed xserver-xorg-core-dbg:amd64 2:1.12.3-1 /var/log/dpkg.log:2012-08-08 23:12:08 status installed xserver-xorg-input-synaptics:amd64 1.6.2-1 /var/log/dpkg.log:2012-08-09 11:00:56 status installed xserver-xorg-input-synaptics-dev:all 1.5.99.902-1 /var/log/dpkg.log:2012-08-09 11:00:56 status installed xserver-xorg-input-synaptics:amd64 1.5.99.902-1 /var/log/dpkg.log:2012-08-15 12:45:23 status installed xserver-xorg-input-synaptics-dev:all 1.6.2+git44-ge28575b-1~yarik0 /var/log/dpkg.log:2012-08-15 12:45:23 status installed xserver-xorg-input-synaptics:amd64 1.6.2+git44-ge28575b-1~yarik0 as you see I have built and installed current master of the synaptics but had no chance yet to restart X to see if crash comes back... I will report back whenever that happens -- 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 521877]
PLEASE stop reopening or discussing this in here. This is not a proper place for such discussion - this is not a forum or mailing list but bug reporting software and xorg developers concluded this is NOT A BUG. If you really want some changes in DPI area then please discuss it through proper channels like xorg@ mailing list (http://lists.freedesktop.org/mailman/listinfo/xorg) first. Thank you. -- 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/521877 Title: [gm45] wrong screen size detected on X200s To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/521877/+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]
*** Bug 53686 has been marked as a duplicate of this bug. *** -- 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 36812]
This patch breaks the keyboard layout switcher from KDE3 and Trinity. It works correctly with the layout switcher in KDE4. Have other people tested this patch with other layout switchers? What are the results? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/36812 Title: Keyboard layout change on hotkeys press instead of release and do not work well with shortcuts To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/36812/+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 521877] Re: [gm45] wrong screen size detected on X200s
** Bug watch added: Mozilla Bugzilla #537890 https://bugzilla.mozilla.org/show_bug.cgi?id=537890 ** Bug watch added: freedesktop.org Bugzilla #41115 https://bugs.freedesktop.org/show_bug.cgi?id=41115 -- 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/521877 Title: [gm45] wrong screen size detected on X200s To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/521877/+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 36812]
Created attachment 63378 xorg-server-1.12.2-xkb-switch-on-release.patch Some code style modifications. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/36812 Title: Keyboard layout change on hotkeys press instead of release and do not work well with shortcuts To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/36812/+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 1021924] Re: Multiple Displays not working on Core i7 3770S + Intel DQ77MK motherboard
Launchpad has imported 2 comments from the remote bug at https://bugs.freedesktop.org/show_bug.cgi?id=51983. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2012-07-11T13:42:02+00:00 Maarten Lankhorst wrote: I have an Intel DQ77MK motherboard, which has 2 DVI connectors, and a Core i7 3770S IvyBridge CPU. Under Ubuntu 12.04, the multiple display support does not work, and I am stuck with a single display. The second screen only shows all pixels as 100% red. Enabling the second screen in Displays in System Settings does allow me to move windows and the mouse cursor to that screen, though I cannot actually see anything on it, as everything is red. For now I have had to force it to mirror displays, to avoid moving things to the second screen. Both screens at 1280x800 works, but both screens at 2048x1152 fails, regardless of whether using mirrored mode in Xorg. Reply at: https://bugs.launchpad.net/xorg- server/+bug/1021924/comments/11 On 2012-08-22T10:43:05+00:00 Daniel-ffwll wrote: Smells like fdi b/c link train fail again. Can you check whether you can switch places of the monitors by switching crtcs (with the xrandr --crtc option). But don't try to use both crtc 12, that will run into a hw limit that we currently don't check ... Also, please retest on latest 3.6-rc kernels just to check, and please attach dmesg with drm.debug=0xe and xrandr --verbose Reply at: https://bugs.launchpad.net/xorg- server/+bug/1021924/comments/12 ** Changed in: xorg-server Status: Unknown = Incomplete ** Changed in: xorg-server Importance: Unknown = Medium -- 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/1021924 Title: Multiple Displays not working on Core i7 3770S + Intel DQ77MK motherboard To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1021924/+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 973096] Re: Nvidia driver causes xorg crash
Well I see a bunch of people have this problem as well, I run KDE (with effects) and it logs me out from time to time. Mainly just running Opera and irssi. Suspect it must be some flash via Opera than which cause the logoff. Running Kubuntu 12.04, nVidia 295.40, and KDE 4.9 I had 240GTS card which I sent back to the store because I thought it was a hardware fail, that said, it still may be because of heavier hangups. Now I am using the backup card which is 8500GT, and here I never have hard hangups, but logs me out. I hope I don't get my 240GTS back now because of faulty drivers, that will be waste of cash. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/973096 Title: Nvidia driver causes xorg crash To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/973096/+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 1039938] Re: [xorg-edgers] glitches in kde panel during scolling in e.g. firefox
I also can see some random text rendering issues in firefox when marking text passages with the mouse or writing in formular fields. And here you can see the flickering: http://www.file- upload.net/download-4701050/panel-flickering.ogg.ogv.html -- 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/1039938 Title: [xorg-edgers] glitches in kde panel during scolling in e.g. firefox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1039938/+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 1019131] Re: vsync is disabled by default in nouveau
Fix is committed in upstream kernel and in nouveau ddx for all cards including kepler. However, due to the drastic changes in upstream kernel it wouldn't be possible to backport to 3.5, unless it's decided to use a backported version of 3.7 drm there. It's not a typo, the changes are too big for 3.6 merge window. ** Changed in: nouveau Status: New = Fix Released -- 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/1019131 Title: vsync is disabled by default in nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/1019131/+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 1040035] Re: Xorg crashed with SIGABRT
*** This bug is a duplicate of bug 1033533 *** https://bugs.launchpad.net/bugs/1033533 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1033533, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: CoreDump.gz https://bugs.launchpad.net/bugs/1040035/+attachment/3271663/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1040035/+attachment/3271665/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1040035/+attachment/3271673/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1040035/+attachment/3271675/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1040035/+attachment/3271676/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1040035/+attachment/3271677/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1040035/+attachment/3271678/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1033533 Xorg crashed with SIGABRT ** Visibility changed to: Public ** Tags removed: need-amd64-retrace -- 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/1040035 Title: Xorg crashed with SIGABRT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1040035/+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 1039125] Re: [drm] nouveau 0000:02:00.0: PFIFO_CACHE_ERROR - Ch 2/2 Mthd 0x0800 Data 0x00000000
I'm attaching the kern.log when running the 3.5.0-11 kernel. ** Attachment added: kern.log https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1039125/+attachment/3271727/+files/kern.log -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1039125 Title: [drm] nouveau :02:00.0: PFIFO_CACHE_ERROR - Ch 2/2 Mthd 0x0800 Data 0x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1039125/+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 1038831] Re: Xorg crashed with SIGABRT in raise()
*** This bug is a duplicate of bug 1030165 *** https://bugs.launchpad.net/bugs/1030165 It seems to fail to load nouveau correctly.. [ 9.772] (EE) [drm] failed to open device [16.622] (EE) [drm] failed to open device I would say you have had the nvidia module loaded previously and things broke as a result. Is there a nouveau blacklist in /etc/modprobe.d ? ** This bug has been marked a duplicate of bug 1030165 Xorg can't use nvidia card with nouveau but doesn't fallback to vesa -- 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/1038831 Title: Xorg crashed with SIGABRT in raise() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1038831/+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 1012149] Re: package libxrandr2 2:1.3.2-2 [modified: usr/share/doc/libxrandr2/changelog.Debian.gz] failed to install/upgrade: libxrandr2:amd64 2
There has been a new version of libxrandr 1.4.0 for some time now, is still still an issue or can the bug be closed? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libxrandr in Ubuntu. https://bugs.launchpad.net/bugs/1012149 Title: package libxrandr2 2:1.3.2-2 [modified: usr/share/doc/libxrandr2/changelog.Debian.gz] failed to install/upgrade: libxrandr2:amd64 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxrandr/+bug/1012149/+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 1030165] Re: Xorg can't use nvidia card with nouveau but doesn't fallback to vesa
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xserver-xorg-video-nouveau (Ubuntu) Status: New = Confirmed -- 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/1030165 Title: Xorg can't use nvidia card with nouveau but doesn't fallback to vesa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1030165/+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 416421]
Committed as http://cgit.freedesktop.org/xorg/xserver/commit/?id=863d528a9f76d0e8f122aebf19f8564a4c67a938 -- 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/416421 Title: [gm45] X crash on X200s with dual monitors (using DisplayPort) To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/416421/+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 1033783] Re: Wacom stylus and touch not recognised on Lenovo X220t
Can you start the Xorg server with -verbose 10, then plug in the device and paste the log? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xf86-input-wacom in Ubuntu. https://bugs.launchpad.net/bugs/1033783 Title: Wacom stylus and touch not recognised on Lenovo X220t To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/1033783/+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 881046]
I applied Mr. Bagwell's patch to Fedora 17 after receiving some guidance from Mr. Weir. I thank all who have posted for their contribution in resolving this long term regression. My specific steps were... 1. Obtain the source: yumdownloader --source xorg-x11-server- common.i686 2. Extract the RPM to a subdirectory structure (in my case, ~/source/xorg-x11-server-x.xx.x-y.fc17.src) 3. Extract the xorg-server-x.xx.x.tar.bz2 file (contained in the directory created in step 2) to source subdirectories of that directory (in my case ~/source/xorg-x11-server-x.xx.x-y.fc.src/xorg-server-x.x.xx) created in step 2. 4. Modify the rrcrtc.c source code in the randr subdirectory (~/source/xorg-x11-server-x.xx.x-y.fc.src/xorg-server-x.x.xx/randr) as Chris states. I had to apply the patch manually, however it's very straightforward. The following steps were issued from within the xorg-server-x.xx.x subdirectory created in step 3 above and presume you have all required development tools installed. 5. Command: ./configure --prefix=/usr. 6. Command: make 7. Command: sudo make install I performed these steps on version 1.12.2-2 as well as on 1.12.2-4 and after testing each patch, I reinstalled (yum reinstall xorg-x11-server-common.i386) standard code to verify repeatability. In each case, scanning/panning was enabled following application of the patch. I am running this on an Acer Aspire AOD257 which has (of course) an integrated trackpad. One issue I have noticed is that after application of the patch, the trackpad scrolling functions are disabled. That is to say, the trackpad continues to function as a mouse, but the finger drag along the right side of the trackpad no longer functions. Under touchpad-system settings (KDE desktop), the touchpad information indicates device not found. I cannot explain the relationship between this function and the patch, but will do more testing -- has anyone else on a netbook noticed this condition? -- 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/881046 Title: Panning in a virtual monitor is not possible after upgrade to Ubuntu 11.10 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/881046/+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 883319]
I applied Mr. Bagwell's patch to Fedora 17 after receiving some guidance from Mr. Weir. I thank all who have posted for their contribution in resolving this long term regression. My specific steps were... 1. Obtain the source: yumdownloader --source xorg-x11-server- common.i686 2. Extract the RPM to a subdirectory structure (in my case, ~/source/xorg-x11-server-x.xx.x-y.fc17.src) 3. Extract the xorg-server-x.xx.x.tar.bz2 file (contained in the directory created in step 2) to source subdirectories of that directory (in my case ~/source/xorg-x11-server-x.xx.x-y.fc.src/xorg-server-x.x.xx) created in step 2. 4. Modify the rrcrtc.c source code in the randr subdirectory (~/source/xorg-x11-server-x.xx.x-y.fc.src/xorg-server-x.x.xx/randr) as Chris states. I had to apply the patch manually, however it's very straightforward. The following steps were issued from within the xorg-server-x.xx.x subdirectory created in step 3 above and presume you have all required development tools installed. 5. Command: ./configure --prefix=/usr. 6. Command: make 7. Command: sudo make install I performed these steps on version 1.12.2-2 as well as on 1.12.2-4 and after testing each patch, I reinstalled (yum reinstall xorg-x11-server-common.i386) standard code to verify repeatability. In each case, scanning/panning was enabled following application of the patch. I am running this on an Acer Aspire AOD257 which has (of course) an integrated trackpad. One issue I have noticed is that after application of the patch, the trackpad scrolling functions are disabled. That is to say, the trackpad continues to function as a mouse, but the finger drag along the right side of the trackpad no longer functions. Under touchpad-system settings (KDE desktop), the touchpad information indicates device not found. I cannot explain the relationship between this function and the patch, but will do more testing -- has anyone else on a netbook noticed this condition? -- 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/883319 Title: xrandr --scale restricts area in which mouse moves To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/883319/+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 589485]
May the so called developers with I know better attitude be treated by physicists with the same attitude! They broke the thing for BUG compatibility with an obsolete piece of crap for a single use case already handled in corresponding application (a web browser), they told us to go sink in the mailing lists and now they are too busy to at least accept the knob. Folks, hallo! Anyone there? Or everyone reading mail on a low DPI 64 plasma? -- 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/589485 Title: Ignores physical display size and calculates based on 96DPI To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/589485/+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 416421] Re: [gm45] X crash on X200s with dual monitors (using DisplayPort)
** Changed in: xserver-xorg-video-intel Status: Confirmed = Fix Released -- 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/416421 Title: [gm45] X crash on X200s with dual monitors (using DisplayPort) To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/416421/+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 1030165] Re: Xorg can't use nvidia card with nouveau but doesn't fallback to vesa
Both xorg logs show traces of nvidia, so I can't say for sure what's going on, other than that those logs are useless and you want to make sure all traces of nvidia are removed before you create a Xorg log :) -- 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/1030165 Title: Xorg can't use nvidia card with nouveau but doesn't fallback to vesa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1030165/+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 1033783] Re: Wacom stylus and touch not recognised on Lenovo X220t
It's the built in device (embedded in the screen). Is there something equivalent I can do? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xf86-input-wacom in Ubuntu. https://bugs.launchpad.net/bugs/1033783 Title: Wacom stylus and touch not recognised on Lenovo X220t To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/1033783/+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 949600] Re: [MIR] xserver-xorg-video-dummy
Approving based on doko's the package itself looks ok for main comment. ** Changed in: xserver-xorg-video-dummy (Ubuntu) Status: New = Fix Committed ** Changed in: xserver-xorg-video-dummy (Ubuntu) Assignee: Matthias Klose (doko) = (unassigned) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-dummy in Ubuntu. https://bugs.launchpad.net/bugs/949600 Title: [MIR] xserver-xorg-video-dummy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-dummy/+bug/949600/+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 949600] Re: [MIR] xserver-xorg-video-dummy
xserver-xorg-video-dummy promoted (needed by xorg-gtest) ** Changed in: xserver-xorg-video-dummy (Ubuntu) Importance: Undecided = Wishlist ** Changed in: xserver-xorg-video-dummy (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-dummy in Ubuntu. https://bugs.launchpad.net/bugs/949600 Title: [MIR] xserver-xorg-video-dummy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-dummy/+bug/949600/+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 408903] Re: Does not handle microphone mute button (KEY_MICMUTE)
That's odd, the only thing I changed is a configuration file /lib/udev/keymaps/module-lenovo . If you want, you can install the old udev and just modify that file and you _should_ have it working. What distro/version are you using? I can help out by debugging on the same platform. Here's the patch if you want to edit module-lenovo yourself: https://bazaar.launchpad.net/~jm- leddy/ubuntu/quantal/udev/micmute/view/head:/debian/patches/remap_micmute.patch -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/408903 Title: Does not handle microphone mute button (KEY_MICMUTE) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/408903/+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 1039148] Re: When logging in to Unity, the Desktop session crashes
Here's some output from my dmesg regarding Xorg as well; not sure if that helps at all... [3.576578] Pid: 1127, comm: Xorg Tainted: P O 3.5.0-11-generic #11-Ubuntu [3.576579] Call Trace: [3.576583] [81051c4f] warn_slowpath_common+0x7f/0xc0 [3.576585] [81051caa] warn_slowpath_null+0x1a/0x20 [3.576587] [81043435] __ioremap_caller+0x335/0x380 [3.576643] [a0de3cc5] ? os_map_kernel_space+0x85/0xf0 [nvidia] [3.576645] [810434b4] ioremap_cache+0x14/0x20 [3.576686] [a0de3cc5] os_map_kernel_space+0x85/0xf0 [nvidia] [3.576729] [a0daf918] _nv014877rm+0x76/0x92 [nvidia] [3.576765] [a07dea1e] ? _nv009673rm+0x89/0x142 [nvidia] [3.576800] [a07deb8f] ? _nv014448rm+0xb8/0x102 [nvidia] [3.576835] [a07df042] ? _nv014486rm+0x58/0x9e [nvidia] [3.576871] [a07daaa8] ? _nv014458rm+0xbe/0x2f0 [nvidia] [3.576906] [a07dad85] ? _nv014491rm+0xab/0x174 [nvidia] [3.576940] [a07dae9e] ? _nv014457rm+0x50/0x5d [nvidia] [3.576976] [a07e1072] ? _nv014432rm+0x82d/0x96b [nvidia] [3.577018] [a0dbf7ef] ? _nv012658rm+0x174/0x573 [nvidia] [3.577059] [a0dbf76d] ? _nv012658rm+0xf2/0x573 [nvidia] [3.577105] [a082b261] ? _nv004021rm+0x1bb/0x19e9 [nvidia] [3.577196] [a0b82ef9] ? _nv004046rm+0x8690/0xae8b [nvidia] [3.577284] [a0b818bb] ? _nv004046rm+0x7052/0xae8b [nvidia] [3.577316] [a07b3d0c] ? _nv009980rm+0x25/0x40 [nvidia] [3.577358] [a0dbf501] ? _nv014932rm+0x7c9/0x943 [nvidia] [3.577399] [a0dc04af] ? _nv001095rm+0x42a/0x6b4 [nvidia] [3.577441] [a0db8ef4] ? rm_init_adapter+0xac/0x146 [nvidia] [3.577481] [a0dd8f74] ? nv_kern_open+0x4b4/0x800 [nvidia] -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/1039148 Title: When logging in to Unity, the Desktop session crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1039148/+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 973096] Re: Nvidia driver causes xorg crash
Here's some output from my dmesg regarding Xorg as well; not sure if that helps at all... [3.576578] Pid: 1127, comm: Xorg Tainted: P O 3.5.0-11-generic #11-Ubuntu [3.576579] Call Trace: [3.576583] [81051c4f] warn_slowpath_common+0x7f/0xc0 [3.576585] [81051caa] warn_slowpath_null+0x1a/0x20 [3.576587] [81043435] __ioremap_caller+0x335/0x380 [3.576643] [a0de3cc5] ? os_map_kernel_space+0x85/0xf0 [nvidia] [3.576645] [810434b4] ioremap_cache+0x14/0x20 [3.576686] [a0de3cc5] os_map_kernel_space+0x85/0xf0 [nvidia] [3.576729] [a0daf918] _nv014877rm+0x76/0x92 [nvidia] [3.576765] [a07dea1e] ? _nv009673rm+0x89/0x142 [nvidia] [3.576800] [a07deb8f] ? _nv014448rm+0xb8/0x102 [nvidia] [3.576835] [a07df042] ? _nv014486rm+0x58/0x9e [nvidia] [3.576871] [a07daaa8] ? _nv014458rm+0xbe/0x2f0 [nvidia] [3.576906] [a07dad85] ? _nv014491rm+0xab/0x174 [nvidia] [3.576940] [a07dae9e] ? _nv014457rm+0x50/0x5d [nvidia] [3.576976] [a07e1072] ? _nv014432rm+0x82d/0x96b [nvidia] [3.577018] [a0dbf7ef] ? _nv012658rm+0x174/0x573 [nvidia] [3.577059] [a0dbf76d] ? _nv012658rm+0xf2/0x573 [nvidia] [3.577105] [a082b261] ? _nv004021rm+0x1bb/0x19e9 [nvidia] [3.577196] [a0b82ef9] ? _nv004046rm+0x8690/0xae8b [nvidia] [3.577284] [a0b818bb] ? _nv004046rm+0x7052/0xae8b [nvidia] [3.577316] [a07b3d0c] ? _nv009980rm+0x25/0x40 [nvidia] [3.577358] [a0dbf501] ? _nv014932rm+0x7c9/0x943 [nvidia] [3.577399] [a0dc04af] ? _nv001095rm+0x42a/0x6b4 [nvidia] [3.577441] [a0db8ef4] ? rm_init_adapter+0xac/0x146 [nvidia] [3.577481] [a0dd8f74] ? nv_kern_open+0x4b4/0x800 [nvidia] -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/973096 Title: Nvidia driver causes xorg crash To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/973096/+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 745112]
Is this still an issue on 3.6-rc kernels? -- 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/745112 Title: [arrandale] desktop is messed up with external monitors (x86_64) To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/745112/+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 also confirm that downgrading to xserver-xorg-input- synaptics=1.5.99.902 appears to have solved the problem. -- 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 1007575] Re: SB Arena USB headset causes X BUG, can't click outside window
I'm available to assist with any debugging or testing for this issue. I have different hardware, but it is my understanding that I am running into the same issue. -- 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/1007575 Title: SB Arena USB headset causes X BUG, can't click outside window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1007575/+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 1037896] Re: Starting Firefox kills xserver immediately
As a *workaround*, you can enable the nouveau driver in /etc/X11/xorg: Unless you happen to own a GTX 560/GF114 card like some of us, as there is a curent Nouveau bug that causes it to throw PFIFO - playist update failed, and failed to idle channel... messages while repeatedly restarting LightDM, ever since a commit on April 30th. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/1037896 Title: Starting Firefox kills xserver immediately To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1037896/+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 1038615] Re: Wacom Intuos 5 button touch moves the cursor to the top left corner
Hi Timo, so I've purged the ppa and connected the intuos 5 after a restart... same behavior as before - The tablet works, but still the nasty bug with the left buttons on the tablet...how can I help to supply information about this issue? We have to be a bit quick because it could be a hardware defect too - when we are at this point, I'll return it immediately (The returning days limit is one week from now on) Greetings, Thomas -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xf86-input-wacom in Ubuntu. https://bugs.launchpad.net/bugs/1038615 Title: Wacom Intuos 5 button touch moves the cursor to the top left corner To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/1038615/+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 1040206] [NEW] nvidia binary driver doesn't support XRandR 1.2/1.3
Public bug reported: Hi, The nvidia binary graphics drivers shipped with Ubuntu 12.04 LTS do no support XRandR 1.2/1.3. Consequently it is not possible to create or use display colour management profiles using the colour tool, as this tool relies on XRandR 1.2. nvidia released an updated version of the binary graphics driver recently. http://www.phoronix.com/scan.php?page=news_itempx=MTA5NTY Please can this be back-ported to the LTS release? It's a major problem for people using Ubuntu for creative work otherwise. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xserver-xorg 1:7.6+12ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24 Uname: Linux 3.2.0-29-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.0.1-0ubuntu12 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz Date: Wed Aug 22 18:32:12 2012 DistUpgraded: 2012-05-13 21:47:36,577 DEBUG enabling apt cron job DistroCodename: precise DistroVariant: ubuntu DkmsStatus: virtualbox, 4.1.12, 3.2.0-25-generic, x86_64: installed virtualbox, 4.1.12, 3.2.0-26-generic, x86_64: installed virtualbox, 4.1.12, 3.2.0-27-generic, x86_64: installed virtualbox, 4.1.12, 3.2.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation G98M [GeForce G 105M] [10de:06ec] (rev a1) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Device [1558:0806] InstallationMedia: Ubuntu 10.04 Lucid Lynx - Beta amd64 (20100318) MachineType: System76, Inc. Pangolin Performance ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-29-generic root=UUID=6f960d0a-0f5f-4dd5-82b3-bed564518bdc ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to precise on 2012-05-13 (100 days ago) dmi.bios.date: 04/06/2009 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 1.02.22 dmi.board.asset.tag: Tag 12345 dmi.board.name: Pangolin Performance dmi.board.vendor: System76, Inc. dmi.board.version: panp5 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr1.02.22:bd04/06/2009:svnSystem76,Inc.:pnPangolinPerformance:pvrpanp5:rvnSystem76,Inc.:rnPangolinPerformance:rvrpanp5:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: Pangolin Performance dmi.product.version: panp5 dmi.sys.vendor: System76, Inc. version.compiz: compiz 1:0.9.7.8-0ubuntu1.4 version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.32-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.3+8.0.2-0ubuntu3.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.3+8.0.2-0ubuntu3.2 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1.2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2 ** Affects: xorg (Ubuntu) Importance: Undecided Assignee: Alberto Milone (albertomilone) Status: New ** Tags: amd64 apport-bug compiz-0.9 precise referred-by-support running-unity ubuntu -- 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/1040206 Title: nvidia binary driver doesn't support XRandR 1.2/1.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1040206/+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 1040206] Re: nvidia binary driver doesn't support XRandR 1.2/1.3
** Changed in: xorg (Ubuntu) Assignee: (unassigned) = Alberto Milone (albertomilone) -- 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/1040206 Title: nvidia binary driver doesn't support XRandR 1.2/1.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1040206/+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 1040206] Re: nvidia binary driver doesn't support XRandR 1.2/1.3
-- 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/1040206 Title: nvidia binary driver doesn't support XRandR 1.2/1.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1040206/+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 1038615] Re: Wacom Intuos 5 button touch moves the cursor to the top left corner
And as an addition: Even when I put the stylus in relative mode and hold it above the tablet causes touching the left buttons almost every time a jump in the left corner and back -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xf86-input-wacom in Ubuntu. https://bugs.launchpad.net/bugs/1038615 Title: Wacom Intuos 5 button touch moves the cursor to the top left corner To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/1038615/+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 1036114] Re: (usability) Apport dialog asks a question that user has no way of answering
You say the issue here is not to do with the questions themselves but that the user needs to be given more information prior to seeing these questions. Could you elaborate on what that information should comprise? For example, would it be sufficient to simply say, Compiz has crashed? Or would you want to see the detailed stack trace and so on? (I'm concerned there may be a chicken-and-egg problem in solving this, but want to better understand your concern first.) (Also, if you have suggestions on improving the phrasing of the five questions, I'm open to feedback on that.) ** Changed in: xdiagnose (Ubuntu) Importance: Undecided = Medium ** Changed in: xdiagnose (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xdiagnose in Ubuntu. https://bugs.launchpad.net/bugs/1036114 Title: (usability) Apport dialog asks a question that user has no way of answering To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdiagnose/+bug/1036114/+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 589485] Re: Ignores physical display size and calculates based on 96DPI
With the new Retina displays and the trend that they impose we are shortly going to have displays dpi values from 90 (old large monitors) to over 300 (newer laptops and tablets). Assuming 96 dpi for everything will surely lead to interesting times. -- 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/589485 Title: Ignores physical display size and calculates based on 96DPI To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/589485/+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 1039148] Re: When logging in to Unity, the Desktop session crashes
I tried something different to generate more meaningful output. -- Logged in from the command-line and ran startx. The session started just fine, however there was no Gnome Panel loaded whatsoever. -- Pressed F12 to launch Guake terminal and typed unity --replace and hit enter. This dropped me immediately to the shell and I observed an error message regarding a segmentation fault pertaining to the nvidia-current driver (please see screen photos attached). ** Attachment added: IMG_0855.JPG https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1039148/+attachment/3272142/+files/IMG_0855.JPG -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/1039148 Title: When logging in to Unity, the Desktop session crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1039148/+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 1039148] Re: When logging in to Unity, the Desktop session crashes
** Attachment removed: IMG_0855.JPG https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1039148/+attachment/3272142/+files/IMG_0855.JPG -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/1039148 Title: When logging in to Unity, the Desktop session crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1039148/+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 1039148] Re: When logging in to Unity, the Desktop session crashes
** Attachment added: IMG_0854.JPG https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1039148/+attachment/3272147/+files/IMG_0854.JPG -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/1039148 Title: When logging in to Unity, the Desktop session crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1039148/+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 1039148] Re: When logging in to Unity, the Desktop session crashes
** Attachment added: IMG_0855.JPG https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1039148/+attachment/3272152/+files/IMG_0855.JPG -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/1039148 Title: When logging in to Unity, the Desktop session crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1039148/+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 973096] Re: Nvidia driver causes xorg crash
I tried something different to generate more meaningful output. -- Logged in from the command-line and ran startx. The session started just fine, however there was no Gnome Panel loaded whatsoever. -- Pressed F12 to launch Guake terminal and typed unity --replace and hit enter. This dropped me immediately to the shell and I observed an error message regarding a segmentation fault pertaining to the nvidia-current driver (please see screen photos attached). ** Attachment added: IMG_0854.JPG https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/973096/+attachment/3272168/+files/IMG_0854.JPG -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/973096 Title: Nvidia driver causes xorg crash To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/973096/+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 973096] Re: Nvidia driver causes xorg crash
** Attachment added: IMG_0855.JPG https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/973096/+attachment/3272169/+files/IMG_0855.JPG -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/973096 Title: Nvidia driver causes xorg crash To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/973096/+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 973096] Re: Nvidia driver causes xorg crash
This happens on Quantal alpha 3, installed on an Asus G75VW, with a dedicated GeForce 660M GTX. On my previous Dell XPS 15z, running a descrete nVidia Optimus card, it worked just fine when running apps with optirun. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/973096 Title: Nvidia driver causes xorg crash To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/973096/+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 1040239] [NEW] Black screen on startup or resume (only sometimes)
Public bug reported: I'm not sure this is an xorg bug or kernel driver / other. Sometimes, when I resume the computer from a suspend, the screen stays black. Very black. It's now just happened on turning on the computer as well. This happens about once out of every 4 or 5 times (as far as I remember). I am using: Ubuntu 12.04 32-bit (Sometimes, the computer crashes when resuming also, but I'll file a different bug once that happens next time, as I think it's a different issue.) I can get round this by switching to a terminal and switching back (ctrl-alt-f1 then ctrl-alt-f7), but it's still rather annoying. I have tried searching for a solution to this, and have found similar problems, but mostly related to nVidia graphics cards and/or old Ubuntu versions, which is not my case. Is there any debugging information I can send to help fix this bug? Thanks ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xorg 1:7.6+12ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-29.46-generic-pae 3.2.24 Uname: Linux 3.2.0-29-generic-pae i686 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.0.1-0ubuntu12 Architecture: i386 CompizPlugins: [core,composite,opengl,decor,mousepoll,move,resize,imgpng,gnomecompat,grid,wall,snap,annotate,place,compiztoolbox,unitymtgrabhandles,regex,text,resizeinfo,shift,session,animation,workarounds,fade,expo,scale,ezoom,unityshell] CompositorRunning: compiz Date: Wed Aug 22 20:06:15 2012 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu DkmsStatus: fglrx, 8.960, 3.2.0-29-generic, i686: installed fglrx, 8.960, 3.2.0-29-generic-pae, i686: installed ExtraDebuggingInterest: Yes, even including gdb or git bisection work if needed GraphicsCard: Advanced Micro Devices [AMD] nee ATI Whistler LE [AMD Radeon HD 6625M Graphics] [1002:6742] (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Device [1179:fb31] InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) JockeyStatus: xorg:fglrx_updates - Controlador para gráficos FGLRX propietario de ATI/AMD (actualizaciones post-lanzamiento) (Privativo, Desactivado, No está en uso) kmod:rtl8723e - Realtek 8723E 802.11n PCI wireless (Libre, Activado, En uso) xorg:fglrx - Controlador gráfico propietario FGLRX para ATI/AMD (Privativo, Activado, En uso) MachineType: TOSHIBA SATELLITE C850-11L ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-29-generic-pae root=UUID=6e89e88d-e532-43d7-98a7-a7ecc0b5dc0e ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 1.30 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name1 dmi.board.vendor: Type2 - Board Vendor Name1 dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvr1.30:bd03/29/2012:svnTOSHIBA:pnSATELLITEC850-11L:pvrPSKCCE-01600QCE:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.name: SATELLITE C850-11L dmi.product.version: PSKCCE-01600QCE dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.7.8-0ubuntu1.4 version.fglrx-installer: fglrx-installer N/A version.libdrm2: libdrm2 2.4.32-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.3+8.0.2-0ubuntu3.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.3+8.0.2-0ubuntu3.2 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1.2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 i386 precise running-unity ubuntu -- 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/1040239 Title: Black screen on startup or resume (only sometimes) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1040239/+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 1040239] Re: Black screen on startup or resume (only sometimes)
-- 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/1040239 Title: Black screen on startup or resume (only sometimes) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1040239/+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 1039148] Re: When logging in to Unity, the Desktop session crashes
** Tags added: compiz -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/1039148 Title: When logging in to Unity, the Desktop session crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1039148/+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
