[Ubuntu-x-swat] [Bug 1231857] Re: [DPMS] Display backlight turns back on almost immediately after being turned off
** Changed in: mir Importance: Undecided => High ** Changed in: xmir Importance: Undecided => High ** Changed in: xorg-server (Ubuntu) Importance: Undecided => High ** Summary changed: - [DPMS] Display backlight turns back on almost immediately after being turned off + [DPMS] [XMir] Display backlight turns back on almost immediately after being turned off -- 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/1231857 Title: [DPMS] [XMir] Display backlight turns back on almost immediately after being turned off To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1231857/+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 1231262] Re: xorg-server (2:1.14.2.901-2ubuntu5) saucy breaks build of intel and ATI drivers
** Changed in: xorg-server (Ubuntu) Status: New => Fix Released -- 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/1231262 Title: xorg-server (2:1.14.2.901-2ubuntu5) saucy breaks build of intel and ATI drivers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1231262/+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 1180881] Re: Touchscreen only works after suspend/resume on Lenovo ideapad P400 Touch
Patches were sent to: http://www.spinics.net/lists/linux-usb/msg94777.html http://www.spinics.net/lists/linux-usb/msg94778.html ** Changed in: hwe-next Status: New => Confirmed ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Changed in: linux (Ubuntu) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: xserver-xorg-input-evdev (Ubuntu) Status: Fix Committed => Invalid ** Changed in: xserver-xorg-input-evdev (Ubuntu) Assignee: AceLan Kao (acelankao) => (unassigned) ** Also affects: hwe-next/saucy Importance: Undecided Status: New ** Also affects: hwe-next/t-series Importance: Undecided Assignee: AceLan Kao (acelankao) Status: Confirmed ** Changed in: hwe-next/saucy Status: New => Confirmed ** Changed in: hwe-next/saucy Assignee: (unassigned) => AceLan Kao (acelankao) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1180881 Title: Touchscreen only works after suspend/resume on Lenovo ideapad P400 Touch To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1180881/+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 1240450] Re: package nvidia-current 195.36.24-0ubuntu1~10.04.3 failed to install/upgrade: nvidia-current kernel module failed to build
*** This bug is a duplicate of bug 576648 *** https://bugs.launchpad.net/bugs/576648 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 576648, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 576648 package nvidia-* failed to install/upgrade: nvidia-* kernel module failed to build (Unable to determine the target kernel version.) -- 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/1240450 Title: package nvidia-current 195.36.24-0ubuntu1~10.04.3 failed to install/upgrade: nvidia-current kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1240450/+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 1240466] Re: package nvidia-current 195.36.24-0ubuntu1~10.04.3 failed to install/upgrade: nvidia-current kernel module failed to build
*** This bug is a duplicate of bug 576648 *** https://bugs.launchpad.net/bugs/576648 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 576648, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 576648 package nvidia-* failed to install/upgrade: nvidia-* kernel module failed to build (Unable to determine the target kernel version.) -- 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/1240466 Title: package nvidia-current 195.36.24-0ubuntu1~10.04.3 failed to install/upgrade: nvidia-current kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1240466/+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 943162] Re: libgl1-mesa-dev links libGL.so to mesa/libGL.so which conflicts with nvidia's libGL.
Also still in 13.04 and affects the Factor programming language. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/943162 Title: libgl1-mesa-dev links libGL.so to mesa/libGL.so which conflicts with nvidia's libGL. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/943162/+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 1068404] Re: Low graphics mode in muxless hybrid ATI/Intel GPU systems after fglrx upgrade
13.11 beta did not fix the dual monitor issues. Switched back to open source radeon drivers which does work. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1068404 Title: Low graphics mode in muxless hybrid ATI/Intel GPU systems after fglrx upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1068404/+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 1102597] Re: weston-launch: could not open tty0: permission denied
** Branch linked: lp:~ubuntu-branches/debian/sid/weston/sid -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to weston in Ubuntu. https://bugs.launchpad.net/bugs/1102597 Title: weston-launch: could not open tty0: permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/weston/+bug/1102597/+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 1203017] Re: weston needs a systemgroup to launch correctly
** Branch linked: lp:~ubuntu-branches/debian/sid/weston/sid -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to weston in Ubuntu. https://bugs.launchpad.net/bugs/1203017 Title: weston needs a systemgroup to launch correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/weston/+bug/1203017/+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 1240738] [NEW] VG utility functions missing from libopenvg1-mesa
Public bug reported: System: PCDuino (armv7): Description:Linaro 12.11 Release:12.11 libopenvg1-mesa-dev: Installed: 8.0.4-0ubuntu0.6 Candidate: 8.0.4-0ubuntu0.6 Version table: *** 8.0.4-0ubuntu0.6 0 500 http://ports.ubuntu.com/ubuntu-ports/ precise-security/main armhf Packages 500 http://ports.ubuntu.com/ubuntu-ports/ precise-updates/main armhf Packages 100 /var/lib/dpkg/status 8.0.2-0ubuntu3 0 500 http://ports.ubuntu.com/ubuntu-ports/ precise/main armhf Packages When building an application that uses the VG utility functions: (vguLine, vguPolygon, vguRect, vguRoundRect, vguEllipse, vguArc,), the build fails upon linking: ./libshapes.o: In function `poly': libshapes.c:(.text+0xb78): undefined reference to `vguPolygon' ../libshapes.o: In function `Rect': libshapes.c:(.text+0xbe0): undefined reference to `vguRect' ../libshapes.o: In function `Line': libshapes.c:(.text+0xc28): undefined reference to `vguLine' ../libshapes.o: In function `Roundrect': libshapes.c:(.text+0xc80): undefined reference to `vguRoundRect' ../libshapes.o: In function `Ellipse': libshapes.c:(.text+0xcc8): undefined reference to `vguEllipse' ../libshapes.o: In function `Arc': libshapes.c:(.text+0xd2c): undefined reference to `vguArc' collect2: ld returned 1 exit status These functions are properly defined in /usr/include/VG/vgu.h, but don't appear to be accessible in the libOpenVG.so ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Tags: graphics library mesa openvg -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1240738 Title: VG utility functions missing from libopenvg1-mesa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1240738/+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 873495] Re: LightDM fails to start after nvidia-current or nvidia-current-updates are installed (upstart job issue)
@Carl: so this has probably very little to do with the nvidia driver itself if you can reproduce it with intel. I think I need more information to understand where the problem lies (lightdm could probably run some checks before starting X). Can you reproduce the problem and attach the content of the following directory, please? (you might need root privileges) /var/log/lightdm You can do something like the following: 1) reproduce the problem 2) type this from the command line: sudo cp -a /var/log/lightdm ~/ 3) tar the directory and attach the resulting file. ** No longer affects: nvidia-graphics-drivers (Ubuntu) ** No longer affects: nvidia-graphics-drivers (Ubuntu Precise) -- 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/873495 Title: LightDM fails to start after nvidia-current or nvidia-current-updates are installed (upstart job issue) To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/873495/+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 873495] Re: LightDM fails to start after nvidia-current or nvidia-current-updates are installed (upstart job issue)
** No longer affects: nvidia-drivers-ubuntu -- 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/873495 Title: LightDM fails to start after nvidia-current or nvidia-current-updates are installed (upstart job issue) To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/873495/+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 1240674] Re: high CPU load
** Attachment removed: "DpkgLog.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1240674/+attachment/3879622/+files/DpkgLog.txt -- 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/1240674 Title: high CPU load To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1240674/+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 1240674] [NEW] high CPU load
Public bug reported: I've moved my main machine from an ASUS 1001P netbook to a Lenovo Thinkpad X200 Tablet and continue to experience high CPU load from Xorg. In case of the 1001P , I had reported this as bug 1087535. I am opening a new ticket since the underlying hardware changed. When moving to the new machine I simply swapped the HD out of the old and into the new machine. I am still trying to figure out what is causing these high loads of 100% for one core. It seems to me that network activity is a contributing factor, particularly if the network is unstable. I believe many open tabs in FF lead to this situation. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xserver-xorg 1:7.6+12ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-53.81-generic-pae 3.2.50 Uname: Linux 3.2.0-53-generic-pae i686 .tmp.unity.support.test.0: ApportVersion: 2.0.1-0ubuntu17.5 Architecture: i386 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: None Date: Thu Oct 17 03:32:02 2013 DistUpgraded: 2012-11-17 18:58:48,482 DEBUG failed to SystemUnLock() (E:Not locked) DistroCodename: precise DistroVariant: ubuntu DkmsStatus: tp-smapi, 0.41, 3.2.0-53-generic-pae, i686: installed virtualbox, 4.1.12, 3.2.0-51-generic-pae, i686: installed virtualbox, 4.1.12, 3.2.0-52-generic-pae, i686: installed virtualbox, 4.1.12, 3.2.0-53-generic-pae, i686: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, even including gdb or git bisection work if needed GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:20e4] Subsystem: Lenovo Device [17aa:20e4] MachineType: LENOVO 745089G MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 LC_MESSAGES=C SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-53-generic-pae root=/dev/mapper/hostname-root ro quiet splash acpi_osi=Linux backlight=vendor i915.i915_enable_fbc=1 drm.vblankoffdelay=1 SourcePackage: xorg UpgradeStatus: Upgraded to precise on 2012-11-17 (333 days ago) dmi.bios.date: 11/29/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 7WET71WW (3.21 ) dmi.board.name: 745089G dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7WET71WW(3.21):bd11/29/2012:svnLENOVO:pn745089G:pvrThinkPadX200Tablet:rvnLENOVO:rn745089G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 745089G dmi.product.version: ThinkPad X200 Tablet dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.7.12-0ubuntu2 version.libdrm2: libdrm2 2.4.43-0ubuntu0.0.2 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.4-0ubuntu0.6 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.4-0ubuntu0.6 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.13 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1.2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4.4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 precise running-unity ubuntu -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1240674 Title: high CPU load To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1240674/+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 1232726] Re: Dash bg color doesn't match its surroundings
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mesa (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1232726 Title: Dash bg color doesn't match its surroundings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1232726/+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 1240623] [NEW] XShmGetImage returns junk/garbage in between monitors
Public bug reported: In xserver 1.14.3-3ubuntu2, we've observed that on multimonitor systems, we are passed garbage when grabbing the pixels that are not on any monitor. This does not appear to be a bug in our application - it can be easily reproduced by taking a screenshot of the whole screen using GIMP on Ubuntu 13.10 beta. The issue is not present in 1.13.3 as shipped in Ubuntu 13.04. What we are doing: get the geometry of the root window (XGetGeometry), create a pixbuf of the same size (XShmCreateImage/XShmAttach). Then we try and grab the whole thing using XShmGetImage. On multimonitor systems, the off-monitor portions are filling in the pixbuf with garbage (or garbled portions of other sections of the screen). That is, the monitors themselves are captured fine, but if the second monitor is smaller than the first, we used to get a black box in the dead space, where now we're getting garbage. I'm trying to track down the source of the regression - a random stab in the dark might be f21cc327a56e3b453cf0dba04457223d61c27ea6? Alternatively, it may not be a bug in upstream at all - I haven't yet looked into the huge patchset Ubuntu's currently maintaining. Ubuntu's "-3ubuntu2 patchset is far larger than the git diff between 1.13.3 and 1.14.3! ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New -- 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/1240623 Title: XShmGetImage returns junk/garbage in between monitors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1240623/+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 873495] Re: LightDM fails to start after nvidia-current or nvidia-current-updates are installed (upstart job issue)
Just had this happen ~4-5 times in a row on Sunday. I just kept rebooting until it finally worked. 12.04.3. -- 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/873495 Title: LightDM fails to start after nvidia-current or nvidia-current-updates are installed (upstart job issue) To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/873495/+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 1236710] Re: gnome-screensaver couldn't display unlock dialog
Marking this bug as Invalid in the OEM priority queue, as it is a bug that needs to be taken care of by enablement ** Changed in: oem-priority Status: New => Invalid ** Changed in: oem-priority/precise Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-lts-quantal in Ubuntu. https://bugs.launchpad.net/bugs/1236710 Title: gnome-screensaver couldn't display unlock dialog To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1236710/+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 873495] Re: LightDM fails to start after nvidia-current or nvidia-current-updates are installed (upstart job issue)
Yes, this bug still occurs and has expanded to include very fast Haswell hardware with Intel graphics. This seems to be race condition where X is not ready for lightDM to start. We suspect an upstart bug or lightdm.conf config file issue. This fix works consistently: - We've found that adding "sleep 2" above "exec lightdm" in /etc/init/lightdm.conf also resolves the booting issue - System76 is packing and distributing it's own LighDM with this fix so that updates don't wipe it out and then cause failed boots for our users. -- 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/873495 Title: LightDM fails to start after nvidia-current or nvidia-current-updates are installed (upstart job issue) To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/873495/+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 1237495] Re: [xmir] Xorg crashed with SIGABRT in __GI_raise()
Not enough information to diagnose the incomplete stacktrace, but the logs have plenty of issues with xmir. ** Changed in: xserver-xorg-video-intel (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1237495 Title: [xmir] Xorg crashed with SIGABRT in __GI_raise() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1237495/+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
Re: [Ubuntu-x-swat] [Bug 873495] Re: LightDM fails to start after nvidia-current or nvidia-current-updates are installed (upstart job issue)
Le 16/10/2013 13:30, Alberto Milone a écrit : > Is this still a problem? > not anymore on my side thanks for the fix -- 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/873495 Title: LightDM fails to start after nvidia-current or nvidia-current-updates are installed (upstart job issue) To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/873495/+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
Re: [Ubuntu-x-swat] [Bug 873495] Re: LightDM fails to start after nvidia-current or nvidia-current-updates are installed (upstart job issue)
Seems to be not an issue with wither 13.04 or 13.10. Thanks to those who fixed it. frank On 10/16/2013 04:30 AM, Alberto Milone wrote: > Is this still a problem? > -- 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/873495 Title: LightDM fails to start after nvidia-current or nvidia-current-updates are installed (upstart job issue) To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/873495/+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 1180881] Re: Touchscreen only works after suspend/resume on Lenovo ideapad P400 Touch
** Also affects: hwe-next Importance: Undecided Status: New ** Changed in: hwe-next Assignee: (unassigned) => AceLan Kao (acelankao) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1180881 Title: Touchscreen only works after suspend/resume on Lenovo ideapad P400 Touch To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1180881/+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 1236340] Re: new upstream release 9.1.7
nouveau: 3 tests failing. retesting them on 9.1.4 shows that they're flaky before too, so not a real regression. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1236340 Title: new upstream release 9.1.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1236340/+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 1236340] Re: new upstream release 9.1.7
radeon: works, one test that failed to link is now crashing. But it printed � before, so big chance it was just showing garbage and under the right conditions it would already crash. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1236340 Title: new upstream release 9.1.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1236340/+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 873495] Re: LightDM fails to start after nvidia-current or nvidia-current-updates are installed (upstart job issue)
Is this still a problem? -- 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/873495 Title: LightDM fails to start after nvidia-current or nvidia-current-updates are installed (upstart job issue) To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/873495/+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 1240466] [NEW] package nvidia-current 195.36.24-0ubuntu1~10.04.3 failed to install/upgrade: nvidia-current kernel module failed to build
Public bug reported: gustavod@vostro:~$ uname -a Linux vostro 2.6.32-52-generic #114-Ubuntu SMP Wed Sep 11 18:50:27 UTC 2013 x86_64 GNU/Linux gustavod@vostro:~$ lsb_release -rd Description:Ubuntu 10.04.4 LTS Release:10.04 gustavod@vostro:~$ apt-cache policy nvidia-current nvidia-current: Instalado: 195.36.24-0ubuntu1~10.04.3 Candidato: 195.36.24-0ubuntu1~10.04.3 Tabela de versão: *** 195.36.24-0ubuntu1~10.04.3 0 500 http://archive.ubuntu.com/ubuntu/ lucid-updates/restricted Packages 500 http://archive.ubuntu.com/ubuntu/ lucid-security/restricted Packages 100 /var/lib/dpkg/status 195.36.15-0ubuntu2 0 500 http://archive.ubuntu.com/ubuntu/ lucid/restricted Packages ProblemType: Package DistroRelease: Ubuntu 10.04 Package: nvidia-current 195.36.24-0ubuntu1~10.04.3 ProcVersionSignature: Ubuntu 2.6.32-52.114-generic 2.6.32.61+drm33.26 Uname: Linux 2.6.32-52-generic x86_64 Architecture: amd64 Date: Wed Oct 16 07:44:34 2013 DkmsStatus: nvidia-current, 195.36.24, 2.6.32-52-generic, x86_64: installed ErrorMessage: nvidia-current kernel module failed to build InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) MachineType: Dell Inc. Vostro 270s PackageVersion: 195.36.24-0ubuntu1~10.04.3 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-52-generic root=UUID=ba8290ab-9997-41a9-b160-145664499256 ro quiet splash SourcePackage: nvidia-graphics-drivers Title: package nvidia-current 195.36.24-0ubuntu1~10.04.3 failed to install/upgrade: nvidia-current kernel module failed to build dmi.bios.date: 11/22/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0478VN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd11/22/2012:svnDellInc.:pnVostro270s:pvr:rvnDellInc.:rn0478VN:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: Vostro 270s dmi.sys.vendor: Dell Inc. glxinfo: Error: [Errno 2] Arquivo ou diretório não encontrado system: distro: Ubuntu codename: lucid architecture: x86_64 kernel: 2.6.32-52-generic ** Affects: nvidia-graphics-drivers (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package lucid -- 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/1240466 Title: package nvidia-current 195.36.24-0ubuntu1~10.04.3 failed to install/upgrade: nvidia-current kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1240466/+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 1240450] [NEW] package nvidia-current 195.36.24-0ubuntu1~10.04.3 failed to install/upgrade: nvidia-current kernel module failed to build
Public bug reported: gustavod@xps:~$ uname -a Linux xps 3.0.0-32-generic #51~lucid1-Ubuntu SMP Fri Mar 22 17:34:23 UTC 2013 x86_64 GNU/Linux gustavod@xps:~$ lsb_release -rd Description:Ubuntu 10.04.4 LTS Release:10.04 gustavod@xps:~$ apt-cache policy nvidia-current nvidia-current: Instalado: 195.36.24-0ubuntu1~10.04.3 Candidato: 195.36.24-0ubuntu1~10.04.3 Tabela de versão: *** 195.36.24-0ubuntu1~10.04.3 0 500 http://archive.ubuntu.com/ubuntu/ lucid-updates/restricted Packages 500 http://archive.ubuntu.com/ubuntu/ lucid-security/restricted Packages 100 /var/lib/dpkg/status 195.36.15-0ubuntu2 0 500 http://archive.ubuntu.com/ubuntu/ lucid/restricted Packages ProblemType: Package DistroRelease: Ubuntu 10.04 Package: nvidia-current 195.36.24-0ubuntu1~10.04.3 ProcVersionSignature: Ubuntu 3.0.0-32.51~lucid1-generic 3.0.69 Uname: Linux 3.0.0-32-generic x86_64 Architecture: amd64 Date: Wed Oct 16 06:53:53 2013 DkmsStatus: vboxhost, 4.2.18, 2.6.32-52-generic, x86_64: installed vboxhost, 4.2.18, 3.0.0-32-generic, x86_64: installed nvidia-current, 195.36.24, 2.6.32-52-generic, x86_64: installed ErrorMessage: nvidia-current kernel module failed to build InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) MachineType: Dell Inc. XPS M1330 PackageVersion: 195.36.24-0ubuntu1~10.04.3 ProcCmdLine: BOOT_IMAGE=/vmlinuz-3.0.0-32-generic root=UUID=9402aea0-f9bc-4dc6-8825-7a297fc5adce ro quiet splash SourcePackage: nvidia-graphics-drivers Title: package nvidia-current 195.36.24-0ubuntu1~10.04.3 failed to install/upgrade: nvidia-current kernel module failed to build dmi.bios.date: 12/26/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd12/26/2008:svnDellInc.:pnXPSM1330:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: XPS M1330 dmi.sys.vendor: Dell Inc. glxinfo: Error: [Errno 2] Arquivo ou diretório não encontrado system: distro: Ubuntu codename: lucid architecture: x86_64 kernel: 3.0.0-32-generic ** Affects: nvidia-graphics-drivers (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package lucid -- 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/1240450 Title: package nvidia-current 195.36.24-0ubuntu1~10.04.3 failed to install/upgrade: nvidia-current kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1240450/+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 1240428] [NEW] Radeon drivers not loaded properly after upgrading to Saucy
Public bug reported: After upgrading to Ubuntu 13.10 (Saucy), GDM stops to work (strange colors appearing on screen), and lightdm works using llvmpipe instead of radeon drivers. Performance is really bad and dual screen no longer works. It worked perfectly before upgrading. When loging to the session a message box appears saying "System program problem detected". Unfortunately when I click to "Send report..." nothing happens. The display box disappears automatically after some time. Among other things, I tried to purge all radeon-related packages and reinstalling them again, with no success. Any idea? Thank you very much Output of glxinfo | grep Gallium: OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.3, 128 bits) Output of dmesg | egrep 'drm|radeon' [ 16.400055] [drm] Initialized drm 1.1.0 20060810 [ 17.543444] [drm] radeon kernel modesetting enabled. [ 17.543878] [drm] initializing kernel modesetting (RV610 0x1002:0x94C1 0x1028:0x0D02). [ 17.543892] [drm] register mmio base: 0xFE9F [ 17.543893] [drm] register mmio size: 65536 [ 17.543971] radeon :01:00.0: VRAM: 256M 0x - 0x0FFF (256M used) [ 17.543973] radeon :01:00.0: GTT: 512M 0x1000 - 0x2FFF [ 17.543975] [drm] Detected VRAM RAM=256M, BAR=256M [ 17.543976] [drm] RAM width 64bits DDR [ 17.544046] [drm] radeon: 256M of VRAM memory ready [ 17.544047] [drm] radeon: 512M of GTT memory ready. [ 17.544061] [drm] GART: num cpu pages 131072, num gpu pages 131072 [ 17.544453] [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0 [ 17.555887] [drm] Loading RV610 Microcode [ 17.910231] [drm] PCIE GART of 512M enabled (table at 0x0004). [ 17.910278] radeon :01:00.0: WB enabled [ 17.910281] radeon :01:00.0: fence driver on ring 0 use gpu addr 0x1c00 and cpu addr 0x880115f00c00 [ 17.910283] radeon :01:00.0: fence driver on ring 3 use gpu addr 0x1c0c and cpu addr 0x880115f00c0c [ 17.910289] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). [ 17.910290] [drm] Driver supports precise vblank timestamp query. [ 17.910308] radeon :01:00.0: irq 51 for MSI/MSI-X [ 17.910318] radeon :01:00.0: radeon: using MSI. [ 17.910339] [drm] radeon: irq initialized. [ 17.941667] [drm] ring test on 0 succeeded in 1 usecs [ 17.941724] [drm] ring test on 3 succeeded in 1 usecs [ 17.942047] [drm] ib test on ring 0 succeeded in 0 usecs [ 17.942058] [drm] ib test on ring 3 succeeded in 0 usecs [ 17.942266] [drm] Radeon Display Connectors [ 17.942268] [drm] Connector 0: [ 17.942269] [drm] DIN-1 [ 17.942270] [drm] Encoders: [ 17.942271] [drm] TV1: INTERNAL_KLDSCP_DAC2 [ 17.942272] [drm] Connector 1: [ 17.942273] [drm] DVI-I-1 [ 17.942274] [drm] HPD2 [ 17.942276] [drm] DDC: 0x7e50 0x7e50 0x7e54 0x7e54 0x7e58 0x7e58 0x7e5c 0x7e5c [ 17.942277] [drm] Encoders: [ 17.942278] [drm] CRT2: INTERNAL_KLDSCP_DAC2 [ 17.942279] [drm] DFP1: INTERNAL_KLDSCP_TMDS1 [ 17.942280] [drm] Connector 2: [ 17.942281] [drm] DVI-I-2 [ 17.942282] [drm] HPD1 [ 17.942283] [drm] DDC: 0x7e40 0x7e40 0x7e44 0x7e44 0x7e48 0x7e48 0x7e4c 0x7e4c [ 17.942284] [drm] Encoders: [ 17.942285] [drm] CRT1: INTERNAL_KLDSCP_DAC1 [ 17.942286] [drm] DFP2: INTERNAL_LVTM1 [ 17.942294] [drm] Internal thermal controller with fan control [ 17.942325] [drm] radeon: power management initialized [ 18.013016] [drm] fb mappable at 0xD0142000 [ 18.013019] [drm] vram apper at 0xD000 [ 18.013020] [drm] size 7299072 [ 18.013021] [drm] fb depth is 24 [ 18.013022] [drm]pitch is 6912 [ 18.013081] fbcon: radeondrmfb (fb0) is primary device [ 18.215983] radeon :01:00.0: fb0: radeondrmfb frame buffer device [ 18.215984] radeon :01:00.0: registered panic notifier [ 18.215989] [drm] Initialized radeon 2.34.0 20080528 for :01:00.0 on minor 0 [ 1658.773964] [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 202 [ 1658.775016] [drm:radeon_dvi_detect] *ERROR* DVI-I-2: probed a monitor but no|invalid EDID [ 1669.407596] [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 165 ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xserver-xorg-video-radeon (not installed) ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,decor,compiztoolbox,gnomecompat,mousepoll,place,grid,regex,move,wall,vpswitch,obs,commands,snap,imgpng,animation,resize,session,unitymtgrabhandles,workarounds,expo,ezoom,staticswitcher,fade,scale,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Oct 16 11:23:57 2013 DistUpgraded: 2013-10-15 14
[Ubuntu-x-swat] [Bug 1041790]
(In reply to comment #113) > On snb the blorp engine in mesa has become a bit more hang-happy, see bug > #70151 > Not all gpu hangs are created equal ;-) > Actually it was on Sandybridge. > You mean a gpu hang happens while when doing a vt switch? No I meant, if you suffer a lockup you just have to wait a few seconds and switch to another VT and back, then you can resume with your system (although sometimes fonts are broken). -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1041790 Title: [snb] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001, workaround i915.semaphores=0 To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1041790/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1041790]
(In reply to comment #112) > Just a few remarks. > I still see this bug with Kernel 3.8, Mesa 9.2.1 and DRI 2.99.904. > Moreover, with switching from Mesa 9.1.x to Mesa 9.2.x the number of lockups > highly increased (especially in games). On snb the blorp engine in mesa has become a bit more hang-happy, see bug #70151 Not all gpu hangs are created equal ;-) > Additionally with running the latest drivers complete system lockups are > gone, but it's still a lockup for multiple seconds with following VT > switching. You mean a gpu hang happens while when doing a vt switch? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1041790 Title: [snb] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001, workaround i915.semaphores=0 To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1041790/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
