[Ubuntu-x-swat] [Bug 1038615] Re: Wacom Intuos 5 button touch moves the cursor to the top left corner
Launchpad has imported 5 comments from the remote bug at https://bugs.freedesktop.org/show_bug.cgi?id=54250. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2012-08-30T08:00:37+00:00 Timo Aaltonen wrote: I get extra lines with gimp leading to the top-left corner when I touch the buttons on my Intuos5 S while drawing. No need to touch the button down, just showing the finger seems to be enough.. Happens with 1.12.99.905 server, kernel 3.5, -wacom 0.16+git9f32b03. Reply at: https://bugs.launchpad.net/xf86-input- wacom/+bug/1038615/comments/11 On 2012-08-30T08:13:49+00:00 Timo Aaltonen wrote: by silent I mean the cursor doesn't seem to jump there, but gimp shows these streaks.. xev shows this even when that happens: KeymapNotify event, serial 42, synthetic NO, window 0x0, keys: 4294967235 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Reply at: https://bugs.launchpad.net/xf86-input- wacom/+bug/1038615/comments/12 On 2012-09-13T12:36:00+00:00 Timo Aaltonen wrote: still the same with kernel 3.6-rc5, -wacom 0.17. Reply at: https://bugs.launchpad.net/xf86-input- wacom/+bug/1038615/comments/14 On 2012-09-13T22:59:04+00:00 Killertofu wrote: After some poking around, I think I've tracked down the cause of this behavior. When touching (but not pressing) a button, the kernel driver mostly ignores the hardware event it receives. The out-of-prox logic is triggered, and we send an event indicating the pad has left proximity. The problem is that since the pad never *entered* proximity, it can leave the X driver a little confused. When a new packet comes in from the kernel, the X driver uses the serial number to find the appropriate channel to store event data in. It then updates the most-recent information in that channel with the packet data and processes the result as an event. An excess out-of-prox event starts from an empty state, causing the driver to ask the kernel for the tool that is currently in proximity. If it finds something, an empty event is sent for that tool, causing a momentary jump to the top-left corner. There are two ways I see to fix this bug: a) have the kernel send an (empty) in-prox event for button touches so the X driver doesn't get confused, b) have the X driver ignore out-of-prox events for already out-of-prox tools. Reply at: https://bugs.launchpad.net/xf86-input- wacom/+bug/1038615/comments/16 On 2012-09-14T04:57:57+00:00 Timo Aaltonen wrote: I could certainly use a patch for the X driver, faster to get it accepted as a stable update :) Don't mind if the kernel would get fixed later. Reply at: https://bugs.launchpad.net/xf86-input- wacom/+bug/1038615/comments/17 ** Changed in: xf86-input-wacom Status: Unknown = In Progress ** Changed in: xf86-input-wacom Importance: Unknown = Medium -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xf86-input-wacom in Ubuntu. https://bugs.launchpad.net/bugs/1038615 Title: Wacom Intuos 5 button touch moves the cursor to the top left corner To manage notifications about this bug go to: https://bugs.launchpad.net/xf86-input-wacom/+bug/1038615/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1037411] Re: [regression][DRI] SubBuffer rendering is much slower in compiz 0.9.8.0 than it was in 0.9.7
Launchpad has imported 8 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=54763.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.
On 2012-09-11T09:24:50+00:00 Daniel van Vugt wrote:
I call glCopyPixels a couple of times briefly on startup and then never
again. The problem is that doing this makes all subsequent rendering
much slower. If I never call glCopyPixels on startup then rendering
remains fast thereafter.
It seems glCopyPixels is modifying the context in a way that permanently
cripples later operations. The only possible cause I can see so far is:
src/mesa/main/drawpix.c: _mesa_CopyPixels:
/* We're not using the current vertex program, and the driver may install
* it's own. Note: this may dirty some state.
*/
_mesa_set_vp_override(ctx, GL_TRUE);
This seems to set a flag in the ctx which is never cleared.
Using Mesa 8.0.2 in Ubuntu 12.04
Reply at: https://bugs.launchpad.net/compiz/+bug/1037411/comments/16
On 2012-09-11T10:10:48+00:00 Daniel van Vugt wrote:
I am using Intel Sandy Bridge HD 2000 by the way. I believe that means
i965.
Reply at: https://bugs.launchpad.net/compiz/+bug/1037411/comments/18
On 2012-09-11T13:32:24+00:00 Michel-daenzer wrote:
(In reply to comment #2)
I call glCopyPixels a couple of times briefly on startup and then never again.
The problem is that doing this makes all subsequent rendering much slower. If
I
never call glCopyPixels on startup then rendering remains fast thereafter.
What are the read and draw buffers for glCopyPixels? If either of them
is GL_FRONT*, that will cause a DRI2 fake front buffer to be allocated
and thereafter kept up to date wrt the real front buffer.
This seems to set a flag in the ctx which is never cleared.
It is cleared:
end:
_mesa_set_vp_override(ctx, GL_FALSE);
Reply at: https://bugs.launchpad.net/compiz/+bug/1037411/comments/19
On 2012-09-12T01:48:54+00:00 Daniel van Vugt wrote:
Yes, the read buffer is GL_FRONT in this case. So I guess the slow-down
is by design in Mesa. I'm going to work around it in compiz anyway.
glCopyPixels should never be touched at all really.
P.S. _mesa_set_vp_override(ctx, GL_FALSE) does not clear NewState. Which
is what I was concerned about:
void
_mesa_set_vp_override(struct gl_context *ctx, GLboolean flag)
{
if (ctx-VertexProgram._Overriden != flag) {
ctx-VertexProgram._Overriden = flag;
/* Set one of the bits which will trigger fragment program
* regeneration:
*/
ctx-NewState |= _NEW_PROGRAM;
}
}
Reply at: https://bugs.launchpad.net/compiz/+bug/1037411/comments/20
On 2012-09-12T02:33:00+00:00 Marek Olšák wrote:
Don't worry about NewState. It's cleared after every draw operation.
Reply at: https://bugs.launchpad.net/compiz/+bug/1037411/comments/21
On 2012-09-12T04:52:06+00:00 Chris Forbes wrote:
Would it be reasonable to put a performance note in
ARB_debug_output/KHR_debug when mesa falls into this slow state?
Reply at: https://bugs.launchpad.net/compiz/+bug/1037411/comments/22
On 2012-09-12T09:29:28+00:00 Michel-daenzer wrote:
(In reply to comment #3)
Yes, the read buffer is GL_FRONT in this case. So I guess the slow-down is by
design in Mesa.
Rather the X server / DRI2 protocol. It *might* be possible to make
xserver not enforce the fake front buffer for the Composite Overlay
Window, not sure.
I'm going to work around it in compiz anyway. glCopyPixels
should never be touched at all really.
Out of curiosity, what are you using it for?
Reply at: https://bugs.launchpad.net/compiz/+bug/1037411/comments/23
On 2012-09-12T09:31:58+00:00 Daniel van Vugt wrote:
It is a fallback used for maintaining a persistent backbuffer if FBOs
are not available. However it's not an important one because all drivers
provide FBOs now.
http://bazaar.launchpad.net/~compiz-
team/compiz/0.9.8/view/head:/plugins/opengl/src/screen.cpp#L1726
Reply at: https://bugs.launchpad.net/compiz/+bug/1037411/comments/24
** Changed in: mesa
Status: Unknown = Confirmed
** Changed in: mesa
Importance: Unknown = Medium
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
[Ubuntu-x-swat] [Bug 1037411] Re: [regression][DRI] SubBuffer rendering is much slower in compiz 0.9.8.0 than it was in 0.9.7
Fix committed into lp:compiz at revision 3370 -- 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/1037411 Title: [regression][DRI] SubBuffer rendering is much slower in compiz 0.9.8.0 than it was in 0.9.7 To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1037411/+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 946417] Re: Cando Touchscreen buggy since Precise - After the first few successful clicks on the touchscreen, new clicks are not registered anymore.
I also have this bug on my gigabyte t1005 cando touchscreen. A workaround for me is replacing unity with avant-window-navigator. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/946417 Title: Cando Touchscreen buggy since Precise - After the first few successful clicks on the touchscreen, new clicks are not registered anymore. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/946417/+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 940564] Re: [8400m] nvidia-graphics-drivers (295.33-0ubuntu1), is causing failed restarts. shutdowns only a blackscreen on tty's other than tty7
I just came across this report, and while I'm not having problems with black screens or failed shut-downs so much, I have a similar set-up to the original reporter: Nvidia 8400M GT, Core 2 Duo, and I've been having problems with the GPU failing to activate (see Bug #1009312). It seems to be happening at the actual kernel level very early in booting, not the nvidia drivers. I'm seeing a lot of similarities in the patterns here though: problem seems to happen in cycles over multiple shutdowns, much better luck with the 64bit version of Ubuntu and the kernel (comment #6 above), having to revert to the VGA drivers (comment #12), some relation to power management. I don't think my report is an exact duplicate of this (and I think all kernel reports are supposed to be treated separately), but I would be interested if anyone here is seeing something similar to what I am. If anyone is, that could really help us narrow down what's going on. And again, if you have a 64bit processor, you really might want to try moving to the 64bit build of Ubuntu; when I was on the PAE kernel, GPU problems were the norm, but since switching to the 64bit version, I've only had one bad session over at least 10 reboots. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/940564 Title: [8400m] nvidia-graphics-drivers (295.33-0ubuntu1), is causing failed restarts. shutdowns only a blackscreen on tty's other than tty7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/940564/+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 971107] Re: vlc crashed with SIGSEGV in XQueryExtension()
Can you check if the following testcase can trigger the bug: wget https://jogamp.org/git/?p=jogl.git\;a=blob_plain\;f=src/test-native/displayMultiple02.c -O displayMultiple02.c gcc -o displayMultiple02 displayMultiple02.c -lX11 -lGL ./displayMultiple02 I belive this bug is similar to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/933846 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/971107 Title: vlc crashed with SIGSEGV in XQueryExtension() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/971107/+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 933846] Re: java crashed with SIGABRT in XQueryExtension()
** Also affects: fglrx-installer (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/933846 Title: java crashed with SIGABRT in XQueryExtension() To manage notifications about this bug go to: https://bugs.launchpad.net/fglrx/+bug/933846/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1038615] Re: Wacom Intuos 5 button touch moves the cursor to the top left corner
When you're patching away this bug, will button touches then get ignored completely? This wouldn't be helpful because under Windows you have got two different options concerning the left pad : To touch the button and execute a touch action or to press the button without executing the touch event. Both options are needed in different cases.. just wanted to state the before it leads to a non working touch pad ;) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xf86-input-wacom in Ubuntu. https://bugs.launchpad.net/bugs/1038615 Title: Wacom Intuos 5 button touch moves the cursor to the top left corner To manage notifications about this bug go to: https://bugs.launchpad.net/xf86-input-wacom/+bug/1038615/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1047306] Re: [Quantal] [Intel Atom] Mesa 2012/09/07 updates broke it all
** Bug watch added: freedesktop.org Bugzilla #54914 https://bugs.freedesktop.org/show_bug.cgi?id=54914 ** Also affects: mesa via https://bugs.freedesktop.org/show_bug.cgi?id=54914 Importance: Unknown Status: Unknown -- 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/1047306 Title: [Quantal] [Intel Atom] Mesa 2012/09/07 updates broke it all To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1047306/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1021924]
Sorry I haven't had more time to try and debug this. Just posted on G+ asking for anyone with the same CPU/Motherboard and multiple displays to help out if possible. That said, I tried switching crtc on the outputs just now, and I can get the main screen to switch between the two, but the secondary always stays black now (it's no longer red, though not sure why). I'm trying to find a 3.6-rc kernel package for Ubuntu, to test with. The current 12.10 kernel is I think based on 3.5.3, and I don't know if it has the Intel video code back-ported from 3.6 or not. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1021924 Title: Multiple Displays not working on Core i7 3770S + Intel DQ77MK motherboard To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1021924/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1021924]
This appears in dmesg: [ 21.891791] i915 :00:02.0: setting latency timer to 64 [ 21.892354] i915 :00:02.0: irq 50 for MSI/MSI-X [ 21.892364] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). [ 21.892365] [drm] Driver supports precise vblank timestamp query. [ 21.892690] vgaarb: device changed decodes: PCI::00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem [ 22.029166] [drm] Enabling RC6 states: RC6 on, RC6p on, RC6pp off [ 22.654318] fbcon: inteldrmfb (fb0) is primary device [ 22.654395] Console: switching to colour frame buffer device 256x72 [ 22.654441] fb0: inteldrmfb frame buffer device [ 22.654442] drm: registered panic notifier [ 22.656484] ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no) [ 22.656611] [drm] Initialized i915 1.6.0 20080730 for :00:02.0 on minor 0 [ 23.490221] [drm:ivb_manual_fdi_link_train] *ERROR* FDI train 1 fail! [ 23.492366] [drm:ivb_manual_fdi_link_train] *ERROR* FDI train 2 fail! The last 2 messages appear to match Daniel's suggestion of fdi train fail. Is this enough information to go on for now? I installed a 3.6-rc5 kernel, but upon booting it, my mouse and keyboard were not working under X, so I was unable to log in, switch to a console, or even reboot without using the hardware reset button. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1021924 Title: Multiple Displays not working on Core i7 3770S + Intel DQ77MK motherboard To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1021924/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 946311]
I got one more laptop with ivy bridge and same issue: Zunebook ux31a. CPU i5-3317U. intel_stepping Vendor: 0x8086, Device: 0x0166, Revision: 0x09 (??) render clock: unknown sampler clock: unknown -- 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/946311 Title: only external screen is working with asus zenbook ux31e [eDP1] To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/946311/+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 556782]
Unfortunately, this patch changed nothing here. I'm still enable to start unity/gnome-shell and I have some graphic corruptions when using a fallback such as Unity 2D. This is on a Acer Emachine e625 laptop. I tested the patch on both 32 and 32-pae kernels from Ubuntu 12.04 (3.2.0-31.50). -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/556782 Title: [rs690m] Graphics corruption with ati x1200 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/556782/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1021924]
Yep, this is an issue with the kernel modeset code in the drm/i915.ko driver. But this bug is in the right bugzilla, we also handle the kernel issues for the intel driver here. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1021924 Title: Multiple Displays not working on Core i7 3770S + Intel DQ77MK motherboard To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1021924/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1021924]
Daniel, does having these messages from drm indicate this is likely a kernel issue rather than an Xorg issue, at this point? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1021924 Title: Multiple Displays not working on Core i7 3770S + Intel DQ77MK motherboard To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1021924/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 496653]
(In reply to comment #15) (In reply to comment #14) The further commits to drt may have regressed this again - I can't be sure as I can't run todays head, but while bisecting for - https://bugs.freedesktop.org/show_bug.cgi?id=27536 I noticed on the goods close to the problematic commit that x11 putimage perf had regressed. That bug is fixed now and the perf with todays drt is OK, so as far as I am concerned this bug is fixed. Closing. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/496653 Title: [KMS][RV530] compiz very slow on Radeon AGP video cards To manage notifications about this bug go to: https://bugs.launchpad.net/desktop-screenshots/+bug/496653/+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 496653] Re: [KMS][RV530] compiz very slow on Radeon AGP video cards
** Changed in: mesa Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/496653 Title: [KMS][RV530] compiz very slow on Radeon AGP video cards To manage notifications about this bug go to: https://bugs.launchpad.net/desktop-screenshots/+bug/496653/+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 1050202] Re: Cherrypick xrandr list providers to complete DRI2 offloading graphics stack
Launchpad has imported 1 comments from the remote bug at https://bugs.freedesktop.org/show_bug.cgi?id=54840. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2012-09-13T06:00:41+00:00 Eric Appleman wrote: A stable release would permit the upcoming distro releases to boast a complete DRI2 offloading stack without a cherrypick. Reply at: https://bugs.launchpad.net/xorg-server/+bug/1050202/comments/2 ** Changed in: xorg-server Status: Unknown = Confirmed ** Changed in: xorg-server Importance: Unknown = Medium -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to x11-xserver-utils in Ubuntu. https://bugs.launchpad.net/bugs/1050202 Title: Cherrypick xrandr list providers to complete DRI2 offloading graphics stack To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1050202/+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 1046951] Re: No desktop environment or window manager, just X with the mouse
The radeon driver no longer supports UMS. Because of the current PowerPC kernel config (radeonfb is built in) KMS drm cannot be activated. You are falling back to the fbdev driver in 8 bit mode (hence the poor colors). One way to activate KMS is using the video=ofonly parameter (this disables radeonfb). If this causes freezing then you should combine it with radeon.agpmode=-1 (forces PCI mode). I've said the same thing on this ubuntu forums thread http://ubuntuforums.org/showthread.php?t=2053596 These solutions have also been documented in the PowerPC FAQ for a long time now https://wiki.ubuntu.com/PowerPCFAQ#What_yaboot_parameters_should_I_use_for_graphics_problems.3F and https://wiki.ubuntu.com/PowerPCFAQ#Radeon_cards -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1046951 Title: No desktop environment or window manager, just X with the mouse To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1046951/+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 1046951] Re: No desktop environment or window manager, just X with the mouse
I'm not sure why ubiquity can't cope with 8 bit colours.possibly something that might be worth looking into? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1046951 Title: No desktop environment or window manager, just X with the mouse To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1046951/+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 1050850] [NEW] fail gpu driver
Public bug reported: po up message of internal sistem fail. fail gpu driver Hardware: Intel Sandy Bridge 2500k ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xorg 1:7.6+12ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-13.13-generic 3.5.3 Uname: Linux 3.5.0-13-generic i686 ApportVersion: 2.0.1-0ubuntu13 Architecture: i386 CheckboxSubmission: 40086fa6300cff25a7af33cc2a1dbc0c CheckboxSystem: daed2f3d6643b4a84b4520a2427f8c2b Date: Fri Sep 14 12:25:43 2012 DistroCodename: precise DistroVariant: ubuntu InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 precise third-party-packages ubuntu -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1050850 Title: fail gpu driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1050850/+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 1050850] Re: fail gpu driver
-- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1050850 Title: fail gpu driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1050850/+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 1047306] Re: [Quantal] [Intel Atom] Mesa 2012/09/07 updates broke it all
Launchpad has imported 1 comments from the remote bug at https://bugs.freedesktop.org/show_bug.cgi?id=54914. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2012-09-14T09:32:20+00:00 Timo Aaltonen wrote: we've bisected a bug in i915_dri.so which was caused by this commit: commit c8a86f717f8e30204c615d06bcec159410ac06c5 Author: Brian Paul bri...@vmware.com Date: Fri Aug 31 08:33:31 2012 -0600 mesa: move IS_NEGATIVE() and DIFFERENT_SIGNS() to macros.h and it was discussed briefly on #intel-gfx: ickle let me guess: GLboolean is a char ickle yup. ickle DIFFERENT_SIGNS() always return 0 as (unsigned char)(131) == 0 ickle also note that fi_type isn't well defined when sizeof(int)!=4 the downstream bug is https://bugs.launchpad.net/ubuntu/quantal/+source/mesa/+bug/1047306 causing unity/compiz segfaults with hw using the dri driver. Reverting just that commit was verified to work. Reply at: https://bugs.launchpad.net/mesa/+bug/1047306/comments/27 ** Changed in: mesa Status: Unknown = Confirmed ** Changed in: mesa Importance: Unknown = Medium -- 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/1047306 Title: [Quantal] [Intel Atom] Mesa 2012/09/07 updates broke it all To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1047306/+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 685516] Re: Ubuntu 10.04 LTS is unable to handle analog monitors (resolution cannot be set)
And still - nothing. Hey guys, there are _lots_ of users out there with good old CRT monitors that are left in rain! Please - We do not ask to mess up the user interface with lots of entries. But is too much to ask for an experts button, behind which you could just simply _set_ resolution, refresh rate? Even Windows can do that. -- 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/685516 Title: Ubuntu 10.04 LTS is unable to handle analog monitors (resolution cannot be set) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/685516/+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 750437] Re: fglrx hard lockup on shutdown
Disabling kernel mode setting is important, as the driver doesn't appear to take advantage of KMS yet. If you do not deactivate KMS, your system might freeze when trying to switch to a tty or even when shutting down via your DE. Source: Arch Wiki For Grub2, edit /etc/default/grub and add nomodeset to the kernel parameter options, e.g. GRUB_CMDLINE_LINUX_DEFAULT=nomodeset -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/750437 Title: fglrx hard lockup on shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/750437/+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 750437] Re: fglrx hard lockup on shutdown
In addition, run sudo update-grub -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/750437 Title: fglrx hard lockup on shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/750437/+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 1046951] Re: No desktop environment or window manager, just X with the mouse
This is the bug for ubiquity https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1040544 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1046951 Title: No desktop environment or window manager, just X with the mouse To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1046951/+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 1037483] Re: [SRU] Needs NVIDIA driver 304.43 [HW-Certification blocker]
** Also affects: nvidia-settings (Ubuntu Quantal) Importance: Medium Assignee: Alberto Milone (albertomilone) Status: Fix Released ** Also affects: nvidia-graphics-drivers (Ubuntu Quantal) Importance: Medium Assignee: Alberto Milone (albertomilone) Status: Fix Released ** Also affects: nvidia-graphics-drivers-updates (Ubuntu Quantal) Importance: Medium Assignee: Alberto Milone (albertomilone) Status: Fix Released ** Also affects: nvidia-settings-updates (Ubuntu Quantal) Importance: Medium Assignee: Alberto Milone (albertomilone) Status: Fix Released -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/1037483 Title: [SRU] Needs NVIDIA driver 304.43 [HW-Certification blocker] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1037483/+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 869047] Re: PgUp does not work Acer Aspire 5750-9668
** Tags added: kernel-bug-exists-upstream kernel-bug-exists- upstream-v3.6-rc5-quantal -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/869047 Title: PgUp does not work Acer Aspire 5750-9668 To manage notifications about this bug go to: https://bugs.launchpad.net/evdev/+bug/869047/+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 1050946] Re: Xorg crashed with SIGABRT in raise()
*** This bug is a duplicate of bug 1037518 *** https://bugs.launchpad.net/bugs/1037518 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1037518, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: CoreDump.gz https://bugs.launchpad.net/bugs/1050946/+attachment/3314690/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1050946/+attachment/3314693/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1050946/+attachment/3314703/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1050946/+attachment/3314705/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1050946/+attachment/3314706/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1050946/+attachment/3314707/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1050946/+attachment/3314708/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1037518 Xorg crashed with SIGABRT - FatalError (f=f@entry=0x7f41e2f9a9e2 no screens found) ** Visibility changed to: Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1050946 Title: Xorg crashed with SIGABRT in raise() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1050946/+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 1047306] Re: [Mesa revert because of it, not impacting quantal right now] [Quantal] [Intel Atom] Mesa 2012/09/07 updates broke it all
** Summary changed: - [Quantal] [Intel Atom] Mesa 2012/09/07 updates broke it all + [Mesa revert because of it, not impacting quantal right now] [Quantal] [Intel Atom] Mesa 2012/09/07 updates broke it all ** Summary changed: - [Mesa revert because of it, not impacting quantal right now] [Quantal] [Intel Atom] Mesa 2012/09/07 updates broke it all + [Mesa reverted, not impacting quantal right now] [Quantal] [Intel Atom] Mesa 2012/09/07 updates broke it all -- 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/1047306 Title: [Mesa reverted, not impacting quantal right now] [Quantal] [Intel Atom] Mesa 2012/09/07 updates broke it all To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1047306/+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 869047] Re: PgUp does not work Acer Aspire 5750-9668
** Description changed: 1) lsb_release -rd Description: Ubuntu precise (development branch) Release: 12.04 lsb_release -rd Description: Ubuntu oneiric (development branch) Release: 11.10 2) uname -a Linux monikerpc 3.4.0-030400rc1-generic #201203312035 SMP Sun Apr 1 00:43:10 UTC 2012 i686 i686 i386 GNU/Linux uname -r 3.0.0-13-generic-pae apt-cache policy xserver-xorg-input-evdev xserver-xorg-input-evdev: Installed: 1:2.6.0-1ubuntu13 Candidate: 1:2.6.0-1ubuntu13 Version table: *** 1:2.6.0-1ubuntu13 0 500 http://us.archive.ubuntu.com/ubuntu/ oneiric/main i386 Packages 100 /var/lib/dpkg/status 3) What is expected to happen is when one presses the PgUp key on the built in keyboard, it does so. 4) What happens instead is no program goes one page up. PgDown works as expected. Following https://wiki.ubuntu.com/DebuggingKeyboardDetection please see attached. **NOTE: Unable to attach gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd as it produced a 0 byte file. I am currently using Xubuntu. + + Reproducible in Lucid. One thing noticed is when pressing Ctrl+Alt+F2 and logging in, PgUp works as expected but does not work in the Terminal when in Ctrl+Alt+F7. xev did not register anything when clicking PgUp. It does register clicking PgDn. xinput list ⎡ Virtual core pointer id=2 [master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPad id=12 [slave pointer (2)] ⎣ Virtual core keyboard id=3 [master keyboard (2)] ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)] ↳ Power Button id=6 [slave keyboard (3)] ↳ Video Bus id=7 [slave keyboard (3)] ↳ Power Button id=8 [slave keyboard (3)] ↳ Sleep Button id=9 [slave keyboard (3)] ↳ 1.3M HD WebCam id=10 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=11 [slave keyboard (3)] xinput test AT Translated Set 2 keyboard does not register anything when clicking PgUp. It does register clicking PgDn. + sudo evtest No device specified, trying to scan all of /dev/input/event* Available devices: /dev/input/event0: Power Button /dev/input/event1: Lid Switch /dev/input/event10: SynPS/2 Synaptics TouchPad /dev/input/event2: Sleep Button /dev/input/event3: Power Button /dev/input/event4: AT Translated Set 2 keyboard /dev/input/event5: Video Bus /dev/input/event6: 1.3M HD WebCam /dev/input/event7: HDA Intel PCH HDMI/DP,pcm=3 /dev/input/event8: HDA Intel PCH Mic /dev/input/event9: HDA Intel PCH Headphone Select the device event number [0-10]: 4 Input driver version is 1.0.1 Input device ID: bus 0x11 vendor 0x1 product 0x1 version 0xab41 Input device name: AT Translated Set 2 keyboard Supported events: Event type 0 (Sync) Event type 1 (Key) Event code 1 (Esc) Event code 2 (1) Event code 3 (2) Event code 4 (3) Event code 5 (4) Event code 6 (5) Event code 7 (6) Event code 8 (7) Event code 9 (8) Event code 10 (9) Event code 11 (0) Event code 12 (Minus) Event code 13 (Equal) Event code 14 (Backspace) Event code 15 (Tab) Event code 16 (Q) Event code 17 (W) Event code 18 (E) Event code 19 (R) Event code 20 (T) Event code 21 (Y) Event code 22 (U) Event code 23 (I) Event code 24 (O) Event code 25 (P) Event code 26 (LeftBrace) Event code 27 (RightBrace) Event code 28 (Enter) Event code 29 (LeftControl) Event code 30 (A) Event code 31 (S) Event code 32 (D) Event code 33 (F) Event code 34 (G) Event code 35 (H) Event code 36 (J) Event code 37 (K) Event code 38 (L) Event code 39 (Semicolon) Event code 40 (Apostrophe) Event code 41 (Grave) Event code 42 (LeftShift) Event code 43 (BackSlash) Event code 44 (Z) Event code 45 (X) Event code 46 (C) Event code 47 (V) Event code 48 (B) Event code 49 (N) Event code 50 (M) Event code 51 (Comma) Event code 52 (Dot) Event code 53 (Slash) Event code 54 (RightShift) Event code 55 (KPAsterisk) Event code 56 (LeftAlt) Event code 57 (Space) Event code 58 (CapsLock) Event code 59 (F1) Event code 60 (F2) Event code 61 (F3) Event code 62 (F4) Event code 63 (F5) Event code 64 (F6) Event code 65 (F7) Event code 66 (F8) Event code 67 (F9) Event code 68 (F10) Event code 69 (NumLock) Event code 70 (ScrollLock) Event code 71 (KP7) Event code 72 (KP8) Event code 73 (KP9) Event code 74 (KPMinus) Event code 75 (KP4) Event code 76 (KP5) Event code 77 (KP6) Event code 78 (KPPlus) Event code 79 (KP1) Event code 80 (KP2)
[Ubuntu-x-swat] [Bug 1050975] Re: Xorg crashed with SIGABRT in raise()
*** This bug is a duplicate of bug 1037518 *** https://bugs.launchpad.net/bugs/1037518 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1037518, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: CoreDump.gz https://bugs.launchpad.net/bugs/1050975/+attachment/3314799/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1050975/+attachment/3314802/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1050975/+attachment/3314812/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1050975/+attachment/3314814/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1050975/+attachment/3314815/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1050975/+attachment/3314816/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1050975/+attachment/3314817/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1037518 Xorg crashed with SIGABRT - FatalError (f=f@entry=0x7f41e2f9a9e2 no screens found) ** Visibility changed to: Public ** Tags removed: need-i386-retrace -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1050975 Title: Xorg crashed with SIGABRT in raise() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1050975/+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 1051020] [NEW] MacBookAir3, 1 has pulsing pixelated vertical line down right side of screen after suspend/resume
Public bug reported: After suspend/resume my MacBookAir3,1 has pulsing pixelated vertical line down right side of screen: * http://www.youtube.com/watch?v=_ymoZ9uIQ4E Logs and additional info should be attached below with ubuntu-bug. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu3 ProcVersionSignature: Ubuntu 3.5.0-14.17-generic 3.5.3 Uname: Linux 3.5.0-14-generic x86_64 ApportVersion: 2.5.1-0ubuntu7 Architecture: amd64 CheckboxSubmission: 15c9c9b122c9273f52b28c9a5df794ac CheckboxSystem: 7e42599bda39ea7ff8b528272b6ef52b Date: Fri Sep 14 14:04:21 2012 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu EcryptfsInUse: Yes GraphicsCard: NVIDIA Corporation Device [10de:08a2] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Device [106b:00d4] InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120911) MachineType: Apple Inc. MacBookAir3,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-14-generic root=UUID=89b2a46d-ca3a-4913-97ed-806488eadb5d ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/24/12 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA31.88Z.0061.B07.1201241641 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-942452F5819B1C1B dmi.board.vendor: Apple Inc. dmi.board.version: 1.0 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-942452F5819B1C1B dmi.modalias: dmi:bvnAppleInc.:bvrMBA31.88Z.0061.B07.1201241641:bd01/24/12:svnAppleInc.:pnMacBookAir3,1:pvr1.0:rvnAppleInc.:rnMac-942452F5819B1C1B:rvr1.0:cvnAppleInc.:ct10:cvrMac-942452F5819B1C1B: dmi.product.name: MacBookAir3,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz 1:0.9.8.0-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.39-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0~git20120903.e1673d20.is.git20120821.c1114c61-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0~git20120903.e1673d20.is.git20120821.c1114c61-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120713.6ef1ad6a-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.7-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug corruption quantal running-unity ubuntu -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1051020 Title: MacBookAir3,1 has pulsing pixelated vertical line down right side of screen after suspend/resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1051020/+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 1051020] Re: MacBookAir3, 1 has pulsing pixelated vertical line down right side of screen after suspend/resume
-- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1051020 Title: MacBookAir3,1 has pulsing pixelated vertical line down right side of screen after suspend/resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1051020/+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 1051027] [NEW] MacBookAir3, 1 loses desktop background image after suspend/resume
Public bug reported: After a suspend/resume my desktop background image changes from my custom image back to black. When I go back into gnome-control-center (Gear - System Settings... - Appearance - Look) the background image is still set there and I have to toggle something (change from Fill to Scale and back to Fill) to get the background image to show back up again. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu3 ProcVersionSignature: Ubuntu 3.5.0-14.17-generic 3.5.3 Uname: Linux 3.5.0-14-generic x86_64 ApportVersion: 2.5.1-0ubuntu7 Architecture: amd64 CheckboxSubmission: 15c9c9b122c9273f52b28c9a5df794ac CheckboxSystem: 7e42599bda39ea7ff8b528272b6ef52b Date: Fri Sep 14 14:18:29 2012 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu EcryptfsInUse: Yes GraphicsCard: NVIDIA Corporation Device [10de:08a2] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Device [106b:00d4] InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120911) MachineType: Apple Inc. MacBookAir3,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-14-generic root=UUID=89b2a46d-ca3a-4913-97ed-806488eadb5d ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/24/12 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA31.88Z.0061.B07.1201241641 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-942452F5819B1C1B dmi.board.vendor: Apple Inc. dmi.board.version: 1.0 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-942452F5819B1C1B dmi.modalias: dmi:bvnAppleInc.:bvrMBA31.88Z.0061.B07.1201241641:bd01/24/12:svnAppleInc.:pnMacBookAir3,1:pvr1.0:rvnAppleInc.:rnMac-942452F5819B1C1B:rvr1.0:cvnAppleInc.:ct10:cvrMac-942452F5819B1C1B: dmi.product.name: MacBookAir3,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz 1:0.9.8.0-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.39-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0~git20120903.e1673d20.is.git20120821.c1114c61-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0~git20120903.e1673d20.is.git20120821.c1114c61-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120713.6ef1ad6a-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.7-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu1 ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug quantal running-unity ubuntu -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1051027 Title: MacBookAir3,1 loses desktop background image after suspend/resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1051027/+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 1051027] Re: MacBookAir3, 1 loses desktop background image after suspend/resume
** Also affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1051027 Title: MacBookAir3,1 loses desktop background image after suspend/resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1051027/+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 1051035] [NEW] MacBookAir3, 1 has screen corruption on boot between Grub and Login (no Pylmouth Ubuntu logo)
Public bug reported: During a reboot or fresh cold boot my MacBookAir3,1 doesn't give a Plymouth Ubuntu logo screen. It's just garbled corruption from unflushed video memory. Sometimes the last image on screen before reboot is visible after reboot (albeit backwards, blocked, and pixelated). * http://www.youtube.com/watch?v=6iOylaUEE4k ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu3 ProcVersionSignature: Ubuntu 3.5.0-14.17-generic 3.5.3 Uname: Linux 3.5.0-14-generic x86_64 ApportVersion: 2.5.1-0ubuntu7 Architecture: amd64 CheckboxSubmission: 15c9c9b122c9273f52b28c9a5df794ac CheckboxSystem: 7e42599bda39ea7ff8b528272b6ef52b Date: Fri Sep 14 14:40:21 2012 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu EcryptfsInUse: Yes GraphicsCard: NVIDIA Corporation Device [10de:08a2] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Device [106b:00d4] InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120911) MachineType: Apple Inc. MacBookAir3,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-14-generic root=UUID=89b2a46d-ca3a-4913-97ed-806488eadb5d ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/24/12 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA31.88Z.0061.B07.1201241641 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-942452F5819B1C1B dmi.board.vendor: Apple Inc. dmi.board.version: 1.0 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-942452F5819B1C1B dmi.modalias: dmi:bvnAppleInc.:bvrMBA31.88Z.0061.B07.1201241641:bd01/24/12:svnAppleInc.:pnMacBookAir3,1:pvr1.0:rvnAppleInc.:rnMac-942452F5819B1C1B:rvr1.0:cvnAppleInc.:ct10:cvrMac-942452F5819B1C1B: dmi.product.name: MacBookAir3,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz 1:0.9.8.0-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.39-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0~git20120903.e1673d20.is.git20120821.c1114c61-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0~git20120903.e1673d20.is.git20120821.c1114c61-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120713.6ef1ad6a-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.7-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug corruption quantal running-unity ubuntu -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1051035 Title: MacBookAir3,1 has screen corruption on boot between Grub and Login (no Pylmouth Ubuntu logo) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1051035/+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 1051035] Re: MacBookAir3, 1 has screen corruption on boot between Grub and Login (no Pylmouth Ubuntu logo)
-- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1051035 Title: MacBookAir3,1 has screen corruption on boot between Grub and Login (no Pylmouth Ubuntu logo) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1051035/+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 1011698] Re: Performance problems with Nvidia driver
Same problem with the following card and twinview. Nothing rotated. 01:00.0 VGA compatible controller: NVIDIA Corporation G84 [Quadro FX 570] (rev a1) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/1011698 Title: Performance problems with Nvidia driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1011698/+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 1051035] Re: MacBookAir3, 1 has screen corruption on boot between Grub and Login (no Pylmouth Ubuntu logo)
This is well before X comes into play. X only kicks in after plymouth is done. Might be a plymouth bug but maybe more likely to be something with the kernel framebuffer initialization. Probably best to start analysis from the kernel and work your way up to find the cause. ** Package changed: xorg (Ubuntu) = linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1051035 Title: MacBookAir3,1 has screen corruption on boot between Grub and Login (no Pylmouth Ubuntu logo) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1051035/+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 1051027] Re: MacBookAir3, 1 loses desktop background image after suspend/resume
Unlikely to be X doing this, but feel free to reopen if evidence comes to light indicating X is doing something wrong. I'd suggest also trying multiple times and see if the fault is reproducible or not. ** Changed in: xorg (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1051027 Title: MacBookAir3,1 loses desktop background image after suspend/resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1051027/+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 1051020] Re: MacBookAir3, 1 has pulsing pixelated vertical line down right side of screen after suspend/resume
Suspend/resume is handled by the kernel, so am bumping this over to them for troubleshooting. However this looks to me like perhaps something screwy with the nouveau drm module not reinitializing the GPU. The kernel team can guide you through testing some alternate kernels and bisect down to the fix if there is one. Fwiw, the collected logs don't reveal anything about the bug (corruption issues almost never show evidence in logs). So I'd recommend doing a bit more experimentation on the hardware to see e.g. how often the flaw can be reproduced, if activities other than suspend/resume can cause it, if any nouveau kernel driver options make it more or less likely to occur, etc. Beyond that, test newer and older kernels. ** Package changed: xorg (Ubuntu) = linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1051020 Title: MacBookAir3,1 has pulsing pixelated vertical line down right side of screen after suspend/resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1051020/+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 1032622] Re: [quantal] ctrl+alt+l fail to start screenserver
Stefan, are you still seeing this issue? If so I'd recommend working through some of the troubleshooting steps at https://wiki.ubuntu.com/Hotkeys to help narrow down where the fault is. ** Changed in: xorg (Ubuntu) Status: Confirmed = Incomplete -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1032622 Title: [quantal] ctrl+alt+l fail to start screenserver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1032622/+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 1049088] Re: Unity crashes at login with nouveau driver
Bug in the nouveau drm I'm guessing. Might try booting newer/older/mainline kernels. ** Package changed: xorg (Ubuntu) = xserver-xorg-video-nouveau (Ubuntu) ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1049088 Title: Unity crashes at login with nouveau driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1049088/+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 1048769] Re: i cant launch system testing application and edge scroling not working .. and i cant adjust brightness with function keys
Not enough information has been provided to make this a useful bug report. See http://wiki.ubuntu.com/X/Reporting for instructions on reporting X issues. In particular for issues such as described in the title, no useful information is printed to logs, so you need to provide a detailed case for how to reproduce the trouble. These particular symptoms often crop up due to gnome rather than xorg, so be sure to isolate what component failed. ** Changed in: xorg (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1048769 Title: i cant launch system testing application and edge scroling not working .. and i cant adjust brightness with function keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1048769/+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 1048465] Re: Xorg can't start in normal graphic mode
Still having trouble? Your bug description is rather terse so hard to understand. I see you have two video cards, and X is not able to associate a video driver with either of them. It might help if you could explain your situation in more detail, what's worked in the past and what all you've tested so far. ** Changed in: xorg (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1048465 Title: Xorg can't start in normal graphic mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1048465/+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 1049088] Re: Unity crashes at login with nouveau driver
** Changed in: linux (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1049088 Title: Unity crashes at login with nouveau driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1049088/+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 1047611] Re: Very weird mouse sticking issues
According to the Xorg.0.log, the touchpad has the synaptics driver loaded, whereas the touchscreen and pen are using the wacom driver. There is also a MCE IR Keyboard/Mouse which loads the evdev driver; I assume that's for your keyboard, no IR mouse? If I understand your report, you're seeing the glitchy pointer behavior with both the touchpad and the touchscreen/pen. Since those use different X drivers, that seems to suggest the issue is not the X driver but something deeper in. Might be interesting to attach a wired mouse and verify the same behavior is seen with that. Do you have a wireless IR mouse attached? If you do, doublecheck the battery. ** Changed in: xorg (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1047611 Title: Very weird mouse sticking issues To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1047611/+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 1046957] Re: error during filesystem turns off monitor, never comes back on
That's actually prior to when X actually gets started up. ** Package changed: xorg (Ubuntu) = plymouth (Ubuntu) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1046957 Title: error during filesystem turns off monitor, never comes back on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1046957/+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 1044746] Re: Response very slow, windows dim out when cliked on close.
** Package changed: xorg (Ubuntu) = virtualbox-ose (Ubuntu) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1044746 Title: Response very slow, windows dim out when cliked on close. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox-ose/+bug/1044746/+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 1047664] Re: xorg swaps some gigabytes and so system is not very responsive
** Package changed: xorg (Ubuntu) = qt4-x11 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1047664 Title: xorg swaps some gigabytes and so system is not very responsive To manage notifications about this bug go to: https://bugs.launchpad.net/vlc/+bug/1047664/+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 1044313] Re: Striped texture when unminimize Blender.
Please collect a full backtrace on this crash - see http://wiki.ubuntu.com/X/Backtracing for guidance. ** Package changed: xorg (Ubuntu) = xserver-xorg-video-ati (Ubuntu) ** Changed in: xserver-xorg-video-ati (Ubuntu) Importance: Undecided = High ** Changed in: xserver-xorg-video-ati (Ubuntu) Status: Confirmed = Incomplete ** Summary changed: - Striped texture when unminimize Blender. + SEGV and Striped texture when unminimize Blender. ** Changed in: xserver-xorg-video-ati (Ubuntu) Status: Incomplete = New -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1044313 Title: SEGV and Striped texture when unminimize Blender. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1044313/+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 1044313] Re: SEGV and Striped texture when unminimize Blender.
Also, when you reproduce this bug can you check that it corresponds with the segfault? E.g. `tail -f /var/log/Xorg.0.log` in a window, then reproduce and see if the stacktrace prints at exactly that moment. I'm assuming it does, but if not you may be looking at two separate bugs (lucky you). ** Changed in: xserver-xorg-video-ati (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1044313 Title: SEGV and Striped texture when unminimize Blender. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1044313/+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 1041368] Re: System boots into black screen unless nomodeset is used
All the logs attached to this bug are useless, they just show VESA loaded because you disabled modesetting on intel. You need to look at the log files from the broken system. Roosje, no your problem is something completely different. ** Changed in: xorg (Ubuntu) Status: Confirmed = Invalid -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1041368 Title: System boots into black screen unless nomodeset is used To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1041368/+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 1040935] Re: Live CD session fails in Graphic Mess
Not enough information has been provided to make this a useful bug report. See http://wiki.ubuntu.com/X/Reporting for instructions on reporting X issues. ** Changed in: xorg (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1040935 Title: Live CD session fails in Graphic Mess To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1040935/+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 1037306] Re: after todays update there is no desktop on omap4+armhf on pandaboard ES
** Package changed: xorg (Ubuntu) = xf86-video-omap (Ubuntu) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xf86-video-omap in Ubuntu. https://bugs.launchpad.net/bugs/1037306 Title: after todays update there is no desktop on omap4+armhf on pandaboard ES To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xf86-video-omap/+bug/1037306/+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 1051075] Re: Xorg crashed with SIGABRT in CloseWellKnownConnections()
** Visibility changed to: Public -- 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/1051075 Title: Xorg crashed with SIGABRT in _XSERVTransClose() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1051075/+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 1051075]
StacktraceTop: _XSERVTransClose (ciptr=0xb9026b00) at /usr/include/X11/Xtrans/Xtrans.c:902 CloseWellKnownConnections () at ../../os/connection.c:515 AbortServer () at ../../os/log.c:649 FatalError (f=f@entry=0xb76dc678 %s: VT_ACTIVATE failed: %s\n) at ../../os/log.c:793 switch_to (vt=7, from=from@entry=0xb76dc701 xf86CloseConsole) at ../../../../../hw/xfree86/os-support/linux/lnx_init.c:64 -- 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/1051075 Title: Xorg crashed with SIGABRT in _XSERVTransClose() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1051075/+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 1051075] Stacktrace.txt
** Attachment added: Stacktrace.txt https://bugs.launchpad.net/bugs/1051075/+attachment/3315419/+files/Stacktrace.txt -- 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/1051075 Title: Xorg crashed with SIGABRT in _XSERVTransClose() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1051075/+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 1051075] StacktraceSource.txt
** Attachment added: StacktraceSource.txt https://bugs.launchpad.net/bugs/1051075/+attachment/3315420/+files/StacktraceSource.txt -- 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/1051075 Title: Xorg crashed with SIGABRT in _XSERVTransClose() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1051075/+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 1051075] ThreadStacktrace.txt
** Attachment added: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1051075/+attachment/3315421/+files/ThreadStacktrace.txt ** Attachment removed: CoreDump.gz https://bugs.launchpad.net/bugs/1051075/+attachment/3315389/+files/CoreDump.gz ** Changed in: xorg-server (Ubuntu) Importance: Undecided = Medium ** Summary changed: - Xorg crashed with SIGABRT in CloseWellKnownConnections() + Xorg crashed with SIGABRT in _XSERVTransClose() ** Tags removed: need-i386-retrace -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1051075 Title: Xorg crashed with SIGABRT in _XSERVTransClose() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1051075/+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 1048465] Re: Xorg can't start in normal graphic mode
Still having trouble yet... Indeed I have two Graphics Cards, but they were fine with Oneiric and Precise, that's why this bug is so strange for me... X never did it with me, I already have used Arch Linux, Debian, Ubuntu and this was my first problem with X. I've tried to reinstall xorg, radeon/ati and nothing worked... Basically after the boot, I can't get X, Ubuntu remains in console mode, I've tried to start lightdm again, but didn't work, start Xorg neither, so after a while turning on and off, sometimes I get the Low-graphics mode of X, where I could see the logs and stuff, but that was the only working option, to see the log. Ubuntu just shows me the graphical user interface when I set the kernel to boot with nomodeset. I've tried two ways to install it, so I guess it's not a problem with the ISO, should I try to install 12.04 and then upgrade it? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1048465 Title: Xorg can't start in normal graphic mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1048465/+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 1047611] Re: Very weird mouse sticking issues
The only infra red device on this laptop is the receiver for the remote control. I don't think that should be affecting this. Next time it happens (probably later tonight), I'll attach a wired mouse, but I think the issues will remain. After that, I'll try blacklisting the wacom driver and seeing if that stops it occurring, then the synaptics driver should the problem still occur without the touch screen. Stand by for the results Cheers -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1047611 Title: Very weird mouse sticking issues To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1047611/+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 901630] Re: multitouch + qt doesn't work (eg fingerpaint demo) with wacom serial touchscreen
Hello, Can someone clarify where we stand in regard with this issue and Ubuntu Quantal 12.10? I've been following Qt doc to the letter and got QPinchGesture working in a QWidget... but as soon as the grabGesture is issued on that widget all other widgets (tabs, pushbuttons, lineedits, etc.) stop responding to click (tap). Where does the problem lie? Can it be fixed or shall one forget to have that gesture-stuff working along evdev (at least as far as 12.10 is concerned)? Thanks for your answer. Cheers -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xf86-input-wacom in Ubuntu. https://bugs.launchpad.net/bugs/901630 Title: multitouch + qt doesn't work (eg fingerpaint demo) with wacom serial touchscreen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/901630/+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 930936] Re: Xorg crashes after connect bluetooth keyboard
@Dmitry, continue crashing - do you have Xorg from oneiric-proposed installed? Post your /var/log/Xorg.0.log.old from after a crash. -- 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/930936 Title: Xorg crashes after connect bluetooth keyboard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/930936/+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
