[Ubuntu-x-swat] [Bug 1998929] Re: Compatibility issues with intel-opencl-icd_22.14.22890-1_amd64 build
Additionnal issue opened on the SYCL side: https://github.com/intel/llvm/issues/7659 ** Bug watch added: github.com/intel/llvm/issues #7659 https://github.com/intel/llvm/issues/7659 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to intel-compute-runtime in Ubuntu. https://bugs.launchpad.net/bugs/1998929 Title: Compatibility issues with intel-opencl-icd_22.14.22890-1_amd64 build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-compute-runtime/+bug/1998929/+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 1998929] [NEW] Compatibility issues with intel-opencl-icd_22.14.22890-1_amd64 build
Public bug reported: I'm trying to run SYCL-based software on gpu (using dpctl:https://github.com/IntelPython/dpctl) and it requires the compute runtime to be installed to detect gpu devices. The issue I have is that using the ubuntu build (installed with: `apt- get install intel-opencl-icd`) the gpu devices are not detected. The same version downloaded from github: https://github.com/intel/compute- runtime/releases/tag/22.14.22890 works. But for end users it's much easier to use the build available in the official repositories. What differences in those two builds could explain this ? I don't know if this is a bug on the SYCL side or something related to customization of the ubuntu build. I've mirrored the issue on intel/compute-runtime github: https://github.com/intel/compute- runtime/issues/588 . Considering also opening an issue on https://github.com/intel/llvm/ . Tested on ubuntu focal and ubuntu jammy, using official latest ubuntu docker images. ** Affects: intel-compute-runtime (Ubuntu) Importance: Undecided Status: New ** Tags: driver gpu intel intel-runtime opencl -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to intel-compute-runtime in Ubuntu. https://bugs.launchpad.net/bugs/1998929 Title: Compatibility issues with intel-opencl-icd_22.14.22890-1_amd64 build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-compute-runtime/+bug/1998929/+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 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Tested on last manjaro k5.8, and currently on debian sid unstable (k5.8.0-1)and same issue with touchpad. Same results as above... Lenovo Gaming 3 15ARH05 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 To manage notifications about this bug go to: https://bugs.launchpad.net/pop-os/+bug/1887190/+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 1713313] Re: Unable to launch pkexec'ed applications on Wayland session
@aquina I was just pointing ufw vs firewalld as it is the app (gufw) that drove me here. I also wanted to point out that by adopting Gnome / Systemd / Wayland / ... Ubuntu is now dependant and has to keep up with the new upstream, that tends to be RedHat / Fedora. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xdiagnose in Ubuntu. https://bugs.launchpad.net/bugs/1713313 Title: Unable to launch pkexec'ed applications on Wayland session To manage notifications about this bug go to: https://bugs.launchpad.net/backintime/+bug/1713313/+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 1713313] Re: Unable to launch pkexec'ed applications on Wayland session
Are there any plans to move forward and try to coordinate applications rewrite/adaptation ? I'm not in love with wayland, but isolating graphical applications for each other seems a legitimate concern (see https://theinvisiblethings.blogspot.com/2011/04/linux-security-circus-on-gui-isolation.html for example). Now that Ubuntu has given up on Wayland by default, I'm afraid there is now less incentive for transitioning to the security model wayland wants to impose. So what? Should we use firewalld instead of ufw? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xdiagnose in Ubuntu. https://bugs.launchpad.net/bugs/1713313 Title: Unable to launch pkexec'ed applications on Wayland session To manage notifications about this bug go to: https://bugs.launchpad.net/backintime/+bug/1713313/+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 1508870] Re: Font corruption (gets bold) when scrolling in Eclipse
** Summary changed: - Font corruption (gets blod) when scrolling in Eclipse + Font corruption (gets bold) when scrolling in Eclipse -- 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/1508870 Title: Font corruption (gets bold) when scrolling in Eclipse To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1508870/+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 1508870] [NEW] Font corruption (gets blod) when scrolling in Eclipse
Public bug reported: After scrolling in Eclipse, some lines appear as "bold" on screen. If the mouse goes over the bold text, it comes back to normal. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Thu Oct 22 12:06:25 2015 DistUpgraded: Fresh install DistroCodename: wily DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.4, 4.2.0-14-generic, x86_64: installed virtualbox, 5.0.4, 4.2.0-16-generic, x86_64: installed 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:21fb] InstallationDate: Installed on 2015-10-04 (17 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002) MachineType: LENOVO 2353CTO ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-16-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro noprompt persistent kaslr threadirqs quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-intel UdevLog: Error: [Errno 2] Aucun fichier ou dossier de ce type: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/14/2014 dmi.bios.vendor: LENOVO dmi.bios.version: G7ETA0WW (2.60 ) dmi.board.asset.tag: Not Available dmi.board.name: 2353CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG7ETA0WW(2.60):bd05/14/2014:svnLENOVO:pn2353CTO:pvrThinkPadT430s:rvnLENOVO:rn2353CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2353CTO dmi.product.version: ThinkPad T430s dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Thu Oct 22 09:13:08 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 12876 vendor SEC xserver.version: 2:1.17.2-1ubuntu9 ** Affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu wily ** Attachment added: "example of bold text (contexts-available for example)" https://bugs.launchpad.net/bugs/1508870/+attachment/4502252/+files/bold-fonts.png -- 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/1508870 Title: Font corruption (gets blod) when scrolling in Eclipse To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1508870/+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 1430230] Re: Log flooding with warning message when using linux-lowlatency kernel
It seems to be fixed as of version 2:2.99.917-1~exp1ubuntu2.1 of xserver-xorg-vieo-intel. I don't get the warnings anymore, be it with threadirqs parameter and generic kernel, or with lowlatency 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/1430230 Title: Log flooding with warning message when using linux-lowlatency kernel To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1430230/+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 1430230] Re: Log flooding with warning message when using linux-lowlatency kernel
Hope this can land in Vivid. Not using thread irqs certainly works this bug around, but then playing audio on bluetooth is at best flaky ! -- 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/1430230 Title: Log flooding with warning message when using linux-lowlatency kernel To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1430230/+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 1430230] Re: Log flooding with warning message when using linux-lowlatency kernel
I'm not really entitled to make any suggestion, but One hundred papercuts / importance low seems a little bit understated to me: this is literally flooding the log, resulting in system slowdown, unusable logs and intense disk activity (bye SSDs). -- 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/1430230 Title: Log flooding with warning message when using linux-lowlatency kernel To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1430230/+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 1430230] [NEW] Log flooding with warning message when using linux-lowlatency kernel
Public bug reported: In Vivid, when booting with lowlatency kernel (and possibly with generic kernel and threadirqs), Intel graphics driver will flood the logs with warning: Mar 10 09:35:43 franck-ThinkPad-T430s kernel: [ 2216.247652] [ cut here ] Mar 10 09:35:43 franck-ThinkPad-T430s kernel: [ 2216.247683] WARNING: CPU: 3 PID: 659 at /build/buildd/linux-3.19.0/drivers/gpu/drm/i915/intel_display.c:9705 intel_check_page_flip+0xa2/0xf0 [i915]() Mar 10 09:35:43 franck-ThinkPad-T430s kernel: [ 2216.247685] WARN_ON(!in_irq()) Mar 10 09:35:43 franck-ThinkPad-T430s kernel: [ 2216.247686] Modules linked in: md4 nls_utf8 cifs fscache msr acpi_call(OE) xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 bridge stp llc ebtable_filter ebtables pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) binfmt_misc rfcomm bnep nls_iso8859_1 hid_apple intel_rapl iosf_mbi x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel uvcvideo kvm videobuf2_vmalloc videobuf2_memops crct10dif_pclmul i915 videobuf2_core crc32_pclmul ghash_clmulni_intel v4l2_common videodev aesni_intel media aes_x86_64 btusb lrw gf128mul glue_helper bluetooth ablk_helper cryptd arc4 snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic iwldvm dm_multipath scsi_dh snd_hda_intel mac80211 snd_hda_controller snd_hda_codec joydev snd_hwdep serio_raw drm_kms_helper iwlwifi snd_pcm thinkpad_acpi cfg80211 snd_seq_midi snd_seq_midi_event nvram snd_rawmidi snd_seq ip6t_REJECT nf_reject_ipv6 snd_seq_devi ce nf_log_ipv6 lpc_ich snd_timer drm shpchp xt_hl snd mei_me nf_conntrack_ipv6 mei nf_defrag_ipv6 i2c_algo_bit ip6t_rt soundcore wmi video mac_hid ipt_REJECT nf_reject_ipv4 nf_log_ipv4 nf_log_common xt_LOG xt_multiport xt_limit xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 xt_addrtype xt_conntrack ip6table_filter ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast cuse nf_nat_ftp nf_nat nf_conntrack_ftp parport_pc nf_conntrack ppdev iptable_filter ip_tables lp x_tables parport autofs4 btrfs xor raid6_pq hid_generic usbhid hid psmouse ahci e1000e sdhci_pci libahci sdhci ptp pps_core Mar 10 09:35:43 franck-ThinkPad-T430s kernel: [ 2216.247768] CPU: 3 PID: 659 Comm: irq/32-i915 Tainted: GW OE 3.19.0-7-lowlatency #7-Ubuntu Mar 10 09:35:43 franck-ThinkPad-T430s kernel: [ 2216.247770] Hardware name: LENOVO 2353CTO/2353CTO, BIOS G7ETA0WW (2.60 ) 05/14/2014 Mar 10 09:35:43 franck-ThinkPad-T430s kernel: [ 2216.247781] c0be7010 88042a353c98 817c5402 88043e2cfd78 Mar 10 09:35:43 franck-ThinkPad-T430s kernel: [ 2216.247784] 88042a353ce8 88042a353cd8 8107738a 88042a353cd8 Mar 10 09:35:43 franck-ThinkPad-T430s kernel: [ 2216.247786] 880428f3f000 880428f5e800 Mar 10 09:35:43 franck-ThinkPad-T430s kernel: [ 2216.247788] Call Trace: Mar 10 09:35:43 franck-ThinkPad-T430s kernel: [ 2216.247795] [817c5402] dump_stack+0x4c/0x6e Mar 10 09:35:43 franck-ThinkPad-T430s kernel: [ 2216.247805] [8107738a] warn_slowpath_common+0x8a/0xc0 Mar 10 09:35:43 franck-ThinkPad-T430s kernel: [ 2216.247814] [81077406] warn_slowpath_fmt+0x46/0x50 Mar 10 09:35:43 franck-ThinkPad-T430s kernel: [ 2216.247830] [c0b92482] intel_check_page_flip+0xa2/0xf0 [i915] Mar 10 09:35:43 franck-ThinkPad-T430s kernel: [ 2216.247843] [c0b5f4d8] ironlake_irq_handler+0x428/0x1010 [i915] Mar 10 09:35:43 franck-ThinkPad-T430s kernel: [ 2216.247847] [8109b55d] ? finish_task_switch+0x5d/0x100 Mar 10 09:35:43 franck-ThinkPad-T430s kernel: [ 2216.247854] [810cfc60] ? irq_thread_fn+0x50/0x50 Mar 10 09:35:43 franck-ThinkPad-T430s kernel: [ 2216.247858] [810cfc8d] irq_forced_thread_fn+0x2d/0x70 Mar 10 09:35:43 franck-ThinkPad-T430s kernel: [ 2216.247861] [810d01af] irq_thread+0x11f/0x150 Mar 10 09:35:43 franck-ThinkPad-T430s kernel: [ 2216.247865] [810cfd00] ? wake_threads_waitq+0x30/0x30 Mar 10 09:35:43 franck-ThinkPad-T430s kernel: [ 2216.247868] [810d0090] ? irq_thread_check_affinity+0x90/0x90 Mar 10 09:35:43 franck-ThinkPad-T430s kernel: [ 2216.247871] [81095bc9] kthread+0xc9/0xe0 Mar 10 09:35:43 franck-ThinkPad-T430s kernel: [ 2216.247874] [81095b00] ? kthread_create_on_node+0x1c0/0x1c0 Mar 10 09:35:43 franck-ThinkPad-T430s kernel: [ 2216.247877] [817cc33c] ret_from_fork+0x7c/0xb0 Mar 10 09:35:43 franck-ThinkPad-T430s kernel: [ 2216.247880] [81095b00] ? kthread_create_on_node+0x1c0/0x1c0 Mar 10 09:35:43 franck-ThinkPad-T430s kernel: [ 2216.247883] ---[ end trace fa4376848cde145f ]--- There seems to be a bug report here https://bugs.freedesktop.org/show_bug.cgi?id=89321 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64
[Ubuntu-x-swat] [Bug 1285811] Re: HDMI/DVI stopped working
@Chris thanks for you quick reply. ...and apologies for bothering you: finally, everything seems to work after I switched the DVI ports on the dock... So it might be a hardware problem, or the software being confused and getting back in order after the config changed... Anyway, I'm closing this bug as I can't sorry reproduce it myself. Sorry for the noise. ** Changed in: xserver-xorg-video-intel (Ubuntu) Status: New = Invalid -- 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/1285811 Title: HDMI/DVI stopped working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1285811/+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 1285811] [NEW] HDMI/DVI stopped working
Public bug reported: Today after upgrading Trusty, my HDMI/DVI second monitor stopped working. This is on a laptop, and the HDMI monitor is connected to the docking station with a DVI/HDMI cable. After latest upgrade, the monitor does not seem to be recognized anymore. Here is the upgrade : Start-Date: 2014-02-27 15:03:15 Commandline: aptdaemon role='role-commit-packages' sender=':1.127' Install: libtasn1-6-dev:amd64 (3.4-3) Upgrade: libservlet3.0-java:amd64 (7.0.50-1, 7.0.52-1), libtasn1-3-dev:amd64 (2.14-3ubuntu1, 3.4-3), libtasn1-6:amd64 (3.4-2, 3.4-3) End-Date: 2014-02-27 15:03:19 Start-Date: 2014-02-27 18:31:27 Commandline: aptdaemon role='role-commit-packages' sender=':1.128' Upgrade: libnux-4.0-common:amd64 (4.0.5+14.04.20140214-0ubuntu1, 4.0.5+14.04.20140226-0ubuntu1), libnux-4.0-0:amd64 (4.0.5+14.04.20140214-0ubuntu1, 4.0.5+14.04.20140226-0ubuntu1), nux-tools:amd64 (4.0.5+14.04.20140214-0ubuntu1, 4.0.5+14.04.20140226-0ubuntu1) End-Date: 2014-02-27 18:31:28 Here is the output of xrandr: Screen 0: minimum 320 x 200, current 1600 x 900, maximum 32767 x 32767 LVDS1 connected primary 1600x900+0+0 (normal left inverted right x axis y axis) 310mm x 174mm 1600x900 60.0*+ 1440x900 59.9 1360x768 59.8 60.0 1152x864 60.0 1024x768 60.0 800x60060.3 56.2 640x48059.9 VGA1 disconnected (normal left inverted right x axis y axis) HDMI1 disconnected (normal left inverted right x axis y axis) DP1 disconnected (normal left inverted right x axis y axis) HDMI2 disconnected (normal left inverted right x axis y axis) DP2 disconnected (normal left inverted right x axis y axis) VIRTUAL1 disconnected (normal left inverted right x axis y axis) What else should I check ? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-12.32-generic 3.13.4 Uname: Linux 3.13.0-12-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Feb 27 19:00:38 2014 DistUpgraded: 2014-01-22 17:41:22,726 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.6, 3.13.0-11-generic, x86_64: installed virtualbox, 4.3.6, 3.13.0-12-generic, x86_64: installed 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:21fb] InstallationDate: Installed on 2013-02-16 (375 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130216) MachineType: LENOVO 2353CTO ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-12-generic root=UUID=bb7483c9-09ca-49c5-9cb5-fd6ecf814340 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-intel UpgradeStatus: Upgraded to trusty on 2014-01-22 (36 days ago) dmi.bios.date: 04/30/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G7ET94WW (2.54 ) dmi.board.asset.tag: Not Available dmi.board.name: 2353CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG7ET94WW(2.54):bd04/30/2013:svnLENOVO:pn2353CTO:pvrThinkPadT430s:rvnLENOVO:rn2353CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2353CTO dmi.product.version: ThinkPad T430s dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11+14.04.20140218-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0~rc1-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0~rc1-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Thu Feb 27 18:56:21 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 12876 vendor SEC xserver.version: 2:1.15.0-1ubuntu6 ** Affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in Ubuntu.
[Ubuntu-x-swat] [Bug 1277143] [NEW] Graphical artifacts in button with some toolkits (eg. in pgadmin)
Public bug reported: After upgrading to latest version of xserver-xorg-video-intel, I see some visual artifacts on the buttons of some of my applications, espacially in the save under dialogs (but probably not only). Some examples are attached. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-intel 2:2.99.909-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-7.26-generic 3.13.1 Uname: Linux 3.13.0-7-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Feb 6 16:44:17 2014 DistUpgraded: 2014-01-22 17:41:22,726 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: acpi-call, 20130623, 3.13.0-7-generic, x86_64: installed virtualbox, 4.3.2, 3.13.0-7-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21fb] InstallationDate: Installed on 2013-02-16 (354 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130216) MachineType: LENOVO 2353CTO ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-7-generic root=UUID=bb7483c9-09ca-49c5-9cb5-fd6ecf814340 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-intel UpgradeStatus: Upgraded to trusty on 2014-01-22 (14 days ago) dmi.bios.date: 04/30/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G7ET94WW (2.54 ) dmi.board.asset.tag: Not Available dmi.board.name: 2353CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG7ET94WW(2.54):bd04/30/2013:svnLENOVO:pn2353CTO:pvrThinkPadT430s:rvnLENOVO:rn2353CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2353CTO dmi.product.version: ThinkPad T430s dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu4 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.0.1-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental 10.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 10.0.1-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.909-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Thu Feb 6 09:59:44 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 12876 vendor SEC xserver.version: 2:1.15.0-1ubuntu2 ** Affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu ** Attachment added: visaul artifact in pgadmin save request dialog https://bugs.launchpad.net/bugs/1277143/+attachment/3971376/+files/Requ%C3%AAte_036.png -- 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/1277143 Title: Graphical artifacts in button with some toolkits (eg. in pgadmin) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1277143/+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 1277143] Re: Graphical artifacts in button with some toolkits (eg. in pgadmin)
Another example ** Attachment added: visual artifact in firefox file chooser https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1277143/+attachment/3971402/+files/firefox-artifact.png -- 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/1277143 Title: Graphical artifacts in button with some toolkits (eg. in pgadmin) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1277143/+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 982889] Re: X trying to start before plymouth has finished using the drm driver
Just a question: what if the no-splash is passed as a boot option ? Or if plymouth is removed ? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/982889 Title: X trying to start before plymouth has finished using the drm driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889/+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 982889] Re: X trying to start before plymouth has finished using the drm driver
I can confirm that adding 'and started plymouth-splash' after the 'and dbus' line in /etc/init/lightdm.conf , as Maarten suggests, does fix the problem for me. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/982889 Title: X trying to start before plymouth has finished using the drm driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889/+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 1159099] [NEW] X fails on boot, but starting lightdm afterwards works
Public bug reported: This was fixed before, but it came back lately... Error in log is: [ 4.748] (EE) No devices detected. [ 4.748] Fatal server error: [ 4.748] no screens found ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-13.23-generic 3.8.3 Uname: Linux 3.8.0-13-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.9.2-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sat Mar 23 11:31:47 2013 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu DkmsStatus: virtualbox, 4.2.8, 3.8.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21fb] InstallationDate: Installed on 2013-02-16 (34 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130216) MachineType: LENOVO 2353CTO MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-13-generic root=UUID=bb7483c9-09ca-49c5-9cb5-fd6ecf814340 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/22/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G7ET91WW (2.51 ) dmi.board.asset.tag: Not Available dmi.board.name: 2353CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG7ET91WW(2.51):bd01/22/2013:svnLENOVO:pn2353CTO:pvrThinkPadT430s:rvnLENOVO:rn2353CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2353CTO dmi.product.version: ThinkPad T430s dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.9~daily13.03.20-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.42-0ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.3-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.3-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu3 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.5-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.6-0ubuntu3b1 xserver.bootTime: Sat Mar 23 11:04:20 2013 xserver.configfile: default xserver.devices: xserver.errors: No devices detected. No devices detected. Please also check the log file at /var/log/Xorg.0.log for additional information. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.13.3-0ubuntu3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 raring ubuntu ** Attachment added: Xorg log on failure https://bugs.launchpad.net/bugs/1159099/+attachment/3591635/+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/1159099 Title: X fails on boot, but starting lightdm afterwards works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1159099/+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 1159099] Re: X fails on boot, but starting lightdm afterwards works
Maybe the bug is related to ligthdm / upstart rather to xorg, refering to comment in bug report https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/799069 ** Package changed: xorg (Ubuntu) = lightdm (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/1159099 Title: X fails on boot, but starting lightdm afterwards works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1159099/+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 982889] Re: X trying to start before plymouth has finished using the drm driver
Just fixed for me, but it seems that last update in Lightdm and / or upstart broke things again. Symptoms are not quite the same, but the issues might be related... Now X fails with these messages: [ 4.746] (WW) xf86OpenConsole: setpgid failed: Operation not permitted [ 4.746] (WW) xf86OpenConsole: setsid failed: Operation not permitted [ 4.748] (WW) Falling back to old probe method for vesa [ 4.748] (WW) Falling back to old probe method for modesetting [ 4.748] (WW) Falling back to old probe method for fbdev [ 4.748] (EE) No devices detected. [ 4.748] Fatal server error: [ 4.748] no screens found I opened bug #1159099 against lightdm (but maybe its a duplicate after all). I also found references to the same type of problems in #799069. All related to a race condition / problem with upstart events between lightdm / plymouth. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/982889 Title: X trying to start before plymouth has finished using the drm driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889/+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 982889] Re: X trying to start before plymouth has finished using the drm driver
The problem(s) seem to be fixed for me. No more boot delay, lightdm starts fine, no console appearing... My boot time is under 10 sec. No warning or anaivalable drm in Xorg.0.log... Kind of miraculous :-) Attached are my logs, in case this matters. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/982889 Title: X trying to start before plymouth has finished using the drm driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889/+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 982889] Re: X trying to start before plymouth has finished using the drm driver
** Attachment added: Xorg.0.log https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889/+attachment/3581229/+files/Xorg.0.log -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/982889 Title: X trying to start before plymouth has finished using the drm driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889/+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 982889] Re: X trying to start before plymouth has finished using the drm driver
@Maarten. Sorry, forgot to attach it and did it on a second post. Here it is. ** Attachment added: Works. https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889/+attachment/3581439/+files/Xorg.0.log -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/982889 Title: X trying to start before plymouth has finished using the drm driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889/+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 982889] Re: X trying to start before plymouth has finished using the drm driver
Here is a Xorg.0.log with new patch. Regarding the whole boot process, I didn't get the 10 sec stale at the very beginning at the boot process that was in my latest bootchart graph... but this might be totally unrelated, I don't know. ** Attachment added: Xorg.0.log https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889/+attachment/3571592/+files/Xorg.0.log -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/982889 Title: X trying to start before plymouth has finished using the drm driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889/+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 982889] Re: X trying to start before plymouth has finished using the drm driver
Here is a Xorg.0.log with new patch (under amd64). Regarding the whole boot process, I didn't get the 10 sec stale at the very beginning at the boot process that was in my latest bootchart graph... but this might be totally unrelated, I don't know. ** Attachment added: Xorg.0.log https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889/+attachment/3571593/+files/Xorg.0.log -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/982889 Title: X trying to start before plymouth has finished using the drm driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889/+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 982889] Re: X trying to start before plymouth has finished using the drm driver
Sorry for duplicate post... can't seem to attach my log. Last try :-) ** Attachment added: Xorg.0.log, PPA at 20130313 https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889/+attachment/3571621/+files/Xorg.0.log -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/982889 Title: X trying to start before plymouth has finished using the drm driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889/+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 982889] Re: X trying to start before plymouth has finished using the drm driver
** Attachment added: Latest Xorg.0.log amd64 https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889/+attachment/3571594/+files/Xorg.0.log -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/982889 Title: X trying to start before plymouth has finished using the drm driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889/+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 982889] Re: X trying to start before plymouth has finished using the drm driver
Here are some materials about what I see happen here: - a video showing how the console shows after plymouth and before X comes back - a bootchart - syslog - Xorg.0.log There is indeed a huge gap (10 seconds) without any activity at the beginning of the boot, maybe not related to X, but still here. Then X will take another 10 sec until lightdm is ready. Does this fit into this bug report ? ** Attachment added: boot sequence video https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889/+attachment/3567857/+files/13030025-1.mp4 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/982889 Title: X trying to start before plymouth has finished using the drm driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889/+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 982889] Re: X trying to start before plymouth has finished using the drm driver
** Attachment added: Xorg.log https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889/+attachment/3567860/+files/Xorg.0.log -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/982889 Title: X trying to start before plymouth has finished using the drm driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889/+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 982889] Re: X trying to start before plymouth has finished using the drm driver
** Attachment added: bootchart https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889/+attachment/3567858/+files/franck-ThinkPad-T430s-raring-20130311-2.png -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/982889 Title: X trying to start before plymouth has finished using the drm driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889/+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 982889] Re: X trying to start before plymouth has finished using the drm driver
** Attachment added: syslog https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889/+attachment/3567859/+files/syslog -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/982889 Title: X trying to start before plymouth has finished using the drm driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889/+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 982889] Re: X trying to start before plymouth has finished using the drm driver
thanks Bryce. One question: this workaround results in a flip-flap between console mode / graphical mode during boot, and a 5 to 20 seconds delay in the boot. This is better than lightdm failing to start, but not the best we can aim... So my question is: should I open another bug report, maybe mentioning EACCESS error code ? Are we just going on with this workaround, waiting for Mir to fix everything (and probably break some also :-) ) ? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/982889 Title: X trying to start before plymouth has finished using the drm driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889/+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 982889] Re: X trying to start before plymouth has finished using the drm driver
Here is my log with latest from PPA. ** Attachment added: Xorg.0.log, PPA at 20130306-0900 https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889/+attachment/3559875/+files/Xorg.0.log -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/982889 Title: X trying to start before plymouth has finished using the drm driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889/+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 982889] Re: X trying to start before plymouth has finished using the drm driver
Still no amd64... From the PPA status page: Build status [CANCELLED] Cancelled build Started on 2013-03-03 Finished 8 hours ago (took 20 hours, 38 minutes, 42.3 seconds) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/982889 Title: X trying to start before plymouth has finished using the drm driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889/+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 982889] Re: X trying to start before plymouth has finished using the drm driver
I have compiled xorg-server from PPA localy. So now I have tried it, and kind of works. Not really satisfactory, although. What happens is that lightdm end up starting, BUT in the meantime, I have a TTY console showing off (ie no plymouth), and it takes a looong time. Here is the log of such a case. ** Attachment added: Xorg log, kind of works https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889/+attachment/3556312/+files/Xorg.0.log -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/982889 Title: X trying to start before plymouth has finished using the drm driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889/+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 982889] Re: X trying to start before plymouth has finished using the drm driver
Build for amd64 running for 12 hours and an half, and ils still ongoing... ils that expected ?? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/982889 Title: X trying to start before plymouth has finished using the drm driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889/+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 982889] Re: X trying to start before plymouth has finished using the drm driver
I was quite sure I activated the PPA, and it failed. But looking at the version in Xorg.0.log, it seems I didn't get the right version. I did not pin any specific version... Looking at what is installed, I only have xerver-common coming from the PPA... And looking at the PPA web page, it seems that amd64 build was cancelled. So, am I wrong, or is mad64 build missing from the PPA ? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/982889 Title: X trying to start before plymouth has finished using the drm driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889/+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 982889] Re: X trying to start before plymouth has finished using the drm driver
Sorry, wrong attachment file extension... here it is. ** Attachment added: Failed with PPA https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889/+attachment/3552485/+files/Xorg.0.log -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/982889 Title: X trying to start before plymouth has finished using the drm driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889/+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 982889] Re: X trying to start before plymouth has finished using the drm driver
Tested the PPA: it still fails here. Attached is the log... I'm availalbe to do test whatever is needed. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/982889 Title: X trying to start before plymouth has finished using the drm driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889/+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 982889] Re: X trying to start before plymouth has finished using the drm driver
Yes, SSD too here. but I guess this ain't extraordinary nowdays... Also this most probably has an impact, as it seems to be a race condiction... -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/982889 Title: X trying to start before plymouth has finished using the drm driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889/+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 982889] Re: X trying to start before plymouth has finished using the drm driver
I also just had a success on rebooting ! Here is the relevant Xorg.0.log. Hopes that helps. ** Attachment added: Successful Xorg.0.log on reboot https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889/+attachment/3549545/+files/Xorg.0.log.ok -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/982889 Title: X trying to start before plymouth has finished using the drm driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889/+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 1131134] Re: Visual artifacts are displayed with intel video driver (Ivy bridge)
Note for those (like me) that are not so much into xorg: IVB stands for Intel Ivy Bridge. -- 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/1131134 Title: Visual artifacts are displayed with intel video driver (Ivy bridge) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1131134/+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 1131134] Re: Visual artifacts are displayed with intel video driver (Ivy bridge)
Here is a screenshot showing the problem. The problem is triggered quite frequently with the copy window of nautilus... ** Attachment added: Artifact in display https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1131134/+attachment/3539852/+files/artifact.png -- 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/1131134 Title: Visual artifacts are displayed with intel video driver (Ivy bridge) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1131134/+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 1131134] [NEW] Visual artifacts are displayed with intel video driver (Ivy bridge)
Public bug reported: From time to time, visual artifacts are poluting the display using Intel driver in raring. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xserver-xorg-video-intel 2:2.21.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-7.14-generic 3.8.0 Uname: Linux 3.8.0-7-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.8-0ubuntu4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Thu Feb 21 11:28:04 2013 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu DkmsStatus: virtualbox, 4.1.22, 3.8.0-7-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21fb] InstallationDate: Installed on 2013-02-16 (4 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130216) MachineType: LENOVO 2353CTO MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-7-generic root=UUID=bb7483c9-09ca-49c5-9cb5-fd6ecf814340 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-intel UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/22/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G7ET91WW (2.51 ) dmi.board.asset.tag: Not Available dmi.board.name: 2353CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG7ET91WW(2.51):bd01/22/2013:svnLENOVO:pn2353CTO:pvrThinkPadT430s:rvnLENOVO:rn2353CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2353CTO dmi.product.version: ThinkPad T430s dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.9~daily13.02.19-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.42-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.2-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.2-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.6-0ubuntu3 xserver.bootTime: Thu Feb 21 09:46:55 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.13.2-0ubuntu2 xserver.video_driver: intel ** Affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 raring running-unity ubuntu -- 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/1131134 Title: Visual artifacts are displayed with intel video driver (Ivy bridge) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1131134/+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 1131134] Re: Visual artifacts are displayed with intel video driver (Ivy bridge)
I can always (almost always ?) trigger the bug with the following procedure: 1) copy some directory from one drive to another (must be big enough to have nautilus copy window show) 2) the cancel button (a red button on the right side) has a black square on its upper right corner Once this has been triggered, the restart (reboot ? Redémarrer in french) button in the restart/reboot dialog has the same problem. If the mouse pointer goes uppon the artifact, it will disappear. -- 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/1131134 Title: Visual artifacts are displayed with intel video driver (Ivy bridge) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1131134/+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 1129220] Re: Fails to boot to X, but starting lightdm afterward works
Finally this is not a duplicate of #982889, although it belongs to the same class of race condition in X bugs. So I removed duplicate info. ** This bug is no longer a duplicate of bug 982889 X trying to start before plymouth has finished using the drm driver -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1129220 Title: Fails to boot to X, but starting lightdm afterward works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1129220/+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 982889] Re: X trying to start before plymouth has finished using the drm driver
Ok, I reopen bug report #1129220 as it is not an exact duplicate... -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/982889 Title: X trying to start before plymouth has finished using the drm driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889/+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 982889] Re: X trying to start before plymouth has finished using the drm driver
@Bryce: Chris Wilson commented on bug #1129220 saying both bugs are really related. I quote: It is that bug. What's changed in the meantime is Xorg now has a platform probe first so hits the error even earlier. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/982889 Title: X trying to start before plymouth has finished using the drm driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889/+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 1129220] Re: Fails to boot to X, but starting lightdm afterward works
*** This bug is a duplicate of bug 982889 *** https://bugs.launchpad.net/bugs/982889 Thanks Chris. After searching a bit, I guess my bug is a duplicate of #982889. Notice this is concomitent with me upgrading my SSD to a faster one (840pro). Might explain why I now meet the race condition... ** This bug has been marked a duplicate of bug 982889 X trying to start before plymouth has finished using the drm driver -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1129220 Title: Fails to boot to X, but starting lightdm afterward works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1129220/+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 982889] Re: X trying to start before plymouth has finished using the drm driver
Maybe this is related ??? http://cgit.freedesktop.org/~airlied/linux/commit/?h=drm- nextid=735dc0d1e29329ff34ec97f66e130cce481c9607 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/982889 Title: X trying to start before plymouth has finished using the drm driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889/+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 982889] Re: X trying to start before plymouth has finished using the drm driver
I have just install xserver-common from the PPA, but it did not solve the issue here. Here is my Xorg.0.log on failure. ** Attachment added: Xorg.0.log https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889/+attachment/3536867/+files/Xorg.0.log -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/982889 Title: X trying to start before plymouth has finished using the drm driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889/+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 1129220] [NEW] Fails to boot to X, but starting lightdm afterward works
Public bug reported: I'm using a laptop with an HD4000 graphics cards. It worked perfectly on Quantal. After upgrading to raring, X stopped working on boot. But iIf I switch to a console and issue 'sudo start ligthdm', things work. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xserver-xorg-video-intel 2:2.21.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-6.13-generic 3.8.0-rc7 Uname: Linux 3.8.0-6-generic x86_64 .tmp.unity.support.test.0: .tmp.unity.support.test.1: ApportVersion: 2.8-0ubuntu4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Feb 18 16:54:14 2013 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu DkmsStatus: virtualbox, 4.1.22, 3.8.0-6-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21fb] InstallationDate: Installed on 2013-02-16 (1 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130216) MachineType: LENOVO 2353CTO MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-6-generic root=UUID=bb7483c9-09ca-49c5-9cb5-fd6ecf814340 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-intel UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/22/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G7ET91WW (2.51 ) dmi.board.asset.tag: Not Available dmi.board.name: 2353CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG7ET91WW(2.51):bd01/22/2013:svnLENOVO:pn2353CTO:pvrThinkPadT430s:rvnLENOVO:rn2353CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2353CTO dmi.product.version: ThinkPad T430s dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.9~daily13.02.08-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.42-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.2-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.2-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.6-0ubuntu2 xserver.bootTime: Mon Feb 18 16:41:57 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.13.2-0ubuntu2 xserver.video_driver: intel ** Affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 raring running-unity ubuntu -- 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/1129220 Title: Fails to boot to X, but starting lightdm afterward works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1129220/+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 1129220] Re: Fails to boot to X, but starting lightdm afterward works
Here is the Xorg.0.log file just after it fails. Error lines are: [ 8.460] (EE) Screen 0 deleted because of no matching config section. [ 8.460] (II) UnloadModule: vesa [ 8.460] (EE) Screen 0 deleted because of no matching config section. [ 8.460] (II) UnloadModule: modesetting [ 8.460] Fatal server error: [ 8.460] Cannot run in framebuffer mode. Please specify busIDsfor all framebuffer devices [ 8.460] [ 8.460] (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. [ 8.460] (EE) Please also check the log file at /var/log/Xorg.0.log for additional information. [ 8.460] (EE) [ 8.535] Server terminated with error (1). Closing log file. ** Attachment added: Failing X log https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1129220/+attachment/3535025/+files/Xorg.0.0log.erreur -- 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/1129220 Title: Fails to boot to X, but starting lightdm afterward works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1129220/+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 1129220] Re: Fails to boot to X, but starting lightdm afterward works
Here is a Xorg.0.log after a successful 'sudo start lightdm'. ** Attachment added: Successful Xorg.0.log https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1129220/+attachment/3535131/+files/Xorg.0.log -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1129220 Title: Fails to boot to X, but starting lightdm afterward works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1129220/+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 847967] Re: A minimized window 'remains' behind on the desktop if /apps/compiz-1/plugins/unityshell/screen0/options/show_minimized_windows is set to true
@shanekpiper: Yes. This is behaviour I'm seeing also, and I decided this bug report was corresponding. I hope this is the case :-) Waiting for xorg-server - 2:1.10.4-1ubuntu2 to show up in my update- manager... -- 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/847967 Title: A minimized window 'remains' behind on the desktop if /apps/compiz-1/plugins/unityshell/screen0/options/show_minimized_windows is set to true To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/847967/+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 655032] Re: Latest update in nvidia-current broke my customEDID option
nvidia driver shipping in Natty fixes the problem (in fact custom edid is not needed anymore). ** Changed in: nvidia-graphics-drivers (Ubuntu) Status: New = 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/655032 Title: Latest update in nvidia-current broke my customEDID option ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 629516] Re: edid cannot be read on Sony VPCCW2S1E and nouveau fails
Latest upgrade (alpha3) did fix the issue (both the edid and the BIT loadval problems). Closing the bug. ** Changed in: xserver-xorg-video-nouveau (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in ubuntu. https://bugs.launchpad.net/bugs/629516 Title: edid cannot be read on Sony VPCCW2S1E and nouveau fails ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 629516] Re: edid cannot be read on Sony VPCCW2S1E and nouveau fails
Trying latest (nightly build) natty, I now get this error : [drm] nouveau Pointer to BIT loadval table invalid So unless this is some other problem showing up, the fix does not seem to work here. ** Changed in: xserver-xorg-video-nouveau (Ubuntu) Status: Fix Released = 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/629516 Title: edid cannot be read on Sony VPCCW2S1E and nouveau fails ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 660829] Re: [rv515] screen flickers every 5 seconds
i confirm i too have flickers every 10 seconds on ati x1300 card on dual monitors with ubuntu10.10 -- [rv515] screen flickers every 5 seconds https://bugs.launchpad.net/bugs/660829 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 655032] [NEW] Latest update in nvidia-current broke my customEDID option
Public bug reported: Upgrading from nvidia-current-256.53-0ubuntu3 to nvidia- current-260.19.06-0ubuntu1 broke my system. I am using the customEDID option of the driver to provide the EDID, as my Sony VPCCW2S1E laptop has a somehow broken EDID. If I don't, when X starts, screen becomes black (off). (See https://bugs.launchpad.net/nouveau/+bug/629516 for a bug report on the same EDID problem with nouveau video driver.) Attached is my /etc/X11/xorg.conf file. With 260.19.06, the option seems to be ignored... Downgrading to 256.53 made my system usable again. ** Affects: nvidia-graphics-drivers (Ubuntu) Importance: Undecided Status: New -- Latest update in nvidia-current broke my customEDID option https://bugs.launchpad.net/bugs/655032 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 655032] Re: Latest update in nvidia-current broke my customEDID option
** Attachment added: xorg.conf with customEDID option https://bugs.edge.launchpad.net/bugs/655032/+attachment/1672824/+files/xorg.conf -- Latest update in nvidia-current broke my customEDID option https://bugs.launchpad.net/bugs/655032 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 629516] Re: edid cannot be read on Sony VPCCW2S1E and nouveau fails
I have tried the xorg-edgers ppa, where xserver-xorg-video-nouveau is slightly newer than that of Maverick (1:0.0.16+git20100827 vs git20100805), but it still fails. I guess the fix comes in the kernel level part of the driver, where nouveau git is using 2.6.36-rc3. So I might have to wait for 11.04 to get any chance to see nouveau working on that laptop... Until then I guess I'll have to stick to NVidia proprietary blob :( -- edid cannot be read on Sony VPCCW2S1E and nouveau fails https://bugs.launchpad.net/bugs/629516 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 629516] Re: edid cannot be read on Sony VPCCW2S1E and nouveau fails
The last comment in upstream bug report suggests that the latest upstram nouveau driver can handle this case of unreadable EDID. Is there a way to test latest driver in Ubuntu 10.10 beta ? Is there a change this get into Ubuntu 10.10 final release ? ** Bug watch added: freedesktop.org Bugzilla #30086 http://bugs.freedesktop.org/show_bug.cgi?id=30086 ** Also affects: nouveau via http://bugs.freedesktop.org/show_bug.cgi?id=30086 Importance: Unknown Status: Unknown -- edid cannot be read on Sony VPCCW2S1E and nouveau fails https://bugs.launchpad.net/bugs/629516 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 629516] [NEW] edid cannot be read on Sony VPCCW2S1E and nouveau fails
Public bug reported: Binary package hint: xserver-xorg-video-nouveau Edid on this laptop cannot be read, and consequently nouveau driver will have a black screen. get-edid: get-edid version 2.0.0 Performing real mode VBE call Interrupt 0x10 ax=0x4f00 bx=0x0 cx=0x0 Function supported Call successful VBE version 300 VBE string at 0x11100 NVIDIA VBE/DDC service about to be called Report DDC capabilities Performing real mode VBE call Interrupt 0x10 ax=0x4f15 bx=0x0 cx=0x0 Function supported Call successful Monitor and video card combination does not support DDC1 transfers Monitor and video card combination does not support DDC2 transfers 0 seconds per 128 byte EDID block transfer Screen is not blanked during DDC transfer Reading next EDID block VBE/DDC service about to be called Read EDID Performing real mode VBE call Interrupt 0x10 ax=0x4f15 bx=0x1 cx=0x0 Function supported Call failed The EDID data should not be trusted as the VBE call failed Error: output block unchanged Notice that NVidia proprietary driver also fails the same way, but it has a workaround with the custom edid option. Option CustomEDID DFP-0:/etc/X11/SNY05FA.bin Nouveau driver does not seem to have such option. ** Affects: xserver-xorg-video-nouveau (Ubuntu) Importance: Undecided Status: New -- edid cannot be read on Sony VPCCW2S1E and nouveau fails https://bugs.launchpad.net/bugs/629516 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 575902] [NEW] package fglrx (not installed) failed to install/upgrade: context : update from ubuntu 9.10 to 10.4
Public bug reported: update from 9.10 to 10.4 failed ProblemType: Package DistroRelease: Ubuntu 10.04 Package: fglrx (not installed) ProcVersionSignature: Ubuntu 2.6.31-21.59-generic Uname: Linux 2.6.31-21-generic i686 NonfreeKernelModules: fglrx Architecture: i386 Date: Wed May 5 18:29:12 2010 DkmsStatus: ErrorMessage: ErrorMessage: aucun paquet nommé « fglrx » n'est installé, configuration impossible MachineType: Packard Bell NEC 000 ProcCmdLine: root=UUID=fb266427-904f-4483-8a0d-8d467922c3bf ro xforcevesa quiet splash SourcePackage: fglrx-installer Title: package fglrx (not installed) failed to install/upgrade: dmi.bios.date: 04/20/2004 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: V1.6 dmi.board.name: MS-6786 dmi.board.vendor: NEC COMPUTERS INTERNATIONAL dmi.chassis.type: 3 dmi.chassis.vendor: NEC COMPUTERS INTERNATIONAL dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrV1.6:bd04/20/2004:svnPackardBellNEC:pn000:pvrP842022802:rvnNECCOMPUTERSINTERNATIONAL:rnMS-6786:rvr:cvnNECCOMPUTERSINTERNATIONAL:ct3:cvr5IAF: dmi.product.name: 000 dmi.product.version: P842022802 dmi.sys.vendor: Packard Bell NEC glxinfo: Error: couldn't find RGB GLX visual or fbconfig name of display: :0.0 system: distro: Ubuntu codename: lucid architecture: i686 kernel: 2.6.31-21-generic ** Affects: fglrx-installer (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 lucid -- package fglrx (not installed) failed to install/upgrade: context : update from ubuntu 9.10 to 10.4 https://bugs.launchpad.net/bugs/575902 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 575902] Re: package fglrx (not installed) failed to install/upgrade: context : update from ubuntu 9.10 to 10.4
** Attachment added: BootDmesg.txt http://launchpadlibrarian.net/47883627/BootDmesg.txt ** Attachment added: CurrentDmesg.txt http://launchpadlibrarian.net/47883628/CurrentDmesg.txt ** Attachment added: GdmLog.txt http://launchpadlibrarian.net/47883629/GdmLog.txt ** Attachment added: GdmLog1.txt http://launchpadlibrarian.net/47883630/GdmLog1.txt ** Attachment added: GdmLog2.txt http://launchpadlibrarian.net/47883631/GdmLog2.txt ** Attachment added: Lspci.txt http://launchpadlibrarian.net/47883632/Lspci.txt ** Attachment added: Lsusb.txt http://launchpadlibrarian.net/47883633/Lsusb.txt ** Attachment added: PciDisplay.txt http://launchpadlibrarian.net/47883634/PciDisplay.txt ** Attachment added: ProcCpuinfo.txt http://launchpadlibrarian.net/47883635/ProcCpuinfo.txt ** Attachment added: ProcInterrupts.txt http://launchpadlibrarian.net/47883636/ProcInterrupts.txt ** Attachment added: ProcModules.txt http://launchpadlibrarian.net/47883637/ProcModules.txt ** Attachment added: RelatedPackageVersions.txt http://launchpadlibrarian.net/47883638/RelatedPackageVersions.txt ** Attachment added: UdevDb.txt http://launchpadlibrarian.net/47883639/UdevDb.txt ** Attachment added: UdevLog.txt http://launchpadlibrarian.net/47883640/UdevLog.txt ** Attachment added: VarLogDistupgradeAptlog.gz http://launchpadlibrarian.net/47883641/VarLogDistupgradeAptlog.gz ** Attachment added: VarLogDistupgradeApttermlog.gz http://launchpadlibrarian.net/47883642/VarLogDistupgradeApttermlog.gz ** Attachment added: VarLogDistupgradeLspcitxt.gz http://launchpadlibrarian.net/47883643/VarLogDistupgradeLspcitxt.gz ** Attachment added: VarLogDistupgradeMainlog.gz http://launchpadlibrarian.net/47883644/VarLogDistupgradeMainlog.gz ** Attachment added: VarLogDistupgradeSystemstatetargz.gz http://launchpadlibrarian.net/47883645/VarLogDistupgradeSystemstatetargz.gz ** Attachment added: VarLogDistupgradeTermlog.gz http://launchpadlibrarian.net/47883646/VarLogDistupgradeTermlog.gz ** Attachment added: XorgConf.txt http://launchpadlibrarian.net/47883647/XorgConf.txt ** Attachment added: XorgLog.txt http://launchpadlibrarian.net/47883648/XorgLog.txt ** Attachment added: XorgLogOld.txt http://launchpadlibrarian.net/47883649/XorgLogOld.txt ** Attachment added: Xrandr.txt http://launchpadlibrarian.net/47883650/Xrandr.txt ** Attachment added: dmi.chassis.version.gz http://launchpadlibrarian.net/47883651/dmi.chassis.version.gz ** Attachment added: setxkbmap.txt http://launchpadlibrarian.net/47883652/setxkbmap.txt ** Attachment added: xdpyinfo.txt http://launchpadlibrarian.net/47883653/xdpyinfo.txt ** Attachment added: xkbcomp.txt http://launchpadlibrarian.net/47883654/xkbcomp.txt -- package fglrx (not installed) failed to install/upgrade: context : update from ubuntu 9.10 to 10.4 https://bugs.launchpad.net/bugs/575902 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 419328] Re: [i945gme] attaching external monitor: laptop display is black, external monitor too, with frozen mouse coursor
Hi, I encounter the same problem on a Sony Vaio (SZ4MN) with i945GM. lspci -v 00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller (rev 03) Subsystem: Sony Corporation Device 81e6 Flags: bus master, fast devsel, latency 0, IRQ 16 Memory at f830 (32-bit, non-prefetchable) [size=512K] I/O ports at 1800 [size=8] Memory at d000 (32-bit, prefetchable) [size=256M] Memory at f840 (32-bit, non-prefetchable) [size=256K] Capabilities: access denied Kernel driver in use: i915 Kernel modules: i915 The output in /var/log/message is : Oct 13 09:42:05 franck-laptop kernel: [ 447.870056] i2c-adapter i2c-1: unable to read EDID block. Oct 13 09:42:05 franck-laptop kernel: [ 447.870061] i915 :00:02.0: LVDS-1: no EDID data Oct 13 09:42:05 franck-laptop kernel: [ 447.911682] [drm] TV-12: set mode NTSC 480i 0 Oct 13 09:42:05 franck-laptop kernel: [ 448.054970] [drm] TV-12: set mode NTSC 480i 0 Oct 13 09:42:05 franck-laptop kernel: [ 448.303017] [drm] DAC-6: set mode 17 Oct 13 09:42:05 franck-laptop kernel: [ 600.630104] i915/1D 0 356 2 0x Oct 13 09:42:05 franck-laptop kernel: [ 600.630114] 8800798fdd70 0046 00015580 Oct 13 09:42:05 franck-laptop kernel: [ 600.630123] 88007a3347c0 00015580 00015580 00015580 Oct 13 09:42:05 franck-laptop kernel: [ 600.630131] 00015580 88007a3347c0 00015580 00015580 Oct 13 09:42:05 franck-laptop kernel: [ 600.630139] Call Trace: Oct 13 09:42:05 franck-laptop kernel: [ 600.630154] [81523387] __mutex_lock_slowpath+0xd7/0x160 Oct 13 09:42:05 franck-laptop kernel: [ 600.630161] [81523286] mutex_lock+0x26/0x50 Oct 13 09:42:05 franck-laptop kernel: [ 600.630201] [a00a08d8] i915_gem_retire_work_handler+0x38/0x90 [i915] Oct 13 09:42:05 franck-laptop kernel: [ 600.630223] [a00a08a0] ? i915_gem_retire_work_handler+0x0/0x90 [i915] Oct 13 09:42:05 franck-laptop kernel: [ 600.630232] [8106f725] run_workqueue+0x95/0x170 Oct 13 09:42:05 franck-laptop kernel: [ 600.630239] [8106f8a4] worker_thread+0xa4/0x120 Oct 13 09:42:05 franck-laptop kernel: [ 600.630246] [81074ab0] ? autoremove_wake_function+0x0/0x40 Oct 13 09:42:05 franck-laptop kernel: [ 600.630252] [8106f800] ? worker_thread+0x0/0x120 Oct 13 09:42:05 franck-laptop kernel: [ 600.630258] [810746c6] kthread+0xa6/0xb0 Oct 13 09:42:05 franck-laptop kernel: [ 600.630266] [8101308a] child_rip+0xa/0x20 Oct 13 09:42:05 franck-laptop kernel: [ 600.630272] [81074620] ? kthread+0x0/0xb0 Oct 13 09:42:05 franck-laptop kernel: [ 600.630278] [81013080] ? child_rip+0x0/0x20 Oct 13 09:42:05 franck-laptop kernel: [ 600.630307] Xorg D 0 1110 1085 0x0044 Oct 13 09:42:05 franck-laptop kernel: [ 600.630315] 880076debcb8 0082 880076debc90 00015580 Oct 13 09:42:05 franck-laptop kernel: [ 600.630323] 880076dc9a60 00015580 00015580 00015580 Oct 13 09:42:05 franck-laptop kernel: [ 600.630331] 00015580 880076dc9a60 00015580 00015580 Oct 13 09:42:05 franck-laptop kernel: [ 600.630339] Call Trace: Oct 13 09:42:05 franck-laptop kernel: [ 600.630346] [81523387] __mutex_lock_slowpath+0xd7/0x160 Oct 13 09:42:05 franck-laptop kernel: [ 600.630355] [814240a0] ? sock_aio_write+0x0/0x150 Oct 13 09:42:05 franck-laptop kernel: [ 600.630361] [81523286] mutex_lock+0x26/0x50 Oct 13 09:42:05 franck-laptop kernel: [ 600.630382] [a00a0bc6] i915_gem_throttle_ioctl+0x36/0x90 [i915] Oct 13 09:42:05 franck-laptop kernel: [ 600.630414] [a0066cae] drm_ioctl+0x17e/0x3a0 [drm] Oct 13 09:42:05 franck-laptop kernel: [ 600.630423] [81032419] ? default_spin_lock_flags+0x9/0x10 -- [i945gme] attaching external monitor: laptop display is black, external monitor too, with frozen mouse coursor https://bugs.launchpad.net/bugs/419328 You received this bug notification because you are a member of Ubuntu-X, which is the registrant for xf86-video-intel. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 446686] Re: [i945] Intel i945 lockup on screen switch with compiz
*** This bug is a duplicate of bug 419328 *** https://bugs.launchpad.net/bugs/419328 ** This bug has been marked a duplicate of bug 419328 [i945gme] attaching external monitor: laptop display is black, external monitor too, with frozen mouse coursor -- [i945] Intel i945 lockup on screen switch with compiz https://bugs.launchpad.net/bugs/446686 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
