Re: [Ubuntu-x-swat] [Bug 330545] Re: xserver-video-ati defaults MigrationHeuristic to always. Smart and greedy would give vissible improvement to performance.
On Wed, May 13, 2009 at 11:25 AM, Bryce Harrington wrote: > We messed around a bunch with different migration heuristic options with > the intel driver. Certainly there were some measurable improvements > when using greedy, however it was found to cause graphics corruption on > some systems (indeed, corruption issues are to be expected by design > with greedy). > > As I understand it, all these performance issues are part and parcel of > iniquities in DRI1/EXA design, and so in theory DRI2 should solve them. > I'm not sure when we can expect DRI2 for -ati, but it's already > available for -intel so I expect it should be arriving soon, hopefully > in the Karmic time frame. > > Hopefully this explains why I don't think we need to pursue greedy for > ati. > Radeon drm module didn't make it to 2.6.30 kernel which means that Karmic won't have dri2 for radeon cards unless there is plan to use 2.6.31 or backport the changes from Fedora. Maybe it would be good idea to have gui option to select migration heuristic because it gives clear boost for system where bandwidth to graphics card is very limiting factor (like older radeon cards) I haven't at least seen or heard about corruption with radeons if changing heuristics. Most often cause is accelerated download from screen extension. Anyway. I think "smart" is the better option than "greedy" if wanting to get the least lag for the UI. -- xserver-video-ati defaults MigrationHeuristic to always. Smart and greedy would give vissible improvement to performance. https://bugs.launchpad.net/bugs/330545 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati 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 1377220] Re: Google Chrome crash with mesa 10.3 on Intel GPU
Issue might be actually the X driver and mesa disagreeing how to handle the memory buffers. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757435 ** Bug watch added: Debian Bug tracker #757435 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757435 -- 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/1377220 Title: Google Chrome crash with mesa 10.3 on Intel GPU To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1377220/+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 348450] Re: [X1650] freeze on opengl games (bzflag, alienarena)
To fix most of freezes it is enough to use xorg-edgers packages. But there is still sometimes small chance for GPU hang. Now I did compile vanila kernel for jaunty to get KMS where remaining hang problems have disappeared. So non-kms Karmic: Small chance for hang. Reproducing in xmoto level "Green hill zone act 3". There is a small pit after spring where it hangs most of times. kms-karmic: None so far found but testing has been too little to rule out completely. -- [X1650] freeze on opengl games (bzflag, alienarena) https://bugs.launchpad.net/bugs/348450 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati 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 321151] Re: System(input) freezes at not defined reason
Symptoms are caused by gpu hang (your graphics card is running in a forever loop). Same time driver is waiting for signal from the card that operations have done. So result is that the driver gets blocked which blocks most of others parts of kernel too. Only solution to aoid this situation is to use the newer KMS driver which has detection system for GPU hang. -- System(input) freezes at not defined reason https://bugs.launchpad.net/bugs/321151 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati 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 509273] Re: [Lucid] KMS doesn't work properly with old Radeon cards
It would help if there would be kernel message log from original problem. Setting up netconsole to stream the kernel messages to 2nd machine is probably the easiest solution. Screen corruption is different bug and most likely caused by problematic AGP transfers. You can either set your card to PCI mode or disable download from screen accerlation from exa. Both will affect performance quite a lot. -- [Lucid] KMS doesn't work properly with old Radeon cards https://bugs.launchpad.net/bugs/509273 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati 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 507148] Re: [lucid] desktop runs out of video memory on ATI Radeon Mobility 7500
** Bug watch added: freedesktop.org Bugzilla #24810 https://bugs.freedesktop.org/show_bug.cgi?id=24810 ** Also affects: xserver-xorg-driver-ati via https://bugs.freedesktop.org/show_bug.cgi?id=24810 Importance: Unknown Status: Unknown -- [lucid] desktop runs out of video memory on ATI Radeon Mobility 7500 https://bugs.launchpad.net/bugs/507148 You received this bug notification because you are a member of Ubuntu-X, which is the registrant for xserver-xorg-driver-ati. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-x-swat] [Bug 387777] Re: no power set make ati mobility hot
You can install the newest driver from the https://launchpad.net/~xorg-edgers (DDX only repository) which has static power management code. You can set ForceLowPowerMode in xorg.conf. You can see more info about possible options for radeon driver using "man radeon" command. 2010/1/31 Philip Muškovac > ** Package changed: ubuntu => xserver-xorg-video-ati (Ubuntu) > > -- > no power set make ati mobility hot > https://bugs.launchpad.net/bugs/38 > You received this bug notification because you are subscribed to > xserver-xorg-video-ati in ubuntu. > -- no power set make ati mobility hot https://bugs.launchpad.net/bugs/38 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-x-swat] [Bug 361060] Re: [X1400] Extra X sessions very slow because of EXA and no DRI
KMS=Kernel modesetting which you have to enable by passing modeset=1 to radeon kernel module. KMS driver fixes the bug and the commit you think about is for KMS case. KMS is still under heavy development and getting it to working state requires sometimes quite a lot of tweaking depending of hw. On Tue, Feb 2, 2010 at 2:02 PM, Øyvind Stegard wrote: > I agree, it would be nice to get this fixed. Let the driver fallback to > shadowfb-technique if DRI-init fails, I'm sure that would help a lot. > Guest sessions are next to unusable right now. The strange thing is I > remember seeing patches upstream that were meant to revert to non-EXA > acceleration techniques if DRI-init fails, but that simply doesn't work > (I keep radeon-driver updated from git master). EXA is always chosen, > even though it cannot work properly without DRI. > > Here are some interesting related commits to radeon driver: > --- > commit d302481493ff61eb7f8648b7afe7407b6b653cf7 > Author: Jerome Glisse > Date: Wed Sep 16 15:18:40 2009 +0200 > > radeon/kms: fallback to shadowfb if kernel report acceleration is off > > This will fallback to shadowfb is GPU accel failed somewhere during > KMS kernel init. > --- > commit f564460e94c9d0f1cf3ff4b8535481b2b8b4e9c1 > Author: Alex Deucher > Date: Sat Aug 1 16:53:47 2009 -0400 > > radeon: use XAA in some cases > > Use XAA in low memory situations or when the DRI is disabled. > Using shadowfb might also be a viable option, maybe even a better option... > fixes bug 21683 > --- > commit 758fcc33c232c32e7b66261fca51de161d1a4800 > Author: Dave Airlie > Date: Tue Mar 10 10:34:13 2009 +1000 > > r600: enable DRI by default > > fallback to shadowfb if DRI fails pre init > --- > commit 4fc978f3d83ef6370c9715e7ca5350640ccbfe10 > Author: Alex Deucher > Date: Thu Feb 26 12:10:08 2009 -0500 > > R6xx/R7xx: use shadowfb if DRI is disabled > --- > > One would have thought commit f564460e.. might help, but it does not > trigger for guest sessions in Ubuntu Karmic, and EXA is chosen instead > (at least for my X1400/r500). Would be really nice if commit d3024814 > could be done for the r500 UMS-case as well. Perhaps a new upstream bug > report for this problem should be filed.. > > -- > [X1400] Extra X sessions very slow because of EXA and no DRI > https://bugs.launchpad.net/bugs/361060 > You received this bug notification because you are subscribed to > xserver-xorg-video-ati in ubuntu. > -- [X1400] Extra X sessions very slow because of EXA and no DRI https://bugs.launchpad.net/bugs/361060 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-x-swat] [Bug 361060] Re: [X1400] Extra X sessions very slow because of EXA and no DRI
No. Too much work compared to benefits when there exist nearly working solution. If you cannot use xrandr modelines you should report the bug bugs.freedesktop.org so it gets fixed before lucid. http://wiki.debian.org/XStrikeForce/HowToRandR12 for good xrandr configuration help. The performance problem you point is mostly caused very expensive gnome theme that Ubuntu is using. (A lot of calls exaTrapezoids which is not accelerated by free drivers yet) Problematic code path were specially bad with xserver 1.6 and KMS while 1.7 provides some improved performance for Ubuntu theme. On Tue, Feb 2, 2010 at 5:17 PM, Neil Broomfield wrote: > I tired KMS and can confirm that it seems to resolve this issue, however > it currently comes with it's own problems, I’m sure this is because it’s > still under heavy development, the most annoying of which was the lack > of Mode lines previously available under X control. I posted something > on this thread regarding that, when I tried it, > > https://bugs.launchpad.net/firefox/+bug/38131?comments=all > > I've since moved back to non KMS mode. Can this DRI/DMI Issue not be > fixed under X Mode Setting until KMS is viable? > > -- > [X1400] Extra X sessions very slow because of EXA and no DRI > https://bugs.launchpad.net/bugs/361060 > You received this bug notification because you are subscribed to > xserver-xorg-video-ati in ubuntu. > -- [X1400] Extra X sessions very slow because of EXA and no DRI https://bugs.launchpad.net/bugs/361060 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-x-swat] [Bug 517395] Re: [lucid][rv620] xorg fails to start without radeon.modeset=0
Do you have dmesg from any of the failed boots? /var/log/message or /var/log/kern.log should hold the logs from previous boots, Do you have some custom configuration in xorg.conf? If yes then you should renme the xorg.conf and test without special configuration. On Fri, Feb 5, 2010 at 6:31 AM, Robert Wall wrote: > I restarted it a few more times (without radeon.modeset=0) to see if any > other bizzare things would happen. Twice, I got to the screen with an > underscore in the corner, but it had a (moveable) mouse cursor in the > middle. Doing Ctrl-Alt-F1 got me to a text terminal. Switching back to > Xorg with Ctrl-Alt-F7 got me to my desktop. I started up Firefox to get > to Launchpad, and the computer then stopped responding to keyboard and > mouse input. Had to use magic SysRq keys to shutdown. Xorg log is > attached. > > ** Attachment added: "Xorg.0.log.old" > http://launchpadlibrarian.net/38780765/Xorg.0.log.old > > -- > [lucid][rv620] xorg fails to start without radeon.modeset=0 > https://bugs.launchpad.net/bugs/517395 > You received this bug notification because you are subscribed to > xserver-xorg-video-ati in ubuntu. > -- [lucid][rv620] xorg fails to start without radeon.modeset=0 https://bugs.launchpad.net/bugs/517395 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati 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 517395] Re: [lucid][rv620] xorg fails to start without radeon.modeset=0
Problem is that Ubuntu kernel fails to initialize radeon kernel module. Then failure path has null pointer reference which causes the visible error message. Can someone add this to the kernel bugs? Work around for users hacing this error is to boot older kernel that did wotk with KMS. -- [lucid][rv620] xorg fails to start without radeon.modeset=0 https://bugs.launchpad.net/bugs/517395 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-x-swat] [Bug 507148] Re: [lucid] desktop runs out of video memory on ATI Radeon Mobility 7500
On Tue, Feb 9, 2010 at 7:43 PM, Manoj Iyer wrote: > > *snip* > > This is a 64bit kernel, I can also upload a x86 kernel on request. > Radeon 7500 is far older than x86_64. It is from year 1999 if my memory servers right. -- [lucid] desktop runs out of video memory on ATI Radeon Mobility 7500 https://bugs.launchpad.net/bugs/507148 You received this bug notification because you are a member of Ubuntu-X, which is the registrant for xserver-xorg-driver-ati. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-x-swat] [Bug 520618] Re: screen corruption on 10.04 alpha2
On Sun, Feb 14, 2010 at 9:06 PM, Ákos Maróy wrote: > what information would you need - maybe I can collect it manually > instead of apport-collect? > dmesg, xorg.log, lspci -vvvnn Also it would be nice if you could capture the corruption to a screenshot. -- screen corruption on 10.04 alpha2 https://bugs.launchpad.net/bugs/520618 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-x-swat] [Bug 520618] Re: screen corruption on 10.04 alpha2
On Sun, Feb 14, 2010 at 9:52 PM, Ákos Maróy wrote: > added log files - how would I screen capture the corruption? > > -- > screen corruption on 10.04 alpha2 > https://bugs.launchpad.net/bugs/520618 > You received this bug notification because you are subscribed to > xserver-xorg-video-ati in ubuntu. > Press print screen key (Prt Sc in my keyboard) and perss save from the dialog that opens. -- screen corruption on 10.04 alpha2 https://bugs.launchpad.net/bugs/520618 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati 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 522284] Re: [RV770][Lucid][Kubuntu] graphical glitches
http://bugzilla.kernel.org/show_bug.cgi?id=15186 ? ** Bug watch added: Linux Kernel Bug Tracker #15186 http://bugzilla.kernel.org/show_bug.cgi?id=15186 -- [RV770][Lucid][Kubuntu] graphical glitches https://bugs.launchpad.net/bugs/522284 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati 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 490031] Re: Radeon 9250 no 3D.
00:00.0 Host bridge [0600]: VIA Technologies, Inc. VT8385 [K8T800 AGP] Host Bridge [1106:3188] (rev 01) Subsystem: ASUSTeK Computer Inc. Device [1043:80a3] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- (32-bit, prefetchable) Capabilities: Kernel driver in use: agpgart-amd64 It might not be early enough to load the module from /etc/modules. udev should handle the agp loading. At least your agp module is loaded early enough in your original dmesg. But radeon module initialization is silently failing. Can you try mainline kernel ppa to check if that kernel works for you? https://wiki.ubuntu.com/KernelTeam/MainlineBuilds -- Radeon 9250 no 3D. https://bugs.launchpad.net/bugs/490031 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-x-swat] [Bug 490031] Re: Radeon 9250 no 3D.
On Tue, Feb 16, 2010 at 11:40 PM, Walter Kerkhofs wrote: > [ 2.314151] [drm] Initialized drm 1.1.0 20060810 > [ 2.42] [drm] radeon default to kernel modesetting DISABLED. > > [ 27.352666] agpgart-amd64 :00:00.0: AGP 3.5 bridge > [ 27.352686] agpgart-amd64 :00:00.0: putting AGP V3 device into 8x mode > [ 27.352755] pci :01:00.0: putting AGP V3 device into 8x mode > This log looks clearly wrong in that agp is loaded too late. This bug might be some udev configuration bug. I don't know how to configure udev so can't help there. You should see "Loading R200 Microcode" in dmesg when radeon module is loading correctly. > This is my dmesg from today with no changes at all. > As you can see DRM gets loaded before the agpgart module, and there is a line > further up above about AGP but that is about the agp bus that gets found. > > So before I try the mainline kernel I want to know wath you think of > this. > No point testing mainline kernel until module loading is fixed. > Greetings, > > Walter Kerkhofs > -- Radeon 9250 no 3D. https://bugs.launchpad.net/bugs/490031 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati 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 490031] Re: Radeon 9250 no 3D.
agp module not loaded before drm. I think this should be fixed in udev. ** Package changed: xserver-xorg-video-ati (Ubuntu) => udev (Ubuntu) -- Radeon 9250 no 3D. https://bugs.launchpad.net/bugs/490031 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-x-swat] [Bug 522167] Re: adding second monitor changes colors/colours in first monitor
xrandr is the tool that you are lookin for: xrandr --output --gamma 1.0:1.0:1.0 output might be DVI-0 but you can check it with xrandr -q. But I don't understand why 2nd monitor would mess the gamma settings in first one. This would need some more investigation to find the cause for problem. -- adding second monitor changes colors/colours in first monitor https://bugs.launchpad.net/bugs/522167 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-x-swat] [Bug 522394] Re: [Lucid alpha2] ATI Mobility Radeon 9600 not displaying on LVDS
On Thu, Feb 18, 2010 at 7:03 PM, stefan.witwicki wrote: > Even with the additional package, I am unable to get desktop effects > working. Typing "compiz" results in the following output: > > compiz (core) - Fatal: Software rendering detected. > compiz (core) - Error: Failed to manage screen: 0 > compiz (core) - Fatal: No manageable screens found on display :0.0 > Launching fallback window manager > > This seems to be closely-related to the original problem. > > Note: Effects were working for this hardware in the Ubuntu 9.10 (Karmic) > release, without having to install any proprietary drivers. > dmesg and xorg.log, please. You have some problem that disables dri. -- [Lucid alpha2] ATI Mobility Radeon 9600 not displaying on LVDS https://bugs.launchpad.net/bugs/522394 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-x-swat] [Bug 522394] Re: [Lucid alpha2] ATI Mobility Radeon 9600 not displaying on LVDS
fglrx-kernel-source is not part of driver that you want. You should remove it. On Thu, Feb 18, 2010 at 7:35 PM, stefan.witwicki wrote: > > ** Attachment added: "Xorg log after installing fglrx-kernel-source" > http://launchpadlibrarian.net/39370583/Xorg.0.log > Your 3D rendering is disabled because radeon kernel module is not loaded in boot. Kernel module is required for all acceleration in open source drivers. -- [Lucid alpha2] ATI Mobility Radeon 9600 not displaying on LVDS https://bugs.launchpad.net/bugs/522394 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati 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 522394] Re: [Lucid alpha2] ATI Mobility Radeon 9600 not displaying on LVDS
The initial black screen problem looks like kernel modesetting bug. So workaround would be booting with radeon.modeset=0 to use old UMS driver. There has bee quite a lot fixes to mode selection in 2.6.33 kernel which Ubuntu should backport to 2.6.32 kernel to fix the bugs in 2.6.32. -- [Lucid alpha2] ATI Mobility Radeon 9600 not displaying on LVDS https://bugs.launchpad.net/bugs/522394 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-x-swat] [Bug 522394] Re: [Lucid alpha2] ATI Mobility Radeon 9600 not displaying on LVDS
On Thu, Feb 18, 2010 at 11:41 PM, stefan.witwicki wrote: > Pauli, > > Thanks for the help. > >> fglrx-kernel-source is not part of driver that you want. You should >> remove it. > > After removing that package, I was back to the blackscreen problem > (e.g. display showing up only on the external monitor), but my visual effects > (compiz) were indeed working! > >> The initial black screen problem looks like kernel modesetting bug. So >> workaround would be booting with radeon.modeset=0 to use old UMS driver. > > This workaround fixed the blackscreen problem! However, compiz doesn't seem > to play nicely with the old driver: > --- > $ compiz > WARNING: Application calling GLX 1.3 function "glXCreatePixmap" when GLX 1.3 > is not supported! This is an application bug! > ^X^CWARNING: Application calling GLX 1.3 function "glXDestroyPixmap" when GLX > 1.3 is not supported! This is an application bug! > --- > The visual result is that the far right section of the display area > (effecting about 2/3 the screen of one of my monitors) wasn't displaying > properly... a colorful lack of refreshing and some blackness. > How big is your dual head? default virtual size maybe too small so you have to set it to size that your full desktop should be. see http://wiki.debian.org/XStrikeForce/HowToRandR12 for details > So it seems that at the moment, I can't have my cake (compiz) and eat it > too (on dual monitors). > KMS would auto adjust virtual desktop sizes when you add monitors to system. If you want KMS you could try mainline kernel builds from https://wiki.ubuntu.com/KernelTeam/MainlineBuilds -- [Lucid alpha2] ATI Mobility Radeon 9600 not displaying on LVDS https://bugs.launchpad.net/bugs/522394 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-x-swat] [Bug 522394] Re: [Lucid alpha2] ATI Mobility Radeon 9600 not displaying on LVDS
On Fri, Feb 19, 2010 at 1:01 AM, stefan.witwicki wrote: > Hm.. xrandr reports my virtual screen dimensions as 3200 x 1200, which > is correct (1600x1200 on VGA + 1600x1200 on LVDS). But maybe my hardware > does not actual support that large a display area. > Good catch. Your card only support only 2048x2048 rendering target. So even 1600x2400 is too much. I guess zaphod mode might work for dual screen if you want to experiment with it. But it will only work with KMS. -- [Lucid alpha2] ATI Mobility Radeon 9600 not displaying on LVDS https://bugs.launchpad.net/bugs/522394 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati 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 521260] Re: [lucid] HD3200 intermittently does not start, resulting in low-graphics mode
Please try daily mainline-ppa https://wiki.ubuntu.com/KernelTeam/MainlineBuilds and you will need a special firmware http://xorg.freedesktop.org/wiki/radeonBuildHowTo#TroubleshootingExtraFirmwareforR600.2BAC8-R700 This sounds like null pointer deference in init failure path that was fixed in 2.6.33-rc7 or rc8. Also firmware loading problem might be fixed in newer kernel. -- [lucid] HD3200 intermittently does not start, resulting in low-graphics mode https://bugs.launchpad.net/bugs/521260 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati 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 387013] Re: Ubuntu unusable by default with ATI HD4670 video card + monitor on DVI link (blank screen).
(WW) EDID preferred timing clock 162.00MHz exceeds claimed max 160MHz, fixing You should try to set the 1280x1024 as prefered mode in xorg.log just in case the highest resolution is causing the problem. -- Ubuntu unusable by default with ATI HD4670 video card + monitor on DVI link (blank screen). https://bugs.launchpad.net/bugs/387013 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-x-swat] [Bug 525400] Re: Virtual screen causes spontaneous complete system lockups
Your card limit is 2048x2048 for screen sizes if you want DRI. Driver should disable DRI in case you try to use larger than that sizes. (All acceleration) Do you have xorg.log where you have virtual size set in xorg.conf? -- Virtual screen causes spontaneous complete system lockups https://bugs.launchpad.net/bugs/525400 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-x-swat] [Bug 473098] Re: Switching user makes graphics slow for second user
This bug is already fixed in KMS driver. If Lucid enables KMS by default the problem will be fixed. On Mon, Feb 22, 2010 at 10:48 PM, Ben Blout wrote: > This seems like much more than a wish-list level problem. Many home > computers are used by more than one person, and with this bug, the > usability of Ubuntu is quite diminished. > > This will be a problem especially with Lucid if my understanding that > the radeonhd driver is being removed is correct. -- Switching user makes graphics slow for second user https://bugs.launchpad.net/bugs/473098 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-x-swat] [Bug 501551] Re: Xorg assert failure: *** glibc detected *** /usr/bin/X: double free or corruption (fasttop): 0x092447a8 ***
On Tue, Mar 2, 2010 at 12:35 PM, RdeWit wrote: > An extra comment: the many crashes that I mentioned in my initial report > have gone away after I replaced my memory modules. > > This problem however has not ceased to exist and every once or twice a > week I get no monitor input (at all) on startup of X (boot menu shows up > fine) and need to reboot the computer. > > After rebooting my apport tells me that Xorg had crashed, which is this > bug. > Can you try to collect valgrind report? You need to install xserver-xorg-core-dbg and xserver-xorg-video-radeon-dbg packages to get some debug symbols. Then you can start valgrind session from console with: sudo ls && sudo valgrind Xorg :1.0 &> /tmp/xorg.valgrind.log & sleep 15; export DISPLAY=:1.0; /etc/X11/Xsession -- Xorg assert failure: *** glibc detected *** /usr/bin/X: double free or corruption (fasttop): 0x092447a8 *** https://bugs.launchpad.net/bugs/501551 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-x-swat] [Bug 501551] Re: Xorg assert failure: *** glibc detected *** /usr/bin/X: double free or corruption (fasttop): 0x092447a8 ***
On Wed, Mar 3, 2010 at 11:23 PM, RdeWit wrote: > Hi Pauli, > > When would I start this valgrind session? Just any time, just to collect > information, immediately after the crash happens (logged in from another > machine), after reboot (when back in X) or in some other way? > Valgrind had to run from program start. So you need to start new xserver to collect valgrind report. So you need to go to console and stop current xserver (sudo stop gdm or sudo stop kdm) > Please note that when my screen is blank, there is no monitor input (ie, > no console visible). Sometimes a CTRL-ALT-DEL allows me to reboot, > sometimes I need to use the infamous REISUB method. > Yes. When X goes bad there isn't much you can do to fix the graphics card state. -- Xorg assert failure: *** glibc detected *** /usr/bin/X: double free or corruption (fasttop): 0x092447a8 *** https://bugs.launchpad.net/bugs/501551 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-x-swat] [Bug 531525] Re: drag and drop action causes immediate logoff
On Thu, Mar 4, 2010 at 3:10 PM, grawcho wrote: > your the master ... whatever you say > > by the way ... i did not have this problem with karmic kernel but ... > your the expert > > if you need aditional data feel free to contact me > Can you collect Xorg.log + dmesg after crash? Also lspci --vvnn and glxinfo would be nice to see. > Jonathan Thomas wrote: >> Sounds like an Xorg crash, which are video driver issues. >> >> ** Package changed: kdebase-workspace (Ubuntu) => xserver-xorg-video-ati >> (Ubuntu) >> >> -- drag and drop action causes immediate logoff https://bugs.launchpad.net/bugs/531525 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati 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 531525] Re: drag and drop action causes immediate logoff
I was hoping that at least dmesg would show some error message after crash. Is there anything after crash in kdm.log? Also there is quite important bug fixes for your card in the latest code. if you want to try newer driver you can get it from https://launchpad.net/~xorg-edgers/+archive/ppa and https://wiki.ubuntu.com/KernelTeam/MainlineBuilds -- drag and drop action causes immediate logoff https://bugs.launchpad.net/bugs/531525 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati 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 391768] Re: nvidia-96-kernel-source fails to build on Karmic
Looks like build failed because there was multiple palces where 185 driver should have been added but is missing in debian control. -- nvidia-96-kernel-source fails to build on Karmic https://bugs.launchpad.net/bugs/391768 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-96 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 391768] Re: nvidia-96-kernel-source fails to build on Karmic
I got the packages build locally if I applied small typo fix for missing comma :) It was simpler than I tough first. --- nvidia-graphics-drivers-96-96.43.13/debian/control 2009-09-08 11:41:25.0 +0300 +++ new/debian/control 2009-09-08 11:39:18.0 +0300 @@ -111,7 +111,7 @@ Recommends: nvidia-glx-96 (>= 96.43.13) Provides: nvidia-kernel-source Conflicts: nvidia-kernel-src, nvidia-kernel-source -Replaces: nvidia-kernel-src, nvidia-180-kernel-source, nvidia-185-kernel-source +Replaces: nvidia-kernel-src, nvidia-180-kernel-source, nvidia-185-kernel-source, nvidia-177-kernel-source, nvidia-173-kernel-source, nvidia-96-kernel-source, nvidia-71-kernel-source, nvidia-kernel-source, nvidia-new-kernel-source, nvidia-legacy-kernel-source, nvidia-kernel-source-envy, -- nvidia-96-kernel-source fails to build on Karmic https://bugs.launchpad.net/bugs/391768 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-96 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 427572] [NEW] ssh X forwarding fails because user doesn't have access to write to /var/run/gdm/
Public bug reported: Binary package hint: xauth When I try to connect to ssh server running in Ubuntu Karmic with X forwarding enabled I get problem that xauth doesn't have access to write to /var/run/gdm/. There is no problem if I'm already logged in locally with same user because authentication file already exits. ProblemType: Bug Architecture: i386 Date: Fri Sep 11 00:56:29 2009 DistroRelease: Ubuntu 9.10 Package: xauth 1:1.0.3-2 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: xauth Uname: Linux 2.6.31-rc9 i686 ** Affects: xauth (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 -- ssh X forwarding fails because user doesn't have access to write to /var/run/gdm/ https://bugs.launchpad.net/bugs/427572 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xauth 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 427572] Re: ssh X forwarding fails because user doesn't have access to write to /var/run/gdm/
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/31621758/Dependencies.txt -- ssh X forwarding fails because user doesn't have access to write to /var/run/gdm/ https://bugs.launchpad.net/bugs/427572 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xauth in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-x-swat] [Bug 427572] Re: ssh X forwarding fails because user doesn't have access to write to /var/run/gdm/
On Fri, Sep 11, 2009 at 3:04 PM, Bryce Harrington wrote: > Hi paniemin, > > > Thanks for including the attached files. Could you also include your > /var/log/Xorg.0.log (or Xorg.0.log.old) from after reproducing the issue? > > [This is an automated message. Apologies if it has reached you > inappropriately; please just reply to this message indicating so.] > > > ** Tags added: needs-xorglog > > ** Changed in: xauth (Ubuntu) > Status: New => Incomplete > > -- > ssh X forwarding fails because user doesn't have access to write to > /var/run/gdm/ > https://bugs.launchpad.net/bugs/427572 > You received this bug notification because you are a direct subscriber > of the bug. > In any case it looks way too open file permisions for /var/run/gdm directories after gdm creates them. They shouldn't be world writable in my option. -- ssh X forwarding fails because user doesn't have access to write to /var/run/gdm/ https://bugs.launchpad.net/bugs/427572 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xauth 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 368187] Re: [HD3650] Kubuntu: garbage screen
Can you try Option "BusType" "PCIE" in xorg.conf? Looks like it is possible bug in your main board AGP driver or AGP bridge. -- [HD3650] Kubuntu: garbage screen https://bugs.launchpad.net/bugs/368187 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati 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 34155] Re: Suspend-To-Ram (S3) doesn't work on Dell Latitude C640
That sounds like bad problem with DFS or UTS. You can disable them in xorg.conf with exa optinos to device context. More details are in man exa to what can be put to xorg.conf. Can you attach dmesg and xorg.log when modeset=1 is passed to kernel? It works but kernel doesn't know about module to handle it before radeon is loaded so you get that warning for working parameter. -- Suspend-To-Ram (S3) doesn't work on Dell Latitude C640 https://bugs.launchpad.net/bugs/34155 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-x-swat] [Bug 368187] Re: [HD3650] Kubuntu: garbage screen
You should increase your BIOS AGP apperture sizes to see if it helps. The PCI error looks like some conflict in how acpi wants to handle card in PCI mode which causes problems because agpgart has already reserved the memory area. (PCI bar is usually defaulting to 256M which is a lot more than 64M agp setting you have.) On Wed, Sep 16, 2009 at 11:02 AM, pvautrin wrote: > I compared again all the logs from hardy, jaunty and karmic and indeed > the only differences are about AGP aperture. > > Even though size and address are detected correctly in dmesg (and > iomem/ioports are in line with WinXP), ... > [0.004000] Checking aperture... > [0.004000] Node 0: aperture @ e000 size 64 MB > [0.480127] agpgart-amd64 :00:00.0: AGP bridge [1106/0204] > [0.483619] agpgart-amd64 :00:00.0: AGP aperture is 64M @ 0xe000 > > ... the resource allocation fails. > Hardy > [ 31.135720] PCI: Using ACPI for IRQ routing > [ 31.135723] PCI: If a device doesn't work, try "pci=routeirq". If it > helps, post a report > [ 31.135735] PCI: Cannot allocate resource region 0 of device > :00:00.0 > Jaunty > [0.470669] PCI: Using ACPI for IRQ routing > [0.470681] pci :00:00.0: BAR 0: can't allocate resource > Karmic > [0.120980] PCI: Using ACPI for IRQ routing > [0.120997] pci :00:00.0: BAR 0: address space collision on of > device [0xe000-0xe3ff] > [0.121059] pci :00:00.0: BAR 0: can't allocate resource > Jaunty with acpi=off option in grub's menu.lst > [0.261932] ACPI: Interpreter disabled. > [0.264037] pci :00:00.0: BAR 0: can't allocate resource > > So this is probably why drm fails later on > [ 30.201734] [drm] Can't use AGP base @0xe000, won't fit > > Pureblood, you have the same drm error, can you check if you also have > the allocation error before that in your dmesg? > > As for the Xorg.0.log, the only error I found is with aperture size > detection (32M instead of 64M) > (II) RADEON(0): [agp] 32768 kB allocated with handle 0x0001 > > I tried Option "GARTSize" "64" but although 64M get allocated, it still > results in a black screen, probably because the issue happens before. > > > So, is this enough information to determine in which part of the code the > bug lies? > If it's really due to xserver-xorg-video-ati (Ubuntu), can we assign the > appropriate people now? > If not, should another bug be opened in the correct bug tracker? Would that > be bugs.freedesktop.org? bugzilla.kernel.org? > > -- > [HD3650] Kubuntu: garbage screen > https://bugs.launchpad.net/bugs/368187 > You received this bug notification because you are a direct subscriber > of the bug. > -- [HD3650] Kubuntu: garbage screen https://bugs.launchpad.net/bugs/368187 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-x-swat] [Bug 423415] Re: Ati driver issues when logging into desktop
It doesn't crash but calls probably exit in r600_dri.so. So some package is not having correct stuff for r600 3D to work. You might find some info from gdm.log or where ever the Xserver stderr is going to. On Wed, Sep 16, 2009 at 2:34 PM, Martin Pitt wrote: > I don't think it helps much, but I started the live system on a computer > with an RV630 (which has this problem), and if I do compiz --replace I > just get: > > Checking for Xgl: not present. > xset q doesn't reveal the location of the log file. Using fallback > /var/log/Xorg.0.log > Detected PCI ID for VGA: > Checking for texture_from_pixmap: not present. > Trying again with indirect rendering: > Checking for texture_from_pixmap: present. > Checking for non power of two support: present. > Checking for Composite extension: present. > Checking screen 1Comparing resolution (1920x1200) to maximum 3D texture > size (4096): Passed. > Checking for Software Rasterizer: Not present. > Checking for nVidia: not present. > Checking for FBConfig: present. > running under gnome seesion, checking for gnomecompat > /usr/bin/compiz: 446: gconftool: not found > adding missing gnomecompat > /usr/bin/compiz: 446: gconftool: not found > can not add gnomecompat, reseting > /usr/bin/compiz: 446: gconftool: not found > Checking for Xgl: not present. > Starting gtk-window-decorator > > and then it crashes. Nothing in Xorg.0.log either :-( > > -- > Ati driver issues when logging into desktop > https://bugs.launchpad.net/bugs/423415 > You received this bug notification because you are subscribed to > xserver-xorg-video-ati in ubuntu. > -- Ati driver issues when logging into desktop https://bugs.launchpad.net/bugs/423415 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati 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 430304] [NEW] Fglrx installer overwrites OSS driver files
Public bug reported: Fglrx installer overwrites mesa and xserer files causing prombles with open source drivers even after removal. Solution would be install fglrx and open drivers to own subdirectories. Loading would either happen using symbolic links or /etc/ld.so.conf.d/ configuration. Also kernel modules should be blacklisted in /etc/modprobe.d/ when switching between drivers. I strongly suggest this for 10.04 release to make it easier to select between drivers for users. ** Affects: fglrx-installer (Ubuntu) Importance: Undecided Status: New -- Fglrx installer overwrites OSS driver files https://bugs.launchpad.net/bugs/430304 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-x-swat] [Bug 368187] Re: [HD3650] Kubuntu: garbage screen
On Tue, Sep 15, 2009 at 3:16 PM, pvautrin wrote: > Thanks Pauli, > I was recommended this option some time ago and indeed it restores display > (forgot to mention it on this thread). > This problem appeared when I changed motherboard. I was able to access > xorg.conf of my installation of Jaunty with Ctrl+Alt+F1. But the issue is > that I don't think it's possible to edit xorg.conf with a live CD, so this > means no fresh install for me. > Moreover, a number of 3D programs/applications fail and I suspect it comes > from this workaround situation. > Do you mean it's a bug in the BIOS? Any reason why Windows is not suffering > from this? > > Windows has driers from manufactures who know how their hardware works (or should know) so windows drivers have good chance of not hitting problems. Problem is not bios but how AGP bridge and GPU work together when reading/writing data to system memory with GPU. > -- > [HD3650] Kubuntu: garbage screen > https://bugs.launchpad.net/bugs/368187 > You received this bug notification because you are a direct subscriber > of the bug. > -- [HD3650] Kubuntu: garbage screen https://bugs.launchpad.net/bugs/368187 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-x-swat] [Bug 419126] Re: [ATI R6xx and above] X fails to start up after mesa+git update - gdm loops after logging in
In #radeon irc channel we found solution for gentoo users with similar problems. It was caused by commit a381287759b2b65e7de9fb35801c781cab016f10 (log: "drm/radeon/kms/r600: use blit for BO moves") in drm-next branch of Airlied's kernele tree. Reverting solves the problem until blit copy code is fixed. On Wed, Sep 16, 2009 at 6:53 PM, Alberto Milone < alberto.mil...@canonical.com> wrote: > The attached debdiff disables r600 > > ** Attachment added: "mesa_7.6.0~git20090817.7c422387-0ubuntu5.debdiff" > > http://launchpadlibrarian.net/31904627/mesa_7.6.0%7Egit20090817.7c422387-0ubuntu5.debdiff > > -- > [ATI R6xx and above] X fails to start up after mesa+git update - gdm loops > after logging in > https://bugs.launchpad.net/bugs/419126 > You received this bug notification because you are subscribed to > xserver-xorg-video-ati in ubuntu. > -- [ATI R6xx and above] X fails to start up after mesa+git update - gdm loops after logging in https://bugs.launchpad.net/bugs/419126 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-x-swat] [Bug 419126] Re: [ATI R6xx and above] X fails to start up after mesa+git update - gdm loops after logging in
On Thu, Sep 17, 2009 at 1:13 PM, Alberto Milone < alberto.mil...@canonical.com> wrote: > Just a clarification on the issue: > > Removing the 3D driver (/usr/lib/dri/r600_dri.so) is a valid workaround > and the debdiff that I attached in comment 132 prevents mesa from > building that driver. > > We are still looking into the possibility to get a working 3D driver for > r600 in time for Karmic. I can't promise anything though. > > You should co-operate more with upstream when you try to get still in development code to work. It would be nice to know what kernel modules code you are using and what extra patches etc. People will be coming to complain to upstream anyway so fixing bugs is easier there if there is more knowledge what you are doing. Did you try to revert the patch that hooked in blit to kernel copy operation? It is known to be buggy in some hw still so better not to ship that kind of change in Ubuntu until most of problems with blit code is fixed. -- [ATI R6xx and above] X fails to start up after mesa+git update - gdm loops after logging in https://bugs.launchpad.net/bugs/419126 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-x-swat] [Bug 427101] Re: [Karmic] Xorg crash after login. Returns to gdm which then hangs.
On Fri, Sep 18, 2009 at 5:17 AM, bwat47 wrote: > Installed alpha 6, I also get this problem. My card is a mobility 2600. > Login just keeps looping. ctrl alt f1 does not work. How can I change > the xorg.conf if I can't get to the console? > > You can add text to kernel parameter list in grub to boot to console only mode. -- [Karmic] Xorg crash after login. Returns to gdm which then hangs. https://bugs.launchpad.net/bugs/427101 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-x-swat] [Bug 373968] Re: [RV280] glyph corruption and occasional X lockup on radeon 9200 se
On Fri, Sep 18, 2009 at 11:02 AM, fuzzyBSc < benjamincarl...@soundadvice.id.au> wrote: > Just a quick update. > > I am still running Jaunty at the present time. I'm pretty busy at the > current moment and haven't had time to upgrade to Karmic. I have been > working through the AGP modes in xorg.conf. I am up to 4 (tried 1 & 2, > but not 8). This has been more stable for me, which is to say that it > has been failing just as often but not as badly. At settings of 1 and 2 > the whole machine would be unusable until a restart. I could ssh in > (very slowly) and issue the reboot command, but nothing else helped. > With a setting of four I get the same kind of lockups, but occasionally > can Ctrl+Alt+F1 my way out and restart gdm. If that doesn't work (often > the keyboard is completely unresponsive in this case, ie no numlock > response) I have been pretty reliably been able to ssh in. A restart of > gdm has been all that I have required to get back up and running at AGP > mode 4. > > This suggests to me that 4 may be the right mode, but that an underlying > problem still exists with the driver. I'll have a go at Karmic when I > get a chance. Sorry about the delays. > > > You problem is that you have enabled DFS (DownloadFromScreen) which is not stable in AGP mode. You can try to disable UTS/DFS in xorg.conf device section. Details can be found from exa man page. -- [RV280] glyph corruption and occasional X lockup on radeon 9200 se https://bugs.launchpad.net/bugs/373968 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati 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 500105] Re: x freezes in ubuntu 9.04 on using OOo
Few things that could help in problem. You need to add configurations to /etx/X11/xorg.conf to "Configured Video Device" section. You can find more etailed info what can be put there using "man radeon" in console. 1. Disabling DRI (Option "DRI" "off") 2. Disable AGP by enabling PCI mode (Option "BusType" "PCI") 3. Change AGP speed to 4x (Option "AGPMode" "4") 4. Using old XAA acceleration (Option "AccelMethod" "XAA") 5. Have ssh connection to system when it freezes to collect information from dmesg, xorg.log and openoffice/xorg trace logs. ssh connection recuires you to install ssh server which allows secure remote login to your machine. More details about ssh can be found from https://help.ubuntu.com/9.04/serverguide/C/openssh-server.html and strace info https://wiki.ubuntu.com/Strace. You most likely want to write the strace output directly to a file in your second machine which won't freeze. 6. Trying to stream the kernel log to another machine in lan using net console. This might reveal the error message that you can't red locally. But I have small doubt that there might not be anything to see. But if you want to try here is link to the kernel parameter documentation: http://www.mjmwired.net/kernel/Documentation/networking/netconsole.txt I think that some of these freeze problems has been fixed in Karmic too. If you don't want to try the upgrade you can use newer graphics driver from https://launchpad.net/~xorg- edgers/+archive/ppa?field.series_filter=jaunty -- x freezes in ubuntu 9.04 on using OOo https://bugs.launchpad.net/bugs/500105 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-x-swat] [Bug 96991] Re: (Needs radeon-rewrite) 3D stuff breaks with Compiz: Redirected Direct Rendering is needed in DRI
This is different problem. This looks a lot like rendering bug that should be reported in new bug report (unless it is already reported in some newer bug report) On Fri, Dec 25, 2009 at 1:56 PM, Reynaldo Matos Hortensi < lasanhadeberinj...@gmail.com> wrote: > Hi Extender, > I have tried with xorg-edger drivers and radeon.modset=1 kernel > parameter... everything worked fine but googleearth (ATI Radeon Xpress 200, > chipset RS482). > Glxgears worked fine (I can move the glxgears window without artefacts on > screen). > Googleearth have produced artefacts (see attachment). > I will be back with number for glxgears and gtkperf. > > -- (Needs radeon-rewrite) 3D stuff breaks with Compiz: Redirected Direct Rendering is needed in DRI https://bugs.launchpad.net/bugs/96991 You received this bug notification because you are a member of Ubuntu-X, which is the registrant for xf86-video-intel. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-x-swat] [Bug 475428] Re: font corruption with xserver-xorg-video-ati driver
This looks like download from screen bug. You can disable the feature with Option "EXANoDownloadFromScreen" "on" in xorg.conf On Thu, Dec 24, 2009 at 12:50 AM, hansvw wrote: > Experienced the same issue on an older radeon card (radeon 8500) > following an automated update of xserver-xorg-video-radeon (update > manager suggestion). Solved the issue by adding some sections to the > auto-configured xorg.conf. Notably changing to the older "XAA" > AccelMethod appears to fix the issue: > > Section "Device" >Identifier "Radeon 8500" >Driver "ati" >BusID "PCI:1:0:0" >Option "XAANoOffscreenPixmaps" >Option "AccelMethod" "XAA" >Option "EnablePageFlip" "true" >Option "TripleBuffer" "true" > EndSection > > Section "Monitor" >Identifier "Configured Monitor" > EndSection > > Section "Screen" >Identifier "Default Screen" >Monitor "Configured Monitor" >Device "Radeon 8500" > EndSection > > -- > font corruption with xserver-xorg-video-ati driver > https://bugs.launchpad.net/bugs/475428 > You received this bug notification because you are subscribed to > xserver-xorg-video-ati in ubuntu. > -- font corruption with xserver-xorg-video-ati driver https://bugs.launchpad.net/bugs/475428 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati 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 531525] Re: drag and drop action causes immediate logoff
kkd.log is showing that there is internal problem in mesa dri driver that it emits more data to command stream that it should. Then kernel is rejecting the command stream which causes X to crash. There is some bug in mesa radeon driver. I thunk that crash won't happen if you disable kwin composite. If that guess is right you could try to find which kwin feature is causing the problem by disabling them one by one. If you have same problem still with 2.6.33 kernel and mesa 7.8 I think this bug report should be moved to https://bugs.freedesktop.org (mesa and Drivers/r128). In fdo bug tracker you could get some devs with old enough hw to check. After bug report you could join irc channel #rad...@freenode and chat with Airlied if he would need more info to reproduce the problem. -- drag and drop action causes immediate logoff https://bugs.launchpad.net/bugs/531525 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-x-swat] [Bug 533784] Re: [RV280 Radeon 9200 SE] OpenGL Fullscreen hangs/crashes Xorg.
Here is 2 bugs reported in one bug report! First one is GPU hang which is hard to fix. The best bet is to try newer driver version if problem is fixed there. https://launchpad.net/~xorg-edgers/+archive/ppa and https://wiki.ubuntu.com/KernelTeam/MainlineBuilds are providing the the latest version of the driver. Second is memory allocation failure that is fixed in Linus' 2.6 git tree with commits: 7a9f0dd9c49425e2b0e39ada4757bc7a38c84873 drm: Add generic multipart buffer. b4fe945405e477cded91772b4fec854705443dd5 drm/radeon: Fix memory allocation failures in the preKMS command stream checking. 55a5cb5d594c18b3147a2288b00ea359c1a38cf8 drm/radeon: Fix printf type warning in 64bit system. Second problem only affects UMS code path. -- [RV280 Radeon 9200 SE] OpenGL Fullscreen hangs/crashes Xorg. https://bugs.launchpad.net/bugs/533784 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-x-swat] [Bug 543245] Re: Screen's graphics messed up on radeon 9200se (with and without compiz..)
On Sun, Mar 21, 2010 at 9:56 PM, Arkashkin wrote: > Ok, the bug still exist, I have opened th Appearance dialog and it look like > this: > http://www.ubuntu-pics.de/bild/48223/screenshot_C5T17G.png > Appearance dialog caches the old broken images and you need to force the recreation of images with fixed driver. This issue should be fixed in 2.6.33 drm (included in 2.6.32-16). -- Screen's graphics messed up on radeon 9200se (with and without compiz) https://bugs.launchpad.net/bugs/543245 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati 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 547187] Re: Small graphics performance
Bug is that kernel module is not loaded before xstarts. -- Small graphics performance https://bugs.launchpad.net/bugs/547187 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati 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 429003] [NEW] [karmic] Xorg (and anything GLX) crashes on startup
Public bug reported: As of after updates at 2009-09-13 ca. 16:00, Xorg and anything using GLX (eg. glxinfo) crashes on startup. The only thing that seems to have been changed then is the upgrade of libc6 to 2.10.1-0ubuntu11. Log of crashing Xorg run is attached. The corresponding gdb backtrace is: $ gdb /usr/bin/Xorg CoreDump ... (gdb) bt #0 0x278da3c0 in ?? () #1 0x00289d8d in *__GI___backtrace (array=0xbfdab960, size=32) at ../sysdeps/i386/backtrace.c:121 #2 0x08133d1b in xorg_backtrace () at ../../os/backtrace.c:39 #3 0x080c7b95 in xf86SigHandler (signo=11) at ../../../../hw/xfree86/common/xf86Events.c:387 #4 #5 *__GI_strtol_l_internal (nptr=0xbfdac02d "001 GLX", endptr=0xbfdac028, base=10, group=0, loc=0x0) at strtol_l.c:246 #6 0x001d6667 in *__GI_strtol (nptr=0xbfdac02d "001 GLX", endptr=0xbfdac028, base=10) at strtol.c:110 #7 0x0807355e in RegisterExtensionNames (extEntry=0x8387690) at ../../dix/registry.c:168 #8 0x0809e33a in AddExtension (name=0x635ebc "GLX", NumEvents=17, NumErrors=12, MainProc=0x6135f0, SwappedMainProc=0, CloseDownProc=0x613430, MinorOpcodeProc=0x809da10 ) at ../../dix/extension.c:145 #9 0x006132f5 in ?? () from /usr/lib/xorg/modules/extensions//libglx.so #10 0x00635ebc in ?? () from /usr/lib/xorg/modules/extensions//libglx.so #11 0x0011 in ?? () #12 0x000c in ?? () #13 0x006135f0 in ?? () from /usr/lib/xorg/modules/extensions//libglx.so #14 0x00613560 in ?? () from /usr/lib/xorg/modules/extensions//libglx.so #15 0x00613430 in ?? () from /usr/lib/xorg/modules/extensions//libglx.so #16 0x0809da10 in ?? () at ../../dix/extension.c:219 #17 0x080ec7c5 in InitExtensions (argc=4, argv=0xbfdac2d4) at ../../../../mi/miinitext.c:551 #18 0x080722b8 in main (argc=4, argv=0xbfdac2d4, envp=0xbfdac2e8) at ../../dix/main.c:319 Glxinfo backtrace looks like this: $ unset DISPLAY $ gdb glxinfo ... (gdb) run Starting program: /usr/bin/glxinfo Program received signal SIGSEGV, Segmentation fault. *__GI_strtol_l_internal (nptr=0xb57a "\t26782\n", endptr=0x0, base=0, group=0, loc=0x0) at strtol_l.c:246 246 strtol_l.c: No such file or directory. in strtol_l.c (gdb) bt #0 *__GI_strtol_l_internal (nptr=0xb57a "\t26828\n", endptr=0x0, base=0, group=0, loc=0x0) at strtol_l.c:246 #1 0x0045b6b6 in *__GI___strtol_internal (nptr=0xb57a "\t26828\n", endptr=0x0, base=0, group=0) at strtol.c:99 #2 0x006bac15 in ?? () from /usr/lib/libGL.so.1 #3 0xb57a in ?? () #4 0x in ?? () Note that it crashes at a very early stage, not probably even contacting X server yet (since DISPLAY is unset). Packages: ii libc6 2.10.1-0ubuntu11 GNU C Library: Shared libraries ii libc6-dbg 2.10.1-0ubuntu11 GNU C Library: detached debugging symbols ii libc6-dev 2.10.1-0ubuntu11 GNU C Library: Development Libraries and Hea ii libc6-i6862.10.1-0ubuntu11 GNU C Library: Shared libraries [i686 optimi ii libgl1-mesa-glx 7.6.0~git20090817.7c422387-0ubuntu3A free implementation of the OpenGL API -- G ii mesa-utils 7.6.0~git20090817.7c422387-0ubuntu3Miscellaneous Mesa GL utilities ii mesa-utils-dbgsym 7.6.0~git20090817.7c422387-0ubuntu3debug symbols for package mesa-utils ii nvidia-185-kernel-source 185.18.36-0ubuntu2 NVIDIA binary kernel module source ii nvidia-185-libvdpau 185.18.36-0ubuntu2 Video Decode and Presentation API for Unix ii nvidia-glx-185185.18.36-0ubuntu2 NVIDIA binary Xorg driver ii nvidia-settings 180.25-0ubuntu1 Tool of configuring the NVIDIA graphics driv ii rss-glx 0.9.0-2ubuntu3 Really Slick Screensavers GLX Port ii xorg-docs-core1:1.4-5 Core documentation for the X.org X Window Sy ii xserver-xorg-core 2:1.6.3-1ubuntu6 Xorg X server - core server ii xserver-xorg-core-dbg 2:1.6.3-1ubuntu6 Xorg - the X.Org X server (debugging symbols ** Affects: nvidia-graphics-drivers-180 (Ubuntu) Importance: Undecided Status: New -- [karmic] Xorg (and anything GLX) crashes on startup https://bugs.launchpad.net/bugs/429003 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-180 in ubuntu. ___
[Ubuntu-x-swat] [Bug 429003] Re: [karmic] Xorg (and anything GLX) crashes on startup
** Attachment added: "Xorg log file from a crashed run" http://launchpadlibrarian.net/31755284/Xorg.log -- [karmic] Xorg (and anything GLX) crashes on startup https://bugs.launchpad.net/bugs/429003 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-180 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 429003] Re: [karmic] Xorg (and anything GLX) crashes on startup
Some possibly similar bugs were filed recently: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/429005 https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/429002 https://bugs.launchpad.net/ubuntu/+bug/428993 https://bugs.launchpad.net/ubuntu/+source/rss-glx/+bug/428979 https://bugs.launchpad.net/ubuntu/+source/rss-glx/+bug/428975 https://bugs.launchpad.net/ubuntu/+source/xscreensaver/+bug/428974 https://bugs.launchpad.net/ubuntu/+source/xscreensaver/+bug/428973 https://bugs.launchpad.net/ubuntu/+source/rss-glx/+bug/428972 -- [karmic] Xorg (and anything GLX) crashes on startup https://bugs.launchpad.net/bugs/429003 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-180 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 429003] Re: [karmic] Xorg (and anything GLX) crashes on startup
Switching to the "nv" driver, and uninstalling nvidia-glx-185 makes glxinfo and Xorg not crash any more, so it seems this problem is localized to the non-free drivers. -- [karmic] Xorg (and anything GLX) crashes on startup https://bugs.launchpad.net/bugs/429003 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-180 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 429003] Re: [karmic] Xorg (and anything GLX) crashes on startup
Also, as expected, downgrading libc6 and libc6-i686 to 2.10.1-0ubuntu9 made glxinfo not crash when nvidia-glx-185 is installed. Upgrading the two packages to 2.10.1-0ubuntu11 made the crash reappear, and removing nvidia-glx-185 to disappear again. So, this is some kind of mismatch between the new libc packages and Nvidia's drivers. -- [karmic] Xorg (and anything GLX) crashes on startup https://bugs.launchpad.net/bugs/429003 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-180 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 429005] Re: Xorg crashed with SIGSEGV in strtol()
*** This bug is a duplicate of bug 429003 *** https://bugs.launchpad.net/bugs/429003 ** This bug has been marked a duplicate of bug 429003 [karmic] Xorg (and anything GLX) crashes on startup -- Xorg crashed with SIGSEGV in strtol() https://bugs.launchpad.net/bugs/429005 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 429633] Re: X11 fails to start with nvidia 185
*** This bug is a duplicate of bug 429003 *** https://bugs.launchpad.net/bugs/429003 ** This bug has been marked a duplicate of bug 429003 [karmic] Xorg (and anything GLX) crashes on startup -- X11 fails to start with nvidia 185 https://bugs.launchpad.net/bugs/429633 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-180 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 429480] Re: X server can't start with the NVIDIA driver installed
*** This bug is a duplicate of bug 429003 *** https://bugs.launchpad.net/bugs/429003 ** This bug has been marked a duplicate of bug 429003 [karmic] Xorg (and anything GLX) crashes on startup -- X server can't start with the NVIDIA driver installed https://bugs.launchpad.net/bugs/429480 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 429003] Re: [karmic] Xorg (and anything GLX) crashes on startup
@Matthias Klose:
I think it is well possible to test this without any Nvidia hardware:
you probably can just do
$ dpkg-deb -x nvidia-glx-185_185.18.36-0ubuntu2_i386.deb xxx
$ LD_LIBRARY_PATH=$PWD/xxx/usr/lib glxinfo
and observe the crash -- it occurs on shared library load, very likely
before Nvidia's GL library even tries to access the HW. Consider also:
$ cat test.c
int main() { return 0; }
$ gcc -o test test.c -lGL
$ LD_LIBRARY_PATH=$PWD/xxx/usr/lib ./test
Segmentation fault (core dumped)
It crashes before reaching main(). Also, something strange is going on
here:
$ LD_DEBUG=all LD_LIBRARY_PATH=$PWD/xxx/usr/lib ./test
[clip]
6922: symbol=pthread_key_create; lookup in
file=/usr/lib/libXdmcp.so.6 [0]
6922: ./test: error: symbol lookup error: undefined symbol:
pthread_key_create (fatal)
Segmentation fault (core dumped)
I don't know (as of now) how to debug the .init section code of a shared
library, so I'll have to stop here.
--
[karmic] Xorg (and anything GLX) crashes on startup
https://bugs.launchpad.net/bugs/429003
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-180 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 429873] Re: crash X at start
Possibly a duplicate of https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/429003/ -- crash X at start https://bugs.launchpad.net/bugs/429873 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-180 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 437607] [NEW] xorg takes 100% cpu -- but only on first login
Public bug reported: Binary package hint: xorg On Ubuntu Karmic & Nvidia's non-free drivers: after logging in, Xorg takes 100% CPU. No application seems to be redrawing anything (no firefox. Xorg is also the only large CPU user). Apart from the large CPU usage, everything seems to be working normally. The curious thing is that the situation is fixed by logging out (back to gdm), and then logging in again. Then, Xorg's CPU usage is back to normal. ProblemType: Bug Architecture: i386 Date: Sun Sep 27 14:41:24 2009 DistroRelease: Ubuntu 9.10 MachineType: System Manufacturer System Name NonfreeKernelModules: nvidia Package: xorg 1:7.4+3ubuntu5 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-11-generic root=UUID=1333b097-1cf5-44a3-bf1b-13c71021ecf7 ro quiet splash ProcEnviron: LANGUAGE=fi_FI.UTF-8 LC_COLLATE=C PATH=(custom, user) LANG=fi_FI.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-11.36-generic RelatedPackageVersions: xserver-xorg 1:7.4+3ubuntu5 libgl1-mesa-glx 7.6.0~git20090817.7c422387-0ubuntu5 libdrm2 2.4.13-1ubuntu1 xserver-xorg-video-intel 2:2.8.1-1ubuntu2 xserver-xorg-video-ati 1:6.12.99+git20090825.fc74e119-0ubuntu2 SourcePackage: xorg Uname: Linux 2.6.31-11-generic i686 dmi.bios.date: 04/08/2004 dmi.bios.vendor: Award Software, Inc. dmi.bios.version: ASUS A7V600-X ACPI BIOS Revision 1003 dmi.board.name: A7V600-X dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: REV 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 7 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAwardSoftware,Inc.:bvrASUSA7V600-XACPIBIOSRevision1003:bd04/08/2004:svnSystemManufacturer:pnSystemName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnA7V600-X:rvrREV1.xx:cvnChassisManufacture:ct7:cvrChassisVersion: dmi.product.name: System Name dmi.product.version: System Version dmi.sys.vendor: System Manufacturer fglrx: Not loaded system: distro: Ubuntu architecture: i686kernel: 2.6.31-11-generic ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 -- xorg takes 100% cpu -- but only on first login https://bugs.launchpad.net/bugs/437607 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 437607] Re: xorg takes 100% cpu -- but only on first login
** Attachment added: "BootDmesg.txt" http://launchpadlibrarian.net/32518230/BootDmesg.txt ** Attachment added: "CurrentDmesg.txt" http://launchpadlibrarian.net/32518232/CurrentDmesg.txt ** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/32518233/Dependencies.txt ** Attachment added: "Lspci.txt" http://launchpadlibrarian.net/32518234/Lspci.txt ** Attachment added: "Lsusb.txt" http://launchpadlibrarian.net/32518235/Lsusb.txt ** Attachment added: "PciDisplay.txt" http://launchpadlibrarian.net/32518236/PciDisplay.txt ** Attachment added: "ProcCpuinfo.txt" http://launchpadlibrarian.net/32518237/ProcCpuinfo.txt ** Attachment added: "ProcInterrupts.txt" http://launchpadlibrarian.net/32518238/ProcInterrupts.txt ** Attachment added: "ProcModules.txt" http://launchpadlibrarian.net/32518239/ProcModules.txt ** Attachment added: "UdevDb.txt" http://launchpadlibrarian.net/32518240/UdevDb.txt ** Attachment added: "UdevLog.txt" http://launchpadlibrarian.net/32518241/UdevLog.txt ** Attachment added: "XorgConf.txt" http://launchpadlibrarian.net/32518242/XorgConf.txt ** Attachment added: "XorgLog.txt" http://launchpadlibrarian.net/32518243/XorgLog.txt ** Attachment added: "XorgLogOld.txt" http://launchpadlibrarian.net/32518244/XorgLogOld.txt ** Attachment added: "Xrandr.txt" http://launchpadlibrarian.net/32518245/Xrandr.txt ** Attachment added: "glxinfo.txt" http://launchpadlibrarian.net/32518246/glxinfo.txt ** Attachment added: "setxkbmap.txt" http://launchpadlibrarian.net/32518247/setxkbmap.txt ** Attachment added: "xdpyinfo.txt" http://launchpadlibrarian.net/32518248/xdpyinfo.txt ** Attachment added: "xkbcomp.txt" http://launchpadlibrarian.net/32518249/xkbcomp.txt -- xorg takes 100% cpu -- but only on first login https://bugs.launchpad.net/bugs/437607 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 437607] Re: xorg takes 100% cpu -- but only on first login
More information: when Xorg is consuming CPU on the first login, when I switch to another VT, the VT switches immediately back to X. I also cannot use the "Switch to another user" feature. Like so: 1. Ctrl+Alt+SysRQ+R (release keyboard) 2. Alt+F1 (switch VT) 3. In a fraction of a second, VT switches back to X. VT1 only flashes by. This does not happen on the second login: there, VT stays at VT1 and does not switch back by itself. Is it possible that part of Xorg is running in some busy-loop, constantly switching the VT? I cannot easily attach a gdb to Xorg due to the VT problem. I may try setting up some ssh setup later on. -- xorg takes 100% cpu -- but only on first login https://bugs.launchpad.net/bugs/437607 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 438398] [NEW] DKMS build fails, but package upgrade still successful
Public bug reported: The nvidia-185-kernel-source (185.18.36-0ubuntu3) package upgrade succeeds, even though the DKMS build fails. I believe the package should not be marked as configured in this case, especially as otherwise the user will notice the problem only on the next boot. Example failure case (due to DKMS bug #438393): - Configuring: nvidia-185-kernel-source (185.18.36-0ubuntu3) ... Removing all DKMS Modules Done. Adding Module to DKMS build system driver version= 185.18.36 Doing initial module build Error! Bad return status for module build on kernel: 2.6.31-11-generic (i686) Consult the make.log in the build directory /var/lib/dkms/nvidia/185.18.36/build/ for more information. Installing initial module Error! Could not locate nvidia.ko for module nvidia in the DKMS tree. You must run a dkms build for kernel 2.6.31-11-generic (i686) first. Done. - Extract from make.log - DKMS make.log for nvidia-185.18.36 for kernel 2.6.31-11-generic (i686) ti 29.9.2009 00.03.29 +0300 The C compiler '/home/pauli/bin/gcc-cached' does not appear to be able to create executables. Please make sure you have your Linux distribution's libc development package installed and that '/home/pauli/bin/gcc-cached' is a valid C compiler name. *** Failed CC sanity check. Bailing out! *** make: *** [select_makefile] Virhe 1 - ** Affects: nvidia-graphics-drivers-180 (Ubuntu) Importance: Undecided Status: New -- DKMS build fails, but package upgrade still successful https://bugs.launchpad.net/bugs/438398 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-180 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 439138] Re: [karmic, intel] Xorg 100% CPU utilization after startup on SSDs
Same bug: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/437607 -- [karmic, intel] Xorg 100% CPU utilization after startup on SSDs https://bugs.launchpad.net/bugs/439138 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 437607] Re: xorg takes 100% cpu -- but only on first login
*** This bug is a duplicate of bug 439138 *** https://bugs.launchpad.net/bugs/439138 ** This bug has been marked a duplicate of bug 439138 [karmic, intel] Xorg 100% CPU utilization after startup on SSDs -- xorg takes 100% cpu -- but only on first login https://bugs.launchpad.net/bugs/437607 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 439138] Re: [karmic, intel] Xorg 100% CPU utilization after startup on SSDs
That is, happens also here, with Nvidia proprietary drivers on Karmic, GeForce 7600 GS. No SSD drives. -- [karmic, intel] Xorg 100% CPU utilization after startup on SSDs https://bugs.launchpad.net/bugs/439138 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 439138] Re: [karmic] Xorg 100% CPU utilization -- only after first login
** Summary changed: - [karmic] Xorg 100% CPU utilization after startup on SSDs + [karmic] Xorg 100% CPU utilization -- only after first login -- [karmic] Xorg 100% CPU utilization -- only after first login https://bugs.launchpad.net/bugs/439138 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 429003] Re: [karmic] Xorg (and anything GLX) crashes on startup
@srikumar: That doesn't sound like it's the same bug. For instance, I see this bug any more. There can be more than one cause for why X would crash on startup, and this one has most likely been fixed. Please file a separate bug report, thanks! ** Changed in: eglibc (Ubuntu Karmic) Status: Incomplete => Fix Released -- [karmic] Xorg (and anything GLX) crashes on startup https://bugs.launchpad.net/bugs/429003 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-180 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 440396] Re: Xorg cpu utilization high on every other startup
Same as this? https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/439138 -- Xorg cpu utilization high on every other startup https://bugs.launchpad.net/bugs/440396 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 439138] Re: [karmic] Xorg 100% CPU utilization -- only after first login
The behavior of VT switching points toward a low-level bug, rather than an application bug (cf. #437607): 0. After first login: X consumes 100% CPU 1. Alt+SysRQ+R (release KB, the VT switching seems to be disabled in default configuration?) 2. Alt+F1 (switch to VT1) 3. Something (Xorg?) causes the VT to switch immediately back to VT7 3b. The "Switch user" functionality in Gnome doesn't work either: VT switches always back to VT7 4. Log out from X, log then back in 5. X cpu consumption low 6. Alt+F1 7. Now the VT does not switch immediately back 7b. Also "Switch user" functionality works again. It could be useful if the past/future me-tooers verified if they see this same behavior vs. VT switching. There may be multiple causes for 100% cpu consumption, but to me the above seems too much of a coincidence to be accidental. -- [karmic] Xorg 100% CPU utilization -- only after first login https://bugs.launchpad.net/bugs/439138 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 438398] Re: DKMS build fails, but package upgrade still successful
Ideally, this known and safe cause of build failure could be distinguished from real build failures. Does DKMS check that the headers are actually available (I think it does not)? In any case this seems to require some special handling, as nvidia package control file probably cannot instruct dpkg to take care of unpacking updated header files sufficiently early. -- DKMS build fails, but package upgrade still successful https://bugs.launchpad.net/bugs/438398 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-180 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 573334] Re: EQ overflowing and backtrace from xorg
Confirm -- happened several times with natty: [ 24739.679] [mi] EQ overflowing. The server is probably stuck in an infinite loop. [ 24739.679] Backtrace: [ 24739.728] 0: /usr/bin/X (xorg_backtrace+0x26) [0x4a2e56] [ 24739.728] 1: /usr/bin/X (mieqEnqueue+0x1f4) [0x4a2124] [ 24739.728] 2: /usr/bin/X (xf86PostMotionEventM+0x97) [0x47d3d7] [ 24739.729] 3: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f86e30da000+0x5bfb) [0x7f86e30dfbfb] [ 24739.729] 4: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f86e30da000+0x65ed) [0x7f86e30e05ed] [ 24739.729] 5: /usr/bin/X (0x40+0x6c347) [0x46c347] [ 24739.729] 6: /usr/bin/X (0x40+0x12768e) [0x52768e] [ 24739.729] 7: /lib/libpthread.so.0 (0x7f86e8f3d000+0xfc80) [0x7f86e8f4cc80] [ 24739.729] 8: /lib/libc.so.6 (ioctl+0x7) [0x7f86e7f33377] [ 24739.730] 9: /lib/libdrm.so.2 (drmIoctl+0x28) [0x7f86e64cd058] [ 24739.730] 10: /lib/libdrm.so.2 (drmCommandWrite+0x1b) [0x7f86e64cf30b] [ 24739.730] 11: /lib/libdrm_nouveau.so.1 (0x7f86e569e000+0x2b87) [0x7f86e56a0b87] [ 24739.730] 12: /lib/libdrm_nouveau.so.1 (nouveau_bo_map_range+0xfe) [0x7f86e56a119e] [ 24739.730] 13: /usr/lib/xorg/modules/drivers/nouveau_drv.so (0x7f86e58a4000+0x5bbe) [0x7f86e58a9bbe] [ 24739.730] 14: /usr/lib/xorg/modules/libexa.so (0x7f86e4a21000+0x9958) [0x7f86e4a2a958] [ 24739.731] 15: /usr/bin/X (0x40+0xe16a0) [0x4e16a0] [ 24739.731] 16: /usr/bin/X (0x40+0x2ab81) [0x42ab81] [ 24739.731] 17: /usr/bin/X (0x40+0x2dfe1) [0x42dfe1] [ 24739.731] 18: /usr/bin/X (0x40+0x21bbe) [0x421bbe] [ 24739.731] 19: /lib/libc.so.6 (__libc_start_main+0xfe) [0x7f86e7e74efe] [ 24739.731] 20: /usr/bin/X (0x40+0x21769) [0x421769] -- 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/573334 Title: EQ overflowing and backtrace from xorg ___ 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 778083] Re: Switching workspaces does not always redraw everything necessary
I'm seeing the same thing, on Intel 945GME. Happens when using Metacity, but not when using Compiz. -- 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/778083 Title: Switching workspaces does not always redraw everything necessary ___ 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 778083] Re: Switching workspaces does not always redraw everything necessary
** Changed in: xorg-server (Ubuntu) Status: New => Incomplete ** Changed in: xorg-server (Ubuntu) Status: Incomplete => New ** Changed in: xorg-server (Ubuntu) Status: New => Confirmed -- 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/778083 Title: Switching workspaces does not always redraw everything necessary ___ 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 718032] Re: Flash fullscreen mode can cause X to freeze the display
At least in my case upgrading kernel to "2.6.37-020637rc2-generic" from mainline did not do any good. Fullscreen flash still freezes allways but sound works ok. I have also tried all the /etc/adobe/ and export env-variable stuff described in other threads -- no help. -- 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/718032 Title: Flash fullscreen mode can cause X to freeze the display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/718032/+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 321041] Re: gnome-settings-daemon crashed with signal 5 in xkl_process_error()
I think i hit this same bug while setting mixer input volume and then closed the setting dialog, 10.10 up-to-date, netbook remix, i386 -- gnome-settings-daemon crashed with signal 5 in xkl_process_error() https://bugs.launchpad.net/bugs/321041 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
