[Ubuntu-x-swat] [Bug 1153734] Re: Corrupt graphics on Ubuntu 13.04
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete => Expired -- 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/1153734 Title: Corrupt graphics on Ubuntu 13.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1153734/+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 1173074] Re: Nouveau freezes after suspend/resume in Ubuntu 13.04 / 3.8.0
*** This bug is a duplicate of bug 1084960 *** https://bugs.launchpad.net/bugs/1084960 ** Also affects: archlinux 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/1173074 Title: Nouveau freezes after suspend/resume in Ubuntu 13.04 / 3.8.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1173074/+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 1068601] Re: 10de:0322 12.10: Black screen with GeForce FX 5200 card
Some more feedback. The install to hard disk seems to go well. Running from hard disk, using nouveau driver, seems at first glance OK. I left the system, later took out of screen saver. Background and top bar and left side bar ok. But while attempting to open the system setting, the initial menu only shows a rectangle with a king of garbled noisy pattern, nothing readable. Opening a terminal by ctrl-alt-t opens a comparable rectangle. Nothing readable, some kind of garbled noisy pattern (there seems to be some regualarity, random colers/spots). So the nouveau driver still has some issues. After opening ctrl-alt-F1 terminal (that works OK) and installing nvidia-173 (suitable for my graphics card) and a reboot, the original black background issue is again present. So the bug is confirmed using the daily build 13.10 downloaded 28-may-2013. I guess it would make sense to perform the apport-collect thing. But as the terminal is not visible, I need to type blind. Please advise on course of action. Attempt to perform the apport- collect (might install a startup script, maybe some logging into file). Can install the script after starting into one of the resque options. Or does it make sense to kick out nvidia and continue on nouveau? Please advise. -- 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/1068601 Title: 10de:0322 12.10: Black screen with GeForce FX 5200 card To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1068601/+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 1174043] Re: After dist-upgrade to 13.04 Intuos3 can not drag/paint any more under KDE
The 2.0 package + driver from PPA fixed it for me. No trickery needed for drawing after reboot. -- 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/1174043 Title: After dist-upgrade to 13.04 Intuos3 can not drag/paint any more under KDE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/1174043/+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 1041790]
Created attachment 79979 i915_error_state - 3.9.2-201.rhbz879823.fc18.x86_64 (included patch write mbox regs twice on snb, v2) Linux bobloblaw 3.9.2-201.rhbz879823.fc18.x86_64 #1 SMP Thu May 16 13:35:12 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux [45482.757631] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [45482.757645] [drm] capturing error event; look for more information in/sys/kernel/debug/dri/0/i915_error_state [45482.766942] [drm:kick_ring] *ERROR* Kicking stuck semaphore on render ring [45482.770617] [drm:__gen6_gt_force_wake_get] *ERROR* Timed out waiting for forcewake old ack to clear. I added patch (drm/i915: Resurrect ring kicking for semaphores, selectively) to Fedora 18's 3.9.2-200 x86_64 kernel. -- 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/1041790 Title: [snb] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001, workaround i915.semaphores=0 To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1041790/+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 1182103] Re: black screen in Ubuntu, in live CD Ubuntu.
** 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/1182103 Title: black screen in Ubuntu, in live CD Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1182103/+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 1068601] Re: 10de:0322 12.10: Black screen with GeForce FX 5200 card
Just want to give initial feedback, of course the experience of Graham is more important. After burning the daily build live DVD taken from #63 my computer starts quite normal. It uses the nouveau driver, goes into resolution 1680*1050. Works correct, quite slow. So no issues like black screen. No confirmation the bug still exists. Now installing to hard disk. Will check whether or not I can run with proprietary nvidia driver. And bring that into the resulution from 24 inch screen (1920*1200). -- 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/1068601 Title: 10de:0322 12.10: Black screen with GeForce FX 5200 card To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1068601/+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 1137817] Re: [ivb] System freeze after high memory usage
I still had no luck. I am now working with the drm-intel-nightly builds. But the situation is always the same: suddenly after 1 up to 5 hours the system freezes. No chance to get any response from the system. After some minutes the system shuts down. -- 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/1137817 Title: [ivb] System freeze after high memory usage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1137817/+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 1178706] Re: System freeze after DPMS off with external monitors
Thanks for the suggestion - that seems to have fixed it. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1178706 Title: System freeze after DPMS off with external monitors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1178706/+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 884191] Re: "Disable touchpad while typing" doesn't disable Synaptics touchpad on Lenovo ThinkPad T410i on Ubunutu 11.x
Same here on HP Elitebook 8740W with fresh install 13.04 However running syndaemon does disable typing as it should. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/884191 Title: "Disable touchpad while typing" doesn't disable Synaptics touchpad on Lenovo ThinkPad T410i on Ubunutu 11.x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/884191/+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 1178218] Re: Video output judders after suspend
I've additionally tried to restart compiz after docking my notebook; unfortunately, that didn't help at all. The only workaround is still to kill the X server. Is there anything I can do to help debugging the problem? Right now I have to restart X at least once per day... -- 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/1178218 Title: Video output judders after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1178218/+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 365300] Re: Randomly I get double clicks when I do a single click.
I am on Ubuntu 12.04 LTS and suddenly encountering this problem, but only for the right mouse button. It is sporadic, sometimes more often, sometimes less. Really annoying if using easystroke as your system goes wild then with executing batches of arbitrary mouse gestures :D :D Never thought of this possibly being a hardware issue - will test a different mouse, thx for that hint! -- 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/365300 Title: Randomly I get double clicks when I do a single click. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/365300/+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 1178865] Re: [Regression] after upgrading to Quantal X drivers and kernel /var/log/lightdm/x-0.log file is filled by errors: CS section size missmatch start at (../../src/radeon_t
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xserver-xorg-video-ati-lts-quantal (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati-lts-quantal in Ubuntu. https://bugs.launchpad.net/bugs/1178865 Title: [Regression] after upgrading to Quantal X drivers and kernel /var/log/lightdm/x-0.log file is filled by errors: CS section size missmatch start at (../../src/radeon_textured_videofuncs.c,R300PrepareTexturedVideo,1689) 33 vs 66 CS section end at (../../src/radeon_textured_videofuncs.c,R300PrepareTexturedVideo,2147) To manage notifications about this bug go to: https://bugs.launchpad.net/xf86-video-ati/+bug/1178865/+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 1039397] Re: [Dell Precision M6700] HDMI audio fails, HDMI/Displayport output has blank frame
** Tags removed: cid201205-11051 ** Tags added: 201205-11051 taipei-lab -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer-updates in Ubuntu. https://bugs.launchpad.net/bugs/1039397 Title: [Dell Precision M6700] HDMI audio fails, HDMI/Displayport output has blank frame To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer-updates/+bug/1039397/+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 772873] Re: Vino does not work with compositing
for trouble shooting, i have some updates. all are personal opinions and welcome to point out my misunderstanding. based on fglrx driver. when using metacity, we can see ProcCopyArea is frequently invoked if i drag a window around desktop. it help to update the damage region to some drawable which is indicated by VINO as following: vfb->priv->xdamage = XDamageCreate (vfb->priv->xdisplay, GDK_WINDOW_XID (vfb->priv->root_window), XDamageReportDeltaRectangles); in fact, the drawable ID is 186 on my platform, and i can oberve that DamageExtNotify for that ID in this case. the codestack shows it is triggered by damageCopyArea which is mentioned above. then VINO works well. key point, this copy is absolutely not requested by VINO because the client ID is different, so it's not the copy between RFB and root window. i wonder if it is metacity doing this copy. while, change to compiz. ProcCopyArea won't be invoked for draging a window. no damage updates to drawable 186. VINO freezes. actually we can force to flush some damages to drawable monitored by VINO, that's why enabled tear free option gives us a workaround, rotating screen also helps. but i don't prefer to add this flushing into common cases. i also got some questions: how does compiz draw the window while it is moving? if it won't copy area, is there any method to get the damages in Xserver side? i suppose it uses OGL to directly draw this process, but m not sure where it is rendered, root window or redirect window? i ask OGL guys to report kinds of damage to fglrx driver, no effect. i carefully say that it might be issue of DRI in fglrx driver, because radeon driver supports VINO much better, and DRI in fglrx doesn't comply with standards quite well. so all my info and questions are for the purpose of fixing this issue. if any buddy know the damage reporting mechanism for drawable monitored by VINO in COMPIZ+RADEON case, please help me. -- 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/772873 Title: Vino does not work with compositing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/772873/+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 1185340] [NEW] Precise only boots ~1 in 10 times with the NVIDIA driver enabled
Public bug reported: Release: Ubuntu 12.04.2 LTS Package: nvidia-current 304.88-0ubuntu0.0.2 Kernel: 3.2.0-44-generic I installed Precise from scratch on a Thinkpad T420s with NVIDIA Optimus. The BIOS is configured to "Discrete graphics", i.e. Optimus is turned off, and the NVIDIA video card is turned on, and it is the only card visible from Linux. On bootup the machine locks up after grub before I get the decrypt hardware password prompt approximately 9 out of 10 times. In about 1 out of 10 boots, I get to the password prompt, and the machine works as expected afterwards. If I set the acpi=no kernel parameter, booting seems to always work, but I only get one CPU core activated. When booting in recovery mode, I notice that the lockup usually happens in this stretch of kernel initialization: [2.026423] sd 0:0:0:0: [sda] Attached SCSI disk [2.036151] usb 1-1: new high-speed USB device number 2 using ehci_hcd [2.168956] hub 1-1:1.0: USB hub found [2.169240] hub 1-1:1.0: 6 ports detected [2.279887] usb 2-1: new high-speed USB device number 2 using ehci_hcd [2.351789] ata2: SATA link down (SStatus 0 SControl 300) [2.412641] hub 2-1:1.0: USB hub found [2.412923] hub 2-1:1.0: 8 ports detected [2.483714] usb 1-1.3: new full-speed USB device number 3 using ehci_hcd [2.647636] usb 1-1.6: new high-speed USB device number 4 using ehci_hcd [2.679364] ata5: SATA link down (SStatus 0 SControl 300) [2.680465] Freeing unused kernel memory: 924k freed [2.680629] Write protecting the kernel read-only data: 12288k [2.683768] Freeing unused kernel memory: 1596k freed [2.686126] Freeing unused kernel memory: 1188k freed [2.697599] udevd[108]: starting version 175 [2.712918] e1000e: Intel(R) PRO/1000 Network Driver - 1.5.1-k [2.713006] e1000e: Copyright(c) 1999 - 2011 Intel Corporation. [2.713122] e1000e :00:19.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20 [2.713219] e1000e :00:19.0: setting latency timer to 64 [2.713326] e1000e :00:19.0: irq 48 for MSI/MSI-X [2.716222] sdhci: Secure Digital Host Controller Interface driver [2.716312] sdhci: Copyright(c) Pierre Ossman [2.716828] sdhci-pci :05:00.0: SDHCI controller found [1180:e823] (rev 4) [2.717097] sdhci-pci :05:00.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19 [2.717524] sdhci-pci :05:00.0: setting latency timer to 64 [2.717545] mmc0: no vmmc regulator found [2.717789] Registered led device: mmc0:: [2.719020] mmc0: SDHCI controller on PCI [:05:00.0] using DMA [2.729653] acpi device:0a: registered as cooling_device4 [2.729856] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:09/LNXVIDEO:01/input/input4 [2.730052] ACPI: Video Device [VID1] (multi-head: yes rom: yes post: no) [2.815419] usb 2-1.4: new high-speed USB device number 3 using ehci_hcd [2.902710] e1000e :00:19.0: eth0: (PCI Express:2.5GT/s:Width x1) f0:de:f1:c2:bb:67 [2.902821] e1000e :00:19.0: eth0: Intel(R) PRO/1000 Network Connection [2.902941] e1000e :00:19.0: eth0: MAC: 10, PHY: 11, PBA No: 1000FF-0FF [8.462440] EXT4-fs (dm-1): mounted filesystem with ordered data mode. Opts: (null) [8.839798] udevd[400]: starting version 175 After observing a few hundred boot lockups, it would appear that the lockup can happen after either the USB subsystem started its initialization, after the e1000e network card initialization or after the MMC initialization. For all I know, these things run in parallell, and somebody (NVIDIA?) is not holding the appropriate locks, thus interfering with the other initialization code. The lockup mostly results state where the kernel complains about USB reset errors approx every second: [ timestamp] hub 1-1:1.0: hub_port_status failed (err = -100) [ timestamp] hub 1-1.5:1.0: hub_port_status failed (err = -100) [ timestamp+1sec ] hub 1-1:1.0: cannot reset port 6 (err = -110) [ timestamp+2sec ] hub 1-1:1.0: cannot reset port 6 (err = -110) .. etc This problem is not really new; I've experienced it for a long while, but the likelihood of a successful boot seems to have dropped lot (from 1 in 2-3 to 1 in 10) after updating to kernel 3.2.0-44 + ubuntu drivers 304.88-0ubuntu0.0.2. (If I boot the machine using the Intel graphics card, this never happens.) ** Affects: nvidia-graphics-drivers (Ubuntu) Importance: Undecided Status: New -- 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/1185340 Title: Precise only boots ~1 in 10 times with the NVIDIA driver enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1185340/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpa
[Ubuntu-x-swat] [Bug 1171192] Re: Ubuntu 13.04 Beta 2- Intel HD Graphics 3000 - No screen
See http://forums.opensuse.org/english/get-technical-help-here/install- boot-login/466700-intel-graphics-black-screen-problem-update.html It may fix your probleme by just adding acpi_backlight=vendor to grub -- 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/1171192 Title: Ubuntu 13.04 Beta 2- Intel HD Graphics 3000 - No screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1171192/+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 1185299] Re: X crashes when attaching a monitor using the DVI interface
** Attachment added: "Xorg.0.log with the crash (monitor attached to DVI port)" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1185299/+attachment/3689501/+files/Xorg.0.log -- 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/1185299 Title: X crashes when attaching a monitor using the DVI interface To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1185299/+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 1185299] Re: X crashes when attaching a monitor using the DVI interface
** Attachment added: "Xorg.0.log without the crash (monitor attached to VGA port)" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1185299/+attachment/3689500/+files/Xorg.0.log -- 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/1185299 Title: X crashes when attaching a monitor using the DVI interface To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1185299/+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 1185299] [NEW] X crashes when attaching a monitor using the DVI interface
Public bug reported: I am having problems connecting a monitor to my Lenovo T430 using the DVI interface of the docking station. Starting X fails with a segmentation fault. This does not happen when - no external monitor is connected - the same monitor is connected to the VGA interface of either the docking station or the computer itself (when undocked) I have tested with no success: - changing the output DVI port - booting a different kernel (generic vs. lowlatency) - using "nomodeset" boot setting - connecting a monitor of a different kind I have attached a "bad" log (with the segmentation fault) and a "good" log (when the same monitor is connected to the VGA interface). ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-22.15-lowlatency 3.8.11 Uname: Linux 3.8.0-22-lowlatency x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed May 29 09:51:47 2013 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21f4] NVIDIA Corporation GF108M [NVS 5400M] [10de:0def] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21f4] InstallationDate: Installed on 2013-05-07 (21 days ago) InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: LENOVO 2349I17 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-22-lowlatency root=UUID=19c36375-8b1f-494b-96a4-9b6fcd308b13 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/19/2012 dmi.bios.vendor: LENOVO dmi.bios.version: G1ET73WW (2.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 2349I17 dmi.board.vendor: LENOVO dmi.board.version: Win8 Pro DPK TPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG1ET73WW(2.09):bd10/19/2012:svnLENOVO:pn2349I17:pvrThinkPadT430:rvnLENOVO:rn2349I17:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2349I17 dmi.product.version: ThinkPad T430 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.43-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.1-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.1-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.6-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.7-0ubuntu1 xserver.bootTime: Wed May 29 09:32:06 2013 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) NOUVEAU(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.13.3-0ubuntu6 xserver.video_driver: intel ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring ubuntu ** Attachment added: "Log with the crash" https://bugs.launchpad.net/bugs/1185299/+attachment/3689480/+files/Xorg.0.log -- 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/1185299 Title: X crashes when attaching a monitor using the DVI interface To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1185299/+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 1173503] Re: Xorg freeze
The logs indicate that you encounter a GPU hang, for which I need the /sys/kernel/debug/dri/0/i915_error_state to diagnose. -- 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/1173503 Title: Xorg freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1173503/+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 1185285] Re: [saucy] fails to build against linux 3.9.0
dino99, bug 1185253 seems unrelated to me. That doesn't fail because of a missing version.h, that just simply needs porting to 3.9. -- 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/1185285 Title: [saucy] fails to build against linux 3.9.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1185285/+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 1185285] Re: [saucy] fails to build against linux 3.9.0
Only to catch your attention (does not know if dkms has to be blamed), i got that one also, that seems close: https://bugs.launchpad.net/ubuntu/+source/lttng-modules/+bug/1185253 -- 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/1185285 Title: [saucy] fails to build against linux 3.9.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1185285/+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
