[Touch-packages] [Bug 1424466] Re: Devel package not installable in 14.04.2 (mesa-lts-utopic
** Changed in: mesa (Ubuntu) Status: Confirmed = Invalid ** Changed in: mesa (Ubuntu Trusty) Assignee: (unassigned) = Maarten Lankhorst (mlankhorst) ** Changed in: mesa (Ubuntu Trusty) Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1424466 Title: Devel package not installable in 14.04.2 (mesa-lts-utopic Status in mesa package in Ubuntu: Invalid Status in mesa source package in Trusty: Fix Committed Bug description: [Impact] * Some -dev packages like ubuntu-sdk and libglew-dev cannot be installed when the lts-utopic stack is used. [Test Case] * Install the lts-utopic stack. * apt-get install ubuntu-sdk * Good: you get a whole list of packages to install. * Bad: apt-get install fails like pasted in the original bug report. * Also test the same without the lts-utopic stack, to make sure there are no regressions. [Regression Potential] * Low, this has been done for precise before, and mesa packaging has to be updated for every LTS release. Unfortunately there are no alternatives. :( [Other Info] * There's probably an apt bug in here too. Nudging the resolver by specifying libgl1-mesa-dev-lts-utopic and libgles2-mesa-dev-lts-utopic works, but I didn't find a good way to express this in the depends, and that would have to be done for every package. [Original bug report] Not the first, likely not the last devel to not be installable in 14.04.2 or any mesa-lts-utopic install Another one is libglew-dev sudo apt-get install freeglut3-dev Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libcheese-gtk23 : Depends: libclutter-gtk-1.0-0 (= 0.91.8) but it is not going to be installed Depends: libcogl15 (= 1.15.8) but it is not going to be installed libcheese7 : Depends: libclutter-gst-2.0-0 (= 0.10.0) but it is not going to be installed Depends: gstreamer1.0-clutter but it is not going to be installed libclutter-1.0-0 : Depends: libcogl-pango15 (= 1.15.8) but it is not going to be installed Depends: libcogl15 (= 1.15.8) but it is not going to be installed ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: freeglut3-dev (not installed) ProcVersionSignature: Ubuntu 3.16.0-31.41~14.04.1-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CurrentDesktop: Unity Date: Sun Feb 22 18:03:30 2015 InstallationDate: Installed on 2015-02-08 (14 days ago) InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150203.2) SourcePackage: freeglut UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1424466/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1420294] Re: Update Mesa Mir EGL platform for Mir 0.11
** Changed in: mesa (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1420294 Title: Update Mesa Mir EGL platform for Mir 0.11 Status in mesa package in Ubuntu: Fix Released Bug description: The recently released Mir 0.11 provides a different build dependency for the Mesa Mir EGL platform. The attached debdiff fixes this, along with some other issues with the Mesa Mir EGL platform: - Fix potential double free (LP: #1414999). - Fix gbm_device leak (LP: #1419704). - Fix dri_buffers[front/back] leak (LP: #1419710). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1420294/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1132736] Re: Xorg fails to start after installing the hardware enablement stack on precise due to missing symlink after purging old xserver-xorg
Solution 1: stop purging stuff.. Solution 2: Add fallback to /usr/bin/Xorg if solution 1 fails.. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1132736 Title: Xorg fails to start after installing the hardware enablement stack on precise due to missing symlink after purging old xserver-xorg Status in xorg package in Ubuntu: Triaged Status in xorg-lts-quantal package in Ubuntu: Confirmed Status in xorg-lts-raring package in Ubuntu: Confirmed Status in xorg-lts-saucy package in Ubuntu: Confirmed Status in xorg-lts-trusty package in Ubuntu: Confirmed Status in xorg-lts-utopic package in Ubuntu: Confirmed Bug description: After installing the hardware enablement stack on precise by running: sudo apt-get install linux-generic-lts-quantal xserver-xorg-lts-quantal Xorg fail to start. There is no error message or anything, just a black screen. Switching to a vt i possible and lightdm/x-0.log shows that a symlink is missing: X: cannot stat /etc/X11/X (No such file or directory), aborting. I updates two computers running precise x86_64 and both had the problem. Just recreating the symlink fixes the problem and then precise runs perfectly fine with the new stack (in fact, it's more stable so far). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1132736/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1400626] Re: Please backport xtrans, libdrm, x11proto-{fonts, core} packages for 14.04.2
Add libgl1-mesa-glx-lts-utopic:i386 to your line..
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libdrm in Ubuntu.
https://bugs.launchpad.net/bugs/1400626
Title:
Please backport xtrans, libdrm, x11proto-{fonts,core} packages for
14.04.2
Status in libdrm package in Ubuntu:
Invalid
Status in llvm-toolchain-snapshot package in Ubuntu:
Invalid
Status in x11proto-core package in Ubuntu:
Invalid
Status in x11proto-fonts package in Ubuntu:
Invalid
Status in xorg package in Ubuntu:
Invalid
Status in xtrans package in Ubuntu:
Invalid
Status in libdrm source package in Trusty:
Fix Released
Status in llvm-toolchain-snapshot source package in Trusty:
Fix Released
Status in x11proto-core source package in Trusty:
Fix Released
Status in x11proto-fonts source package in Trusty:
Fix Released
Status in xorg source package in Trusty:
Fix Committed
Status in xtrans source package in Trusty:
Fix Released
Bug description:
In order to upload the new xorg-server we need to backport the following
packages from utopic:
libdrm
x11proto-core
x11proto-fonts
xtrans
libdrm 2.4.52-1-2.4.56-1 seems to have the following changes:
- Hides private symbols from all libdrm libraries
- fixes MSAA on Hawaii (radeon).
- Adds cherryview pci-ids (intel).
- Makes libdrm-nouveau threadsafe with concurrent access to the drm fd.
- Fixes to exynos and freedreno.
- Enables building libdrm-freedreno1 and libdrm-exynos1
x11proto-core's main change appears to be changing from the 'pointer' type to
'void *':
https://launchpadlibrarian.net/173873109/x11proto-core_7.0.24-1_7.0.26-1.diff.gz
x11proto-fonts' main change is the same as x11proto-core, but the
documentation is reformatted too:
https://launchpadlibrarian.net/173873038/x11proto-fonts_2.1.2-1_2.1.3-1.diff.gz
xtrans seems to have 2 minor changes, increase default unix pipe size and add
support for systemd socket activation:
https://launchpadlibrarian.net/173873112/xtrans_1.3.2-1_1.3.4-1.diff.gz
xorg needs to be slightly updated, to allow xserver-xorg to provide
the unrenamed lts-utopic, and to allow xorg to be installed with the
renamed xorg-server.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1400626/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1400626] Re: Please backport xtrans, libdrm, x11proto-{fonts, core} packages for 14.04.2
I needed to do something like apt-get install xserver-xorg-lts-utopic
libegl1-mesa-drivers-lts-utopic libgl1-mesa-glx-lts-utopic:i386
John Gilbertson (blackcap93) wrote on 2015-01-29: #13
The new xorg/mesa packages should, but don't, have a Provides:
name-of-package-being-replaced field in the Debian control file, to avoid
breaking other installed packages which depend on the older xorg/mesa packages
by name; for example, the lib-gl1-mesa-glx-lts-utopic package's control file
should contain Provides: lib-gl1-mesa-glx
$ apt-cache show libgl1-mesa-glx-lts-utopic | grep Provides
Provides: libgl1, libgl1-mesa-glx, xorg-renamed-package,
xorg-renamed-package-lts-utopic
Although the provides: libgl1 should be enough in this case, no need for
an explicit libgl1-mesa-glx but it's there anyway. ;-)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libdrm in Ubuntu.
https://bugs.launchpad.net/bugs/1400626
Title:
Please backport xtrans, libdrm, x11proto-{fonts,core} packages for
14.04.2
Status in libdrm package in Ubuntu:
In Progress
Status in llvm-toolchain-snapshot package in Ubuntu:
Invalid
Status in x11proto-core package in Ubuntu:
New
Status in x11proto-fonts package in Ubuntu:
New
Status in xorg package in Ubuntu:
In Progress
Status in xtrans package in Ubuntu:
In Progress
Status in libdrm source package in Trusty:
Fix Released
Status in llvm-toolchain-snapshot source package in Trusty:
Fix Committed
Status in x11proto-core source package in Trusty:
Fix Released
Status in x11proto-fonts source package in Trusty:
Fix Released
Status in xorg source package in Trusty:
Fix Committed
Status in xtrans source package in Trusty:
Fix Released
Bug description:
In order to upload the new xorg-server we need to backport the following
packages from utopic:
libdrm
x11proto-core
x11proto-fonts
xtrans
libdrm 2.4.52-1-2.4.56-1 seems to have the following changes:
- Hides private symbols from all libdrm libraries
- fixes MSAA on Hawaii (radeon).
- Adds cherryview pci-ids (intel).
- Makes libdrm-nouveau threadsafe with concurrent access to the drm fd.
- Fixes to exynos and freedreno.
- Enables building libdrm-freedreno1 and libdrm-exynos1
x11proto-core's main change appears to be changing from the 'pointer' type to
'void *':
https://launchpadlibrarian.net/173873109/x11proto-core_7.0.24-1_7.0.26-1.diff.gz
x11proto-fonts' main change is the same as x11proto-core, but the
documentation is reformatted too:
https://launchpadlibrarian.net/173873038/x11proto-fonts_2.1.2-1_2.1.3-1.diff.gz
xtrans seems to have 2 minor changes, increase default unix pipe size and add
support for systemd socket activation:
https://launchpadlibrarian.net/173873112/xtrans_1.3.2-1_1.3.4-1.diff.gz
xorg needs to be slightly updated, to allow xserver-xorg to provide
the unrenamed lts-utopic, and to allow xorg to be installed with the
renamed xorg-server.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1400626/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1414999] Re: double free in mir when calling eglTerminate and gbm_device_destroy
** Attachment added: valgrind warnings of double free, without valgrind it kills Xmir immediately. https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1414999/+attachment/4306438/+files/spew ** Summary changed: - double free in mir when calling eglTerminate and gbm_device_destroy + double free in mir egl display when calling eglTerminate and gbm_device_destroy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1414999 Title: double free in mir egl display when calling eglTerminate and gbm_device_destroy Status in mesa package in Ubuntu: New Status in mir package in Ubuntu: New Bug description: In my standalone Xmir I do the following things: /* Init code */ if (xmir_screen-gbm) /* NULL on !mesa */ mir_connection_drm_set_gbm_device(xmir_screen-conn, xmir_screen-gbm); xmir_screen-egl_display = eglGetDisplay(mir_connection_get_egl_native_display(xmir_screen-conn)); /* Shutdown code */ eglTerminate(xmir_screen-egl_display); if (xmir_screen-gbm) gbm_device_destroy(xmir_screen-gbm); This works as expected when gbm is NULL, but I'm getting a double free in gbm_device_destroy with the eglTerminate. Calling eglGetDisplay(xmir_screen-gbm) instead works as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1414999/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1414999] [NEW] double free in mir egl display when calling eglTerminate and gbm_device_destroy
Public bug reported: In my standalone Xmir I do the following things: /* Init code */ if (xmir_screen-gbm) /* NULL on !mesa */ mir_connection_drm_set_gbm_device(xmir_screen-conn, xmir_screen-gbm); xmir_screen-egl_display = eglGetDisplay(mir_connection_get_egl_native_display(xmir_screen-conn)); /* Shutdown code */ eglTerminate(xmir_screen-egl_display); if (xmir_screen-gbm) gbm_device_destroy(xmir_screen-gbm); This works as expected when gbm is NULL, but I'm getting a double free in gbm_device_destroy with the eglTerminate. Calling eglGetDisplay(xmir_screen-gbm) instead works as expected. ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Affects: mir (Ubuntu) Importance: Undecided Status: New ** Also affects: mir (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1414999 Title: double free in mir egl display when calling eglTerminate and gbm_device_destroy Status in mesa package in Ubuntu: New Status in mir package in Ubuntu: New Bug description: In my standalone Xmir I do the following things: /* Init code */ if (xmir_screen-gbm) /* NULL on !mesa */ mir_connection_drm_set_gbm_device(xmir_screen-conn, xmir_screen-gbm); xmir_screen-egl_display = eglGetDisplay(mir_connection_get_egl_native_display(xmir_screen-conn)); /* Shutdown code */ eglTerminate(xmir_screen-egl_display); if (xmir_screen-gbm) gbm_device_destroy(xmir_screen-gbm); This works as expected when gbm is NULL, but I'm getting a double free in gbm_device_destroy with the eglTerminate. Calling eglGetDisplay(xmir_screen-gbm) instead works as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1414999/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1414417] Re: [xorg-edgers] [346.35] nvidia-persistenced journalctl errors
** Package changed: xorg (Ubuntu) = nvidia-graphics-drivers (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1414417 Title: [xorg-edgers] [346.35] nvidia-persistenced journalctl errors Status in nvidia-graphics-drivers package in Ubuntu: New Bug description: vivid i386 booted with systemd 218-5ubuntu2, nvidia 346.35 vivid genuine xorg/xserver 346.35 dependencies are set to conflict with nvidia-persistenced /usr/share/doc/nvidia-346/html/nvidia-persistenced.html tell how to install it, but it fails into a terminal: oem@u32:~$ % nvidia-persistenced bash: fg: %: no such job http://us.download.nvidia.com/XFree86/Linux-x86/346.35/README/nvidia-persistenced.html and journalctl log: janv. 25 08:04:31 u32 kernel: NVRM: loading NVIDIA UNIX x86 Kernel Module 346.35 Sat Jan 10 20:33:56 PST 2015 janv. 25 08:04:32 u32 nvidia-persistenced[424]: Started (424) janv. 25 08:04:32 u32 nvidia-persistenced[427]: Failed to open PID file: File exists janv. 25 08:04:32 u32 nvidia-persistenced[427]: Shutdown (427) janv. 25 08:04:32 u32 nvidia-persistenced[424]: Failed to unlink socket: No such file or directory janv. 25 08:04:32 u32 nvidia-persistenced[424]: Failed to unlink PID file: No such file or directory janv. 25 08:04:32 u32 nvidia-persistenced[424]: Shutdown (424) So some package(s) seems needing update; maybe needs to open xorg, xserver and/or systemd affected package(s) too. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.19.0-2.2-generic 3.19.0-rc4 Uname: Linux 3.19.0-2-generic i686 NonfreeKernelModules: nvidia .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86 Kernel Module 346.35 Sat Jan 10 20:33:56 PST 2015 GCC version: gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu2) ApportVersion: 2.15.1-0ubuntu2 Architecture: i386 BootDmesg: (Nothing has been logged yet.) BootLog: CurrentDesktop: GNOME Date: Sun Jan 25 11:02:14 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: nvidia-346, 346.35, 3.18.0-9-generic, i686: installed nvidia-346, 346.35, 3.19.0-2-generic, i686: installed vboxhost, 4.3.20, 3.18.0-9-generic, i686: installed vboxhost, 4.3.20, 3.19.0-2-generic, i686: installed GraphicsCard: NVIDIA Corporation GM107 [GeForce GTX 750] [10de:1381] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:362e] Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-2-generic root=UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 ro init=/lib/systemd/systemd SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5W DH Deluxe dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5W DH Deluxe dmi.product.version: System Version dmi.sys.vendor: ASUSTEK COMPUTER INC version.compiz: compiz 1:0.9.12.0+15.04.20141219-0ubuntu1 version.libdrm2: libdrm2 2.4.58-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.4.2-2ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.4.2-2ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.16.2.901-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Sun Jan 25 08:04:54 2015 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech USB RECEIVER MOUSE, id 8 inputAT Translated Set 2 keyboard KEYBOARD, id 9 xserver.errors: open /dev/fb0: No such file or
[Touch-packages] [Bug 1408593] Re: X server disables acceleartion or turns off output (makes screen black) after kernel upgrade to v3.18 (Ubuntu Vivid)
** Package changed: xorg (Ubuntu) = xserver-xorg-video-intel (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1408593 Title: X server disables acceleartion or turns off output (makes screen black) after kernel upgrade to v3.18 (Ubuntu Vivid) Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-intel package in Ubuntu: Confirmed Bug description: after reboot into kernel 3.18 (3.18.0-8.9) with Intel driver version 2:2.99.916+git20141119-1~exp1ubuntu1 it disables output / blacks the screen and puts in the log : [37.179] (II) GLX: Initialized DRI2 GL provider for screen 0 [37.215] (WW) intel(0): Failed to submit rendering commands, trying again with outputs disabled. (then refuses to switch local VTs both by [Ctrl-]Alt-Fn and by chvt in remote logins) after reverting to 2:2.99.914-1~exp1ubuntu6 it puts : [41.679] (II) GLX: Initialized DRI2 GL provider for screen 0 [41.711] (EE) intel(0): Failed to submit rendering commands, disabling acceleration. (then allows to log in bu with desktop composition effects disabled) after reboot back into kernel 3.16.0-28.38 , both *.916 and *.914 drivers work well probably this bug should also be attached to kernel package v3.18 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.18.0-8.9-generic 3.18.1 Uname: Linux 3.18.0-8-generic x86_64 ApportVersion: 2.15.1-0ubuntu1 Architecture: amd64 Date: Thu Jan 8 11:23:52 2015 InstallationDate: Installed on 2009-11-01 (1893 days ago) InstallationMedia: Kubuntu 9.10 Karmic Koala - Release amd64 (20091027) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=uk_UA.UTF-8 SHELL=/bin/bash SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.15.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mwg1214 F pulseaudio CRDA: country UA: DFS-UNSET (2400 - 2483 @ 40), (N/A, 20), (N/A), NO-OUTDOOR (5150 - 5350 @ 40), (N/A, 20), (N/A), NO-OUTDOOR (57240 - 65880 @ 2160), (N/A, 40), (N/A), NO-OUTDOOR CurrentDesktop: KDE DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=6932e499-f0ad-4456-b93c-2b7f9bf763dc InstallationDate: Installed on 2009-11-01 (1893 days ago) InstallationMedia: Kubuntu 9.10 Karmic Koala - Release amd64 (20091027) MachineType: Acer Aspire Package: xorg 1:7.7+7ubuntu2 PackageArchitecture: amd64 ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic root=UUID=9bc29087-2e9e-4bf9-bea1-2540902b5ae3 ro rootflags=commit=3600 transparent_hugepage=always init=/lib/systemd/systemd ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 RelatedPackageVersions: linux-restricted-modules-3.16.0-28-generic N/A linux-backports-modules-3.16.0-28-generic N/A linux-firmware 1.140 Tags: vivid vivid Uname: Linux 3.16.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin cdrom dialout disk kvm lpadmin netdev plugdev sambashare src _MarkForUpload: True dmi.bios.date: 05/06/2011 dmi.bios.vendor: INSYDE dmi.bios.version: V1.24 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: JV10_CS dmi.board.vendor: Intel Corp. dmi.board.version: Base Board Version dmi.chassis.type: 1 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvrV1.24:bd05/06/2011:svnAcer:pnAspire:pvrV1.24:rvnIntelCorp.:rnJV10_CS:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion: dmi.product.name: Aspire dmi.product.version: V1.24 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1408593/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1404696] Re: No vdpau for the utopic xstack in trusty
Yeah this was a bug in x-staging. Can you verify this works correctly now? ** Changed in: mesa (Ubuntu) Status: New = Incomplete ** Changed in: mesa (Ubuntu) Assignee: (unassigned) = Maarten Lankhorst (mlankhorst) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1404696 Title: No vdpau for the utopic xstack in trusty Status in mesa package in Ubuntu: Incomplete Bug description: Hello, I have tested the utopic xstack in trusty in the Canonical X Staging ppa https://launchpad.net/~canonical-x/+archive/ubuntu/x-staging?field.series_filter=trusty . It installs fine with; LC_ALL=C apt-get install -V libglapi-mesa-lts-utopic libgl1-mesa-glx- lts-utopic xserver-xorg-lts-utopic xserver-xorg-input-all-lts-utopic xserver-xorg-video-all-lts-utopic libgl1-mesa-dri-lts-utopic libglapi- mesa-lts-utopic:i386 libgl1-mesa-dri-lts-utopic:i386 libgl1-mesa-glx- lts-utopic:i386 libgles2-mesa-lts-utopic libglapi-mesa-lts-utopic mesa-vdpau-drivers-lts-utopic libegl1-mesa-drivers-lts-utopic libwayland-egl1-mesa-lts-utopic But under vdpauinfo there are no decoder capabilities for a AMD Radeon 5550 (r600); Decoder capabilities: name level macbs width height --- With stock xstack; Decoder capabilities: name level macbs width height --- MPEG1 0 9216 2048 1152 MPEG2_SIMPLE 3 9216 2048 1152 MPEG2_MAIN3 9216 2048 1152 H264_BASELINE41 9216 2048 1152 H264_MAIN41 9216 2048 1152 H264_HIGH41 9216 2048 1152 VC1_SIMPLE1 9216 2048 1152 VC1_MAIN 2 9216 2048 1152 VC1_ADVANCED 4 9216 2048 1152 The total output of vdpauinfo is attached. Best regards, Bernhard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1404696/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1400626] [NEW] Please backport xtrans, libdrm, x11proto-{fonts, core} packages for 14.04.2
Public bug reported:
In order to upload the new xorg-server we need to backport the following
packages from utopic:
libdrm
x11proto-core
x11proto-fonts
xtrans
libdrm 2.4.52-1-2.4.56-1 seems to have the following changes:
- Hides private symbols from all libdrm libraries
- fixes MSAA on Hawaii (radeon).
- Adds cherryview pci-ids (intel).
- Makes libdrm-nouveau threadsafe with concurrent access to the drm fd.
- Fixes to exynos and freedreno.
- Enables building libdrm-freedreno1 and libdrm-exynos1
x11proto-core's main change appears to be changing from the 'pointer' type to
'void *':
https://launchpadlibrarian.net/173873109/x11proto-core_7.0.24-1_7.0.26-1.diff.gz
x11proto-fonts' main change is the same as x11proto-core, but the documentation
is reformatted too:
https://launchpadlibrarian.net/173873038/x11proto-fonts_2.1.2-1_2.1.3-1.diff.gz
xtrans seems to have 2 minor changes, increase default unix pipe size and add
support for systemd socket activation:
https://launchpadlibrarian.net/173873112/xtrans_1.3.2-1_1.3.4-1.diff.gz
** Affects: libdrm (Ubuntu)
Importance: High
Assignee: Maarten Lankhorst (mlankhorst)
Status: In Progress
** Affects: x11proto-core (Ubuntu)
Importance: Undecided
Status: New
** Affects: x11proto-fonts (Ubuntu)
Importance: Undecided
Status: New
** Affects: xorg (Ubuntu)
Importance: High
Assignee: Maarten Lankhorst (mlankhorst)
Status: In Progress
** Affects: xtrans (Ubuntu)
Importance: High
Assignee: Maarten Lankhorst (mlankhorst)
Status: In Progress
** Affects: libdrm (Ubuntu Trusty)
Importance: Undecided
Status: New
** Affects: x11proto-core (Ubuntu Trusty)
Importance: Undecided
Status: New
** Affects: x11proto-fonts (Ubuntu Trusty)
Importance: Undecided
Status: New
** Affects: xorg (Ubuntu Trusty)
Importance: Undecided
Status: New
** Affects: xtrans (Ubuntu Trusty)
Importance: Undecided
Status: New
** Summary changed:
- Please backport some xorg packages for 14.04.2
+ Please backport xtrans, libdrm, x11proto-{fonts,core} packages for 14.04.2
** Also affects: libdrm (Ubuntu)
Importance: Undecided
Status: New
** Changed in: libdrm (Ubuntu)
Status: New = In Progress
** Changed in: libdrm (Ubuntu)
Assignee: (unassigned) = Maarten Lankhorst (mlankhorst)
** Changed in: libdrm (Ubuntu)
Importance: Undecided = High
** Also affects: xtrans (Ubuntu)
Importance: Undecided
Status: New
** Changed in: xtrans (Ubuntu)
Assignee: (unassigned) = Maarten Lankhorst (mlankhorst)
** Changed in: xtrans (Ubuntu)
Importance: Undecided = High
** Changed in: xtrans (Ubuntu)
Status: New = In Progress
** Also affects: x11proto-fonts (Ubuntu)
Importance: Undecided
Status: New
** Also affects: x11proto-core (Ubuntu)
Importance: Undecided
Status: New
** Also affects: xorg (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: libdrm (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: x11proto-core (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: x11proto-fonts (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: xtrans (Ubuntu Trusty)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1400626
Title:
Please backport xtrans, libdrm, x11proto-{fonts,core} packages for
14.04.2
Status in libdrm package in Ubuntu:
In Progress
Status in x11proto-core package in Ubuntu:
New
Status in x11proto-fonts package in Ubuntu:
New
Status in xorg package in Ubuntu:
In Progress
Status in xtrans package in Ubuntu:
In Progress
Status in libdrm source package in Trusty:
New
Status in x11proto-core source package in Trusty:
New
Status in x11proto-fonts source package in Trusty:
New
Status in xorg source package in Trusty:
New
Status in xtrans source package in Trusty:
New
Bug description:
In order to upload the new xorg-server we need to backport the following
packages from utopic:
libdrm
x11proto-core
x11proto-fonts
xtrans
libdrm 2.4.52-1-2.4.56-1 seems to have the following changes:
- Hides private symbols from all libdrm libraries
- fixes MSAA on Hawaii (radeon).
- Adds cherryview pci-ids (intel).
- Makes libdrm-nouveau threadsafe with concurrent access to the drm fd.
- Fixes to exynos and freedreno.
- Enables building libdrm-freedreno1 and libdrm-exynos1
x11proto-core's main change appears to be changing from the 'pointer' type to
'void *':
https://launchpadlibrarian.net/173873109/x11proto-core_7.0.24-1_7.0.26-1.diff.gz
x11proto-fonts' main change is the same as x11proto-core, but the
documentation is reformatted too:
https://launchpadlibrarian.net
[Touch-packages] [Bug 1400626] Re: Please backport xtrans, libdrm, x11proto-{fonts, core} packages for 14.04.2
** Tags added: lts-utopic trusty
** Description changed:
In order to upload the new xorg-server we need to backport the following
packages from utopic:
libdrm
- x11proto-core
+ x11proto-core
x11proto-fonts
xtrans
libdrm 2.4.52-1-2.4.56-1 seems to have the following changes:
- Hides private symbols from all libdrm libraries
- fixes MSAA on Hawaii (radeon).
- Adds cherryview pci-ids (intel).
- Makes libdrm-nouveau threadsafe with concurrent access to the drm fd.
- Fixes to exynos and freedreno.
- Enables building libdrm-freedreno1 and libdrm-exynos1
x11proto-core's main change appears to be changing from the 'pointer' type to
'void *':
https://launchpadlibrarian.net/173873109/x11proto-core_7.0.24-1_7.0.26-1.diff.gz
x11proto-fonts' main change is the same as x11proto-core, but the
documentation is reformatted too:
https://launchpadlibrarian.net/173873038/x11proto-fonts_2.1.2-1_2.1.3-1.diff.gz
xtrans seems to have 2 minor changes, increase default unix pipe size and add
support for systemd socket activation:
https://launchpadlibrarian.net/173873112/xtrans_1.3.2-1_1.3.4-1.diff.gz
+
+ xorg needs to be slightly updated, to allow xserver-xorg to provide the
+ unrenamed lts-utopic, and to allow xorg to be installed with the renamed
+ xorg-server.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libdrm in Ubuntu.
https://bugs.launchpad.net/bugs/1400626
Title:
Please backport xtrans, libdrm, x11proto-{fonts,core} packages for
14.04.2
Status in libdrm package in Ubuntu:
In Progress
Status in x11proto-core package in Ubuntu:
New
Status in x11proto-fonts package in Ubuntu:
New
Status in xorg package in Ubuntu:
In Progress
Status in xtrans package in Ubuntu:
In Progress
Status in libdrm source package in Trusty:
New
Status in x11proto-core source package in Trusty:
New
Status in x11proto-fonts source package in Trusty:
New
Status in xorg source package in Trusty:
New
Status in xtrans source package in Trusty:
New
Bug description:
In order to upload the new xorg-server we need to backport the following
packages from utopic:
libdrm
x11proto-core
x11proto-fonts
xtrans
libdrm 2.4.52-1-2.4.56-1 seems to have the following changes:
- Hides private symbols from all libdrm libraries
- fixes MSAA on Hawaii (radeon).
- Adds cherryview pci-ids (intel).
- Makes libdrm-nouveau threadsafe with concurrent access to the drm fd.
- Fixes to exynos and freedreno.
- Enables building libdrm-freedreno1 and libdrm-exynos1
x11proto-core's main change appears to be changing from the 'pointer' type to
'void *':
https://launchpadlibrarian.net/173873109/x11proto-core_7.0.24-1_7.0.26-1.diff.gz
x11proto-fonts' main change is the same as x11proto-core, but the
documentation is reformatted too:
https://launchpadlibrarian.net/173873038/x11proto-fonts_2.1.2-1_2.1.3-1.diff.gz
xtrans seems to have 2 minor changes, increase default unix pipe size and add
support for systemd socket activation:
https://launchpadlibrarian.net/173873112/xtrans_1.3.2-1_1.3.4-1.diff.gz
xorg needs to be slightly updated, to allow xserver-xorg to provide
the unrenamed lts-utopic, and to allow xorg to be installed with the
renamed xorg-server.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1400626/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1390390] Re: [xorg-edgers] No drm_driver.set_busid() implementation provided by nv_drm_driver
** Package changed: xorg (Ubuntu) = linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1390390 Title: [xorg-edgers] No drm_driver.set_busid() implementation provided by nv_drm_driver Status in “linux” package in Ubuntu: Incomplete Bug description: Using the nvidia-340.58 (from xorg-edgers ppa) with the latest 3.18 kernel, get that warning logged: kernel: [ 35.160563] No drm_driver.set_busid() implementation provided by nv_drm_driver [nvidia]. Use drm_dev_set_unique() to set the unique name explicitly. This is related to a recent patch: http://lists.freedesktop.org/archives/dri-devel/2014-May/060235.html so it seems an upgrade is needed; there is no trouble seen by the way. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.18.0-2.2-generic 3.18.0-rc3 Uname: Linux 3.18.0-2-generic i686 NonfreeKernelModules: nvidia .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86 Kernel Module 340.58 Fri Oct 31 16:44:41 PDT 2014 GCC version: gcc version 4.9.2 (Ubuntu 4.9.2-1ubuntu1) ApportVersion: 2.14.7-0ubuntu10 Architecture: i386 BootLog: initctl: Event failed * Setting up X socket directories... [80G [74G[ OK ] * Starting automatic crash report generation: apport [80G [74G[ OK ] CurrentDesktop: GNOME CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: No such file or directory Date: Fri Nov 7 10:49:32 2014 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GM107 [GeForce GTX 750] [10de:1381] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:362e] Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.18.0-2-generic root=UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 ro init=/lib/systemd/systemd SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5W DH Deluxe dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5W DH Deluxe dmi.product.version: System Version dmi.sys.vendor: ASUSTEK COMPUTER INC version.compiz: compiz 1:0.9.12.0+15.04.20141105-0ubuntu1 version.libdrm2: libdrm2 2.4.58-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.16.1.901-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Fri Nov 7 07:45:48 2014 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech USB RECEIVER MOUSE, id 8 inputAT Translated Set 2 keyboard KEYBOARD, id 9 xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.16.1.901-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1390390/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1384289] Re: mesa 10.3.1 required for mir
** Changed in: mesa (Ubuntu Utopic) Assignee: (unassigned) = Maarten Lankhorst (mlankhorst) ** Changed in: mesa (Ubuntu Utopic) Importance: Undecided = Critical ** Changed in: mesa (Ubuntu Utopic) Importance: Critical = High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1384289 Title: mesa 10.3.1 required for mir Status in “mesa” package in Ubuntu: Fix Released Status in “mesa” source package in Utopic: New Bug description: There is a bugfix in 10.3.1 that will fix dma-buf handling in i915. So we would like to see the newest minor release of mesa, which is 10.3.1 This will fix: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1275398 and basically enable i915 devices to run mir. [Impact] * The bug leads to crashes in unity8 on i915 and to crashes or 'black buffers' on mir clients. * This is not a request for back porting but a request to pick the next minor bugfix release of mesa. [Test Case] * Install mir-demos on a intel atom netbook or a pentium d system * sudo mir_demo_server_basic --vt 2 --file /tmp/mir_socket * sudo chmod 666 /tmp/mir_socket * mir_demo_client_egltriangle -m /tmp/mir_socket * then vt switch to vt 1 Expected: Animation Observed: Crashing or just showing a black buffer [Regression Potential] * Instead of immediately crashing unity8s desktop session it will make the primary client of unity8: unity8-dash fail to start due to insufficient GL support on the mesa driver - but that is a different error. * 10.3.1 introduces the bespoke i915 bug fix, and further driver local fixes to nouveau for the kepler ir, shutdown leak fixes for radeon and a division by zero fix for llvmpipe. A fix to glsl that first manifested in i965. Apart from that build system cleanups for building mesa for android and detecting LLVM. * the fix to glsl has impact on i965 * fixes for intel are local to i915 and will not cause regression * fixes to radeon should only touch shutdown code * fixes to nouveau should be local to kepler gpus [Other Info] * The switch to this mesa release will not enable mir. But it will not enable unity8 on pentium D and atom, but it will be a step towards that To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1384289/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1384289] Re: mesa 10.3.1 required for mir
** Changed in: mesa (Ubuntu) Assignee: (unassigned) = Maarten Lankhorst (mlankhorst) ** Changed in: mesa (Ubuntu) Importance: Undecided = High ** Changed in: mesa (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1384289 Title: mesa 10.3.1 required for mir Status in “mesa” package in Ubuntu: Confirmed Bug description: There is a bugfix in 10.3.1 that will fix dma-buf handling in i915. So we would like to see the newest minor release of mesa, which is 10.3.1 This will fix: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1275398 and basically enable i915 devices to run mir. [Impact] * The bug leads to crashes in unity8 on i915 and to crashes or 'black buffers' on mir clients. * This is not a request for back porting but a request to pick the next minor bugfix release of mesa. [Test Case] * Install mir-demos on a intel atom netbook or a pentium d system * sudo mir_demo_server_basic --vt 2 --file /tmp/mir_socket * sudo chmod 666 /tmp/mir_socket * mir_demo_client_eglplasma -m /tmp/mir_socket * then vt switch to vt 1 * expected yellowish plasma animation, error: eglplasma crashing or just showing a black buffer [Regression Potential] * Instead of immediately crashing unity8s desktop session it will make the primary client of unity8: unity8-dash fail to start due to insufficient GL support on the mesa driver - but that is a different error. * 10.3.1 introduces the bespoke i915 bug fix, and further driver local fixes to nouveau for the kepler ir, shutdown leak fixes for radeon and a division by zero fix for llvmpipe. A fix to glsl that first manifested in i965. Apart from that build system cleanups for building mesa for android and detecting LLVM. * the fix to glsl has impact on i965 * fixes for intel are local to i915 and will not cause regression * fixes to radeon should only touch shutdown code * fixes to nouveau should be local to kepler gpus [Other Info] * The switch to this mesa release will not enable mir. But it will not enable unity8 on pentium D and atom, but it will be a step towards that To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1384289/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1377853] Re: Nested Mir server crashes on exit (corrupted double-linked list) since Mesa 10.3
** Changed in: mesa (Ubuntu) Milestone: None = ubuntu-14.10 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1377853 Title: Nested Mir server crashes on exit (corrupted double-linked list) since Mesa 10.3 Status in Mir: In Progress Status in “mesa” package in Ubuntu: In Progress Bug description: Nested Mir server crashes on exit: 1. bin/mir_demo_server_minimal -f /tmp/outer sleep 1 ; bin/mir_demo_server_shell --host-socket /tmp/outer -f /tmp/inner 2. Ctrl+C 3. *** Error in `bin/mir_demo_server_shell': corrupted double-linked list: 0x0074e970 *** To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1377853/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1365490] Re: ubuntu 12.04.5 broken on VMware
** Changed in: mesa-lts-trusty (Ubuntu Precise) Status: Incomplete = New ** Changed in: mesa-lts-trusty (Ubuntu Precise) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1365490 Title: ubuntu 12.04.5 broken on VMware Status in “mesa” package in Ubuntu: Fix Released Status in “mesa-lts-trusty” package in Ubuntu: Invalid Status in “mesa-lts-trusty” source package in Precise: Confirmed Status in “mesa” source package in Trusty: Fix Committed Bug description: [Impact] A user might find Ubuntu 12.04.5 unusable on vmware because he would face a black screen after logging in. Although there is a workaround (disabling 3D) a user may have given up at that point. Backporting will help the user run the distro after upgrading, so I believe it's highly justified. [Test Case] On VMware Workstation 10, Install Ubuntu 12.04.5, preferrably using easy install. Boot the VM, log in. You'll see a black screen only. [Regression Potential] The bug affects a function that impots a shared buffer to the 3D driver. The function is completely broken by the bug. Even if the patch should introduce another type of breakage, the problem couldn't be much worse than it already is, and should be confined to the specific function in question. [Other info] Due to different stack ordering of automatic variables, the bug may or may not be visible depending on the C compiler and the level of optimization used. For example, if -O0 -g is used the bug is not visible on 12.04.5. I have not encountered any symptoms of the bug yet on 14.04. [ Original bug report ] Ubuntu 12.04.5 shows a black screen after login with 3D enabled on VMware. This is due to a bug in the svga gallium driver's winsys. It's recently fixed in mesa master commit 2d6206140a, winsys/svga: Fix incorrect type usage in IOCTL v2, with a request to backport to mesa stable, but I'm not sure whether anyone's still maintaining the 10.1 branch. Due to the severity of the symptoms it would be greatly appreciated if this fix could be incorporated in the libgl1-mesa-dri-lts-trusty package as soon as possible. Unfortunately it's affecting the package on the installation iso. Is there anything that can be done about that? Thanks, Thomas To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1365490/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1365490] Re: ubuntu 12.04.5 broken on VMware
Hey, The package correctly mentions utopic, see this package in -updates: https://launchpad.net/ubuntu/+source/mesa/10.1.3-0ubuntu0.1 Unfortunately I mistakenly uploaded a git snapshot at one point to ubuntu instead of a ppa, so it generates a debdiff not against 10.1.3-0ubuntu0.1, but against that git snapshot. I'll attach a debdiff against 10.1.3-0ubuntu0.1 to this bug, and re- upload it again. ~Maarten -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1365490 Title: ubuntu 12.04.5 broken on VMware Status in “mesa” package in Ubuntu: Fix Released Status in “mesa-lts-trusty” package in Ubuntu: Invalid Status in “mesa-lts-trusty” source package in Precise: Incomplete Status in “mesa” source package in Trusty: Incomplete Bug description: [Impact] A user might find Ubuntu 12.04.5 unusable on vmware because he would face a black screen after logging in. Although there is a workaround (disabling 3D) a user may have given up at that point. Backporting will help the user run the distro after upgrading, so I believe it's highly justified. [Test Case] On VMware Workstation 10, Install Ubuntu 12.04.5, preferrably using easy install. Boot the VM, log in. You'll see a black screen only. [Regression Potential] The bug affects a function that impots a shared buffer to the 3D driver. The function is completely broken by the bug. Even if the patch should introduce another type of breakage, the problem couldn't be much worse than it already is, and should be confined to the specific function in question. [Other info] Due to different stack ordering of automatic variables, the bug may or may not be visible depending on the C compiler and the level of optimization used. For example, if -O0 -g is used the bug is not visible on 12.04.5. I have not encountered any symptoms of the bug yet on 14.04. [ Original bug report ] Ubuntu 12.04.5 shows a black screen after login with 3D enabled on VMware. This is due to a bug in the svga gallium driver's winsys. It's recently fixed in mesa master commit 2d6206140a, winsys/svga: Fix incorrect type usage in IOCTL v2, with a request to backport to mesa stable, but I'm not sure whether anyone's still maintaining the 10.1 branch. Due to the severity of the symptoms it would be greatly appreciated if this fix could be incorporated in the libgl1-mesa-dri-lts-trusty package as soon as possible. Unfortunately it's affecting the package on the installation iso. Is there anything that can be done about that? Thanks, Thomas To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1365490/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1365490] Re: ubuntu 12.04.5 broken on VMware
** Patch added: debdiff mesa 10.1.3-0ubuntu1.1 - 1.2 https://bugs.launchpad.net/ubuntu/+source/mesa-lts-trusty/+bug/1365490/+attachment/4221192/+files/mesa.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1365490 Title: ubuntu 12.04.5 broken on VMware Status in “mesa” package in Ubuntu: Fix Released Status in “mesa-lts-trusty” package in Ubuntu: Invalid Status in “mesa-lts-trusty” source package in Precise: Incomplete Status in “mesa” source package in Trusty: Incomplete Bug description: [Impact] A user might find Ubuntu 12.04.5 unusable on vmware because he would face a black screen after logging in. Although there is a workaround (disabling 3D) a user may have given up at that point. Backporting will help the user run the distro after upgrading, so I believe it's highly justified. [Test Case] On VMware Workstation 10, Install Ubuntu 12.04.5, preferrably using easy install. Boot the VM, log in. You'll see a black screen only. [Regression Potential] The bug affects a function that impots a shared buffer to the 3D driver. The function is completely broken by the bug. Even if the patch should introduce another type of breakage, the problem couldn't be much worse than it already is, and should be confined to the specific function in question. [Other info] Due to different stack ordering of automatic variables, the bug may or may not be visible depending on the C compiler and the level of optimization used. For example, if -O0 -g is used the bug is not visible on 12.04.5. I have not encountered any symptoms of the bug yet on 14.04. [ Original bug report ] Ubuntu 12.04.5 shows a black screen after login with 3D enabled on VMware. This is due to a bug in the svga gallium driver's winsys. It's recently fixed in mesa master commit 2d6206140a, winsys/svga: Fix incorrect type usage in IOCTL v2, with a request to backport to mesa stable, but I'm not sure whether anyone's still maintaining the 10.1 branch. Due to the severity of the symptoms it would be greatly appreciated if this fix could be incorporated in the libgl1-mesa-dri-lts-trusty package as soon as possible. Unfortunately it's affecting the package on the installation iso. Is there anything that can be done about that? Thanks, Thomas To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1365490/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1242572] Re: xkeyboard-config, console-setup, and ubiquity should use Super+Space for switching keyboard layouts
Console-setup still needs fixing for this to work. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1242572 Title: xkeyboard-config, console-setup, and ubiquity should use Super+Space for switching keyboard layouts Status in central project for keyboard configuration: Fix Released Status in “console-setup” package in Ubuntu: Confirmed Status in “ubiquity” package in Ubuntu: Confirmed Status in “xkeyboard-config” package in Ubuntu: Fix Released Status in “console-setup” source package in Trusty: Confirmed Status in “ubiquity” source package in Trusty: Confirmed Status in “xkeyboard-config” source package in Trusty: In Progress Bug description: Super+Space is default combination for switching keyboard layouts in gnome3, unity, Mac OS X, Windows. Thus for consistently, Xorg; console-setup; and ubiquity should also use Super+Space combination for switching keyboard layouts. reading xkeyboard-config sources and documentations i don't see that xkeyboard-config can support grp:lwin_space and i guess that needs to be the first step to properly support super+space. Original bug report below: Recently I installed Ubuntu 13.10 and Ubuntu GNOME 13.10. I use two keyboard layouts - English and Russian. So I select them on the corresponding screen of ubiquity setup wizard. It quietly set the keyboard switching shortcut to Alt+Shift and wrote this setting to /etc/default/keyboard: # ... XKBMODEL=pc105 XKBLAYOUT=us,ru XKBVARIANT=, XKBOPTIONS=grp:alt_shift_toggle,grp_led:scroll # ... On first boot of installed system the small notification pop-up showed that Ibus will use Super+Space for layout switching. Please fix this configuration inconsistency. -- For other layout switching problems introduced in Ubuntu 13.10 you can see bug 1218322. -- ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic i686 ApportVersion: 2.12.5-0ubuntu2 Architecture: i386 Date: Mon Oct 21 12:16:58 2013 InstallCmdLine: file=/cdrom/preseed/ubuntu-gnome.seed boot=casper only-ubiquity initrd=/casper/initrd.lz quiet splash -- InstallationDate: Installed on 2013-10-21 (0 days ago) InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Release i386 (20131017) MarkForUpload: True SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/xkeyboard-config/+bug/1242572/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1365490] Re: ubuntu 12.04.5 broken on VMware
I attached a debdiff for lts-trusty, rest of xorg team is away this week, so I've subscribed ubuntu-sponsors :) ** Patch added: debdiff for mesa-lts-trusty https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1365490/+attachment/4221570/+files/mesa-lts-trusty.patch ** Patch removed: debdiff mesa 10.1.3-0ubuntu1.1 - 1.2 https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1365490/+attachment/4221192/+files/mesa.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1365490 Title: ubuntu 12.04.5 broken on VMware Status in “mesa” package in Ubuntu: Fix Released Status in “mesa-lts-trusty” package in Ubuntu: Invalid Status in “mesa-lts-trusty” source package in Precise: Incomplete Status in “mesa” source package in Trusty: Fix Committed Bug description: [Impact] A user might find Ubuntu 12.04.5 unusable on vmware because he would face a black screen after logging in. Although there is a workaround (disabling 3D) a user may have given up at that point. Backporting will help the user run the distro after upgrading, so I believe it's highly justified. [Test Case] On VMware Workstation 10, Install Ubuntu 12.04.5, preferrably using easy install. Boot the VM, log in. You'll see a black screen only. [Regression Potential] The bug affects a function that impots a shared buffer to the 3D driver. The function is completely broken by the bug. Even if the patch should introduce another type of breakage, the problem couldn't be much worse than it already is, and should be confined to the specific function in question. [Other info] Due to different stack ordering of automatic variables, the bug may or may not be visible depending on the C compiler and the level of optimization used. For example, if -O0 -g is used the bug is not visible on 12.04.5. I have not encountered any symptoms of the bug yet on 14.04. [ Original bug report ] Ubuntu 12.04.5 shows a black screen after login with 3D enabled on VMware. This is due to a bug in the svga gallium driver's winsys. It's recently fixed in mesa master commit 2d6206140a, winsys/svga: Fix incorrect type usage in IOCTL v2, with a request to backport to mesa stable, but I'm not sure whether anyone's still maintaining the 10.1 branch. Due to the severity of the symptoms it would be greatly appreciated if this fix could be incorporated in the libgl1-mesa-dri-lts-trusty package as soon as possible. Unfortunately it's affecting the package on the installation iso. Is there anything that can be done about that? Thanks, Thomas To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1365490/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1365490] Re: ubuntu 12.04.5 broken on VMware
This has been fixed in utopic by moving to mesa 10.3. mesa-lts-trusty and mesa in trusty are still affected, I'll prepare a fix for them. I don't think the images can be redone. The trusty 14.04.2 dvd will have the utopic stack which will be fixed, but precise will no longer have new iso's. Could you update the bug description with the template linked below? https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template ** Changed in: mesa (Ubuntu) Assignee: (unassigned) = Maarten Lankhorst (mlankhorst) ** Changed in: mesa-lts-trusty (Ubuntu) Assignee: (unassigned) = Maarten Lankhorst (mlankhorst) ** Also affects: mesa (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: mesa-lts-trusty (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: mesa (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: mesa-lts-trusty (Ubuntu Trusty) Importance: Undecided Status: New ** No longer affects: mesa (Ubuntu Precise) ** No longer affects: mesa-lts-trusty (Ubuntu Trusty) ** Changed in: mesa-lts-trusty (Ubuntu) Status: New = Invalid ** Changed in: mesa-lts-trusty (Ubuntu Precise) Assignee: (unassigned) = Maarten Lankhorst (mlankhorst) ** Changed in: mesa (Ubuntu Trusty) Assignee: (unassigned) = Maarten Lankhorst (mlankhorst) ** Changed in: mesa (Ubuntu Trusty) Importance: Undecided = High ** Changed in: mesa-lts-trusty (Ubuntu Precise) Importance: Undecided = High ** Changed in: mesa (Ubuntu) Importance: Undecided = High ** Changed in: mesa (Ubuntu) Status: New = Fix Released ** Changed in: mesa (Ubuntu Trusty) Status: New = Incomplete ** Changed in: mesa-lts-trusty (Ubuntu Precise) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1365490 Title: ubuntu 12.04.5 broken on VMware Status in “mesa” package in Ubuntu: Fix Released Status in “mesa-lts-trusty” package in Ubuntu: Invalid Status in “mesa-lts-trusty” source package in Precise: Incomplete Status in “mesa” source package in Trusty: Incomplete Bug description: Ubuntu 12.04.5 shows a black screen after login with 3D enabled on VMware. This is due to a bug in the svga gallium driver's winsys. It's recently fixed in mesa master commit 2d6206140a, winsys/svga: Fix incorrect type usage in IOCTL v2, with a request to backport to mesa stable, but I'm not sure whether anyone's still maintaining the 10.1 branch. Due to the severity of the symptoms it would be greatly appreciated if this fix could be incorporated in the libgl1-mesa-dri-lts-trusty package as soon as possible. Unfortunately it's affecting the package on the installation iso. Is there anything that can be done about that? Thanks, Thomas To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1365490/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1365490] Re: ubuntu 12.04.5 broken on VMware
** Description changed: + [Impact] + + A user might find Ubuntu 12.04.5 unusable on vmware because he would + face a black screen after logging in. Although there is a workaround + (disabling 3D) a user may have given up at that point. + + Backporting will help the user run the distro after upgrading, so I + believe it's highly justified. + + [Test Case] + + On VMware Workstation 10, Install Ubuntu 12.04.5, preferrably using easy install. + Boot the VM, log in. You'll see a black screen only. + + [Regression Potential] + + The bug affects a function that impots a shared buffer to the 3D driver. + The function is completely broken by the bug. Even if the patch should + introduce another type of breakage, the problem couldn't be much worse + than it already is, and should be confined to the specific function in + question. + + [Other info] + + Due to different stack ordering of automatic variables, the bug may or + may not be visible depending on the C compiler and the level of + optimization used. For example, if -O0 -g is used the bug is not visible + on 12.04.5. I have not encountered any symptoms of the bug yet on 14.04. + + [ Original bug report ] Ubuntu 12.04.5 shows a black screen after login with 3D enabled on VMware. This is due to a bug in the svga gallium driver's winsys. It's recently fixed in mesa master commit 2d6206140a, winsys/svga: Fix incorrect type usage in IOCTL v2, with a request to backport to mesa stable, but I'm not sure whether anyone's still maintaining the 10.1 branch. Due to the severity of the symptoms it would be greatly appreciated if this fix could be incorporated in the libgl1-mesa-dri-lts-trusty package as soon as possible. Unfortunately it's affecting the package on the installation iso. Is there anything that can be done about that? Thanks, Thomas -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1365490 Title: ubuntu 12.04.5 broken on VMware Status in “mesa” package in Ubuntu: Fix Released Status in “mesa-lts-trusty” package in Ubuntu: Invalid Status in “mesa-lts-trusty” source package in Precise: Incomplete Status in “mesa” source package in Trusty: Incomplete Bug description: [Impact] A user might find Ubuntu 12.04.5 unusable on vmware because he would face a black screen after logging in. Although there is a workaround (disabling 3D) a user may have given up at that point. Backporting will help the user run the distro after upgrading, so I believe it's highly justified. [Test Case] On VMware Workstation 10, Install Ubuntu 12.04.5, preferrably using easy install. Boot the VM, log in. You'll see a black screen only. [Regression Potential] The bug affects a function that impots a shared buffer to the 3D driver. The function is completely broken by the bug. Even if the patch should introduce another type of breakage, the problem couldn't be much worse than it already is, and should be confined to the specific function in question. [Other info] Due to different stack ordering of automatic variables, the bug may or may not be visible depending on the C compiler and the level of optimization used. For example, if -O0 -g is used the bug is not visible on 12.04.5. I have not encountered any symptoms of the bug yet on 14.04. [ Original bug report ] Ubuntu 12.04.5 shows a black screen after login with 3D enabled on VMware. This is due to a bug in the svga gallium driver's winsys. It's recently fixed in mesa master commit 2d6206140a, winsys/svga: Fix incorrect type usage in IOCTL v2, with a request to backport to mesa stable, but I'm not sure whether anyone's still maintaining the 10.1 branch. Due to the severity of the symptoms it would be greatly appreciated if this fix could be incorporated in the libgl1-mesa-dri-lts-trusty package as soon as possible. Unfortunately it's affecting the package on the installation iso. Is there anything that can be done about that? Thanks, Thomas To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1365490/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1374131] Re: qtcreator-plugin autopkgtest fails on AMD64 mesa mesa_10.3.0
I've managed to reproduce this. This seems to be caused because swrast is now linked into the gallium megablob as well. Before llvmpipe was statically linked into libGL.so Adding a depends on libgl1-mesa-dri to libegl1-mesa and libgl1-mesa-glx should fix things. I'm verifying this in a ppa. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1374131 Title: qtcreator-plugin autopkgtest fails on AMD64 mesa mesa_10.3.0 Status in “mesa” package in Ubuntu: Confirmed Bug description: So, in the course of a unity8 package migration it got halted due to qtcreator-plugin autopkg test failing see here http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html which lead me to look at the jenkins run, note its only failling on amd64 arch and...you can see from here https://jenkins.qa.ubuntu.com/job/utopic-adt-qtcreator-plugin-ubuntu/ARCH=amd64,label=adt/ it started failing about 24 hrs ago with can't init gxl...almost certainly meaning it's unhappy with mesa. low and behold the difference between the pasing jenkins and failing is passing - https://jenkins.qa.ubuntu.com/job/utopic-adt-qtcreator-plugin-ubuntu/ARCH=amd64,label=adt/266/console which uses mesa 10.2.6-1ubuntu3 failing - https://jenkins.qa.ubuntu.com/job/utopic-adt-qtcreator-plugin-ubuntu/ARCH=amd64,label=adt/267/console which uses mesa 10.3.0-0ubuntu1 So can we do a couple of things? - revert mesa and see if that fixes the autopkgtest to confirm - if so, please leave reverted until we find out why so we can actually continue landing our unity8/uitk/webbrowser stuff - lastly, might be good to add qtcreator-plugin as an autopkgtest dependency to land a new mesa sorry for marking critical, but we're sunk until we get this sorted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1374131/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1374131] Re: qtcreator-plugin autopkgtest fails on AMD64 mesa mesa_10.3.0
Ok, it also seems that libgbm1 was pulling in libgl1-mesa-dri directly in 10.2.6, this is why libgl1-mesa-dri was installed in the first place. /usr/lib/$ARCH/gbm/gbm_gallium_drm.so was linking to the shared libgallium.so . This no longer happens with 10.3.0 because we drop the patches that build gallium shared, because upstream handles it better. I would say this proves that the tests are all broken and need to add an explicit depend on libgl1-mesa-dri somewhere. But since this has been going on for so long I think the easiest thing to do is fixing up the mesa packaging for backwards compatability. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1374131 Title: qtcreator-plugin autopkgtest fails on AMD64 mesa mesa_10.3.0 Status in “mesa” package in Ubuntu: Confirmed Bug description: So, in the course of a unity8 package migration it got halted due to qtcreator-plugin autopkg test failing see here http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html which lead me to look at the jenkins run, note its only failling on amd64 arch and...you can see from here https://jenkins.qa.ubuntu.com/job/utopic-adt-qtcreator-plugin-ubuntu/ARCH=amd64,label=adt/ it started failing about 24 hrs ago with can't init gxl...almost certainly meaning it's unhappy with mesa. low and behold the difference between the pasing jenkins and failing is passing - https://jenkins.qa.ubuntu.com/job/utopic-adt-qtcreator-plugin-ubuntu/ARCH=amd64,label=adt/266/console which uses mesa 10.2.6-1ubuntu3 failing - https://jenkins.qa.ubuntu.com/job/utopic-adt-qtcreator-plugin-ubuntu/ARCH=amd64,label=adt/267/console which uses mesa 10.3.0-0ubuntu1 So can we do a couple of things? - revert mesa and see if that fixes the autopkgtest to confirm - if so, please leave reverted until we find out why so we can actually continue landing our unity8/uitk/webbrowser stuff - lastly, might be good to add qtcreator-plugin as an autopkgtest dependency to land a new mesa sorry for marking critical, but we're sunk until we get this sorted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1374131/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1374131] Re: qtcreator-plugin autopkgtest fails on AMD64 mesa mesa_10.3.0
** Tags removed: block-proposed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1374131 Title: qtcreator-plugin autopkgtest fails on AMD64 mesa mesa_10.3.0 Status in “mesa” package in Ubuntu: Confirmed Bug description: So, in the course of a unity8 package migration it got halted due to qtcreator-plugin autopkg test failing see here http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html which lead me to look at the jenkins run, note its only failling on amd64 arch and...you can see from here https://jenkins.qa.ubuntu.com/job/utopic-adt-qtcreator-plugin-ubuntu/ARCH=amd64,label=adt/ it started failing about 24 hrs ago with can't init gxl...almost certainly meaning it's unhappy with mesa. low and behold the difference between the pasing jenkins and failing is passing - https://jenkins.qa.ubuntu.com/job/utopic-adt-qtcreator-plugin-ubuntu/ARCH=amd64,label=adt/266/console which uses mesa 10.2.6-1ubuntu3 failing - https://jenkins.qa.ubuntu.com/job/utopic-adt-qtcreator-plugin-ubuntu/ARCH=amd64,label=adt/267/console which uses mesa 10.3.0-0ubuntu1 So can we do a couple of things? - revert mesa and see if that fixes the autopkgtest to confirm - if so, please leave reverted until we find out why so we can actually continue landing our unity8/uitk/webbrowser stuff - lastly, might be good to add qtcreator-plugin as an autopkgtest dependency to land a new mesa sorry for marking critical, but we're sunk until we get this sorted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1374131/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1364003] Re: [FFE] mesa 10.3
Hey, It is my opinion the autopkgtests themselves were broken, but I've added explicit depends in mesa to always force libgl1-mesa-dri to be installed when libgl1-mesa-dri, libegl1-mesa or libgbm1 are installed. This allows the tests to run correctly again, and presumably fixes the armhf tests too. ~Maarten -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1364003 Title: [FFE] mesa 10.3 Status in “mesa” package in Ubuntu: Fix Committed Bug description: Impact to ubuntu: Proper support for llvm 3.5 without crashing llvmpipe when running tests on i386. kms swrast was requested, will be available in 10.3. Build fixes to support a gallium megablob, reducing size even further. New features GL_ARB_ES3_compatibility on nv50, nvc0, r600, radeonsi, softpipe, llvmpipe GL_ARB_clear_texture on i965 GL_ARB_compressed_texture_pixel_storage on all drivers GL_ARB_conditional_render_inverted on i965, nvc0, softpipe, llvmpipe GL_ARB_derivative_control on i965, nv50, nvc0, r600 GL_ARB_draw_indirect on nvc0, radeonsi GL_ARB_explicit_uniform_location (all drivers that support GLSL) GL_ARB_fragment_layer_viewport on nv50, nvc0, llvmpipe, r600 GL_ARB_gpu_shader5 on i965/gen7, nvc0 GL_ARB_multi_draw_indirect on nvc0, radeonsi GL_ARB_sample_shading on radeonsi GL_ARB_seamless_cubemap_per_texture on i965, llvmpipe, nvc0, r600, radeonsi, softpipe GL_ARB_stencil_texturing on nv50, nvc0, r600, and radeonsi GL_ARB_texture_barrier on nv50, nvc0, r300, r600, radeonsi GL_ARB_texture_compression_bptc on i965/gen7+, nvc0, r600/evergreen+, radeonsi GL_ARB_texture_cube_map_array on radeonsi GL_ARB_texture_gather on r600, radeonsi GL_ARB_texture_query_levels on nv50, nvc0, llvmpipe, r600, radeonsi, softpipe GL_ARB_texture_query_lod on r600, radeonsi GL_ARB_viewport_array on nvc0 GL_AMD_vertex_shader_viewport_index on i965/gen7+, r600 GL_OES_compressed_ETC1_RGB8_texture on nv30, nv50, nvc0, r300, r600, radeonsi, softpipe, llvmpipe GLX_MESA_query_renderer on nv30, nv50, nvc0, r300, r600, radeonsi, softpipe, llvmpipe A new software rasterizer driver (kms_swrast_dri.so) that works with DRM drivers that don't have a full-fledged GEM (such as qxl or simpledrm) Distribute the Khronos GL/glcorearb.h header file. Changes Removed support for the GL_ATI_envmap_bumpmap extension The hacky --enable-32/64-bit is no longer available in configure. To build 32/64 bit mesa refer to the default method recommended by your distribution To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1364003/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1359262] Re: Chrome + Radeon + hardware acceleration: black Google maps tab
ScottK, the upload was acked by infinity: http://irclogs.ubuntu.com/2014/09/24/%23ubuntu-release.html -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1359262 Title: Chrome + Radeon + hardware acceleration: black Google maps tab Status in “mesa” package in Ubuntu: Confirmed Bug description: When opening Google Maps, i got a completely black tab instead - see the attached image. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libgl1-mesa-dri 10.1.3-0ubuntu0.1 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 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: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Aug 20 17:29:32 2014 DistUpgraded: 2014-04-04 15:34:47,605 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Park [Mobility Radeon HD 5430] [1002:68e1] (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Caicos [Radeon HD 5450] [174b:3000] InstallationDate: Installed on 2012-11-15 (643 days ago) InstallationMedia: Ubuntu-Server 12.10 Quantal Quetzal - Release amd64 (20121017.2) MachineType: Intel Corporation Shark Bay Client platform ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-34-generic root=UUID=5f908618-7000-4276-855c-8ec7a19ce316 ro crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M SourcePackage: mesa UpgradeStatus: Upgraded to trusty on 2014-04-04 (138 days ago) dmi.bios.date: 01/28/2013 dmi.bios.vendor: Intel Corporation dmi.bios.version: HSWLPTU1.86C.0109.R03.1301282055 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Flathead Creek Crb dmi.board.vendor: Intel Corp. dmi.board.version: 2 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnIntelCorporation:bvrHSWLPTU1.86C.0109.R03.1301282055:bd01/28/2013:svnIntelCorporation:pnSharkBayClientplatform:pvr0.1:rvnIntelCorp.:rnFlatheadCreekCrb:rvr2:cvnIntelCorporation:ct3:cvr0.1: dmi.product.name: Shark Bay Client platform dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Wed Aug 20 11:04:41 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu2 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1359262/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1364003] Re: [FFE] mesa 10.3
ScottK: http://irclogs.ubuntu.com/2014/09/24/%23ubuntu-release.html -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1364003 Title: [FFE] mesa 10.3 Status in “mesa” package in Ubuntu: Fix Committed Bug description: Impact to ubuntu: Proper support for llvm 3.5 without crashing llvmpipe when running tests on i386. kms swrast was requested, will be available in 10.3. Build fixes to support a gallium megablob, reducing size even further. New features GL_ARB_ES3_compatibility on nv50, nvc0, r600, radeonsi, softpipe, llvmpipe GL_ARB_clear_texture on i965 GL_ARB_compressed_texture_pixel_storage on all drivers GL_ARB_conditional_render_inverted on i965, nvc0, softpipe, llvmpipe GL_ARB_derivative_control on i965, nv50, nvc0, r600 GL_ARB_draw_indirect on nvc0, radeonsi GL_ARB_explicit_uniform_location (all drivers that support GLSL) GL_ARB_fragment_layer_viewport on nv50, nvc0, llvmpipe, r600 GL_ARB_gpu_shader5 on i965/gen7, nvc0 GL_ARB_multi_draw_indirect on nvc0, radeonsi GL_ARB_sample_shading on radeonsi GL_ARB_seamless_cubemap_per_texture on i965, llvmpipe, nvc0, r600, radeonsi, softpipe GL_ARB_stencil_texturing on nv50, nvc0, r600, and radeonsi GL_ARB_texture_barrier on nv50, nvc0, r300, r600, radeonsi GL_ARB_texture_compression_bptc on i965/gen7+, nvc0, r600/evergreen+, radeonsi GL_ARB_texture_cube_map_array on radeonsi GL_ARB_texture_gather on r600, radeonsi GL_ARB_texture_query_levels on nv50, nvc0, llvmpipe, r600, radeonsi, softpipe GL_ARB_texture_query_lod on r600, radeonsi GL_ARB_viewport_array on nvc0 GL_AMD_vertex_shader_viewport_index on i965/gen7+, r600 GL_OES_compressed_ETC1_RGB8_texture on nv30, nv50, nvc0, r300, r600, radeonsi, softpipe, llvmpipe GLX_MESA_query_renderer on nv30, nv50, nvc0, r300, r600, radeonsi, softpipe, llvmpipe A new software rasterizer driver (kms_swrast_dri.so) that works with DRM drivers that don't have a full-fledged GEM (such as qxl or simpledrm) Distribute the Khronos GL/glcorearb.h header file. Changes Removed support for the GL_ATI_envmap_bumpmap extension The hacky --enable-32/64-bit is no longer available in configure. To build 32/64 bit mesa refer to the default method recommended by your distribution To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1364003/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1364003] Re: [FFE] mesa 10.3
Depending on the problems I might be able to fix them myself. I would also like to note that at least with nouveau I haven't encountered any yet. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1364003 Title: [FFE] mesa 10.3 Status in “mesa” package in Ubuntu: New Bug description: Impact to ubuntu: Proper support for llvm 3.5 without crashing llvmpipe when running tests on i386. kms swrast was requested, will be available in 10.3. Build fixes to support a gallium megablob, reducing size even further. New features GL_ARB_ES3_compatibility on nv50, nvc0, r600, radeonsi, softpipe, llvmpipe GL_ARB_clear_texture on i965 GL_ARB_compressed_texture_pixel_storage on all drivers GL_ARB_conditional_render_inverted on i965, nvc0, softpipe, llvmpipe GL_ARB_derivative_control on i965, nv50, nvc0, r600 GL_ARB_draw_indirect on nvc0, radeonsi GL_ARB_explicit_uniform_location (all drivers that support GLSL) GL_ARB_fragment_layer_viewport on nv50, nvc0, llvmpipe, r600 GL_ARB_gpu_shader5 on i965/gen7, nvc0 GL_ARB_multi_draw_indirect on nvc0, radeonsi GL_ARB_sample_shading on radeonsi GL_ARB_seamless_cubemap_per_texture on i965, llvmpipe, nvc0, r600, radeonsi, softpipe GL_ARB_stencil_texturing on nv50, nvc0, r600, and radeonsi GL_ARB_texture_barrier on nv50, nvc0, r300, r600, radeonsi GL_ARB_texture_compression_bptc on i965/gen7+, nvc0, r600/evergreen+, radeonsi GL_ARB_texture_cube_map_array on radeonsi GL_ARB_texture_gather on r600, radeonsi GL_ARB_texture_query_levels on nv50, nvc0, llvmpipe, r600, radeonsi, softpipe GL_ARB_texture_query_lod on r600, radeonsi GL_ARB_viewport_array on nvc0 GL_AMD_vertex_shader_viewport_index on i965/gen7+, r600 GL_OES_compressed_ETC1_RGB8_texture on nv30, nv50, nvc0, r300, r600, radeonsi, softpipe, llvmpipe GLX_MESA_query_renderer on nv30, nv50, nvc0, r300, r600, radeonsi, softpipe, llvmpipe A new software rasterizer driver (kms_swrast_dri.so) that works with DRM drivers that don't have a full-fledged GEM (such as qxl or simpledrm) Distribute the Khronos GL/glcorearb.h header file. Changes Removed support for the GL_ATI_envmap_bumpmap extension The hacky --enable-32/64-bit is no longer available in configure. To build 32/64 bit mesa refer to the default method recommended by your distribution To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1364003/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1354046] Re: no 3d acceleration with error [drm:intel_dp_start_link_train] *ERROR* too many full retries, give up
** Package changed: xorg (Ubuntu) = xserver-xorg-video-intel (Ubuntu) ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1354046 Title: no 3d acceleration with error [drm:intel_dp_start_link_train] *ERROR* too many full retries, give up Status in “linux” package in Ubuntu: Confirmed Status in “xserver-xorg-video-intel” package in Ubuntu: Confirmed Bug description: Description: 3D games, video (especially flash) makes computer unresponsive. The problem has been present since upgrade to Utopic, but have recently become worse, maybe because of error message [drm:intel_dp_start_link_train] *ERROR* too many full retries, give up which appears in all terminals. How to reproduce: Start a 1080p video. e.g. Note that the video is not run from an encrypted folder. Or watch a video on youtube. Reproducable for new users as well, so not related to /home/$USER What happens: Usage on all four CPUs on my DELL XPS 13 DEVELOPER EDITION will be between 30% and 100%. What I expected: Expected same 3D performance as on Thrusty. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.5-0ubuntu3 Architecture: amd64 BootLog: Scanning for Btrfs filesystems * Setting up X socket directories... [240G [234G[ OK ] 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: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Aug 7 17:03:51 2014 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20120703-2 DistroCodename: utopic DistroVariant: ubuntu DkmsStatus: vboxhost, 4.3.12, 3.13.0-24-generic, x86_64: installed vboxhost, 4.3.12, 3.13.0-27-generic, x86_64: installed vboxhost, 4.3.12, 3.13.0-29-generic, x86_64: installed vboxhost, 4.3.12, 3.16.0-5-generic, x86_64: installed vboxhost, 4.3.12, 3.16.0-6-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:058b] InstallationDate: Installed on 2013-08-27 (345 days ago) InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20120703-15:08 MachineType: Dell Inc. Dell System XPS L322X ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-6-generic root=UUID=221de9c1-f10a-4be4-9273-5c12864c8680 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display SystemImageInfo: Error: [Errno 2] No such file or directory: 'system-image-cli' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/15/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0PJHXN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA09:bd05/15/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L322X dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11+14.10.20140707-0ubuntu1b1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.54-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.3-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental 10.0.0-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.3-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Thu Aug 7 16:54:59 2014 xserver.configfile: default xserver.errors: intel: Failed to load module dri3 (module does not exist, 0) intel: Failed to load module present (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4933 vendor CMN xserver.version: 2:1.15.1-0ubuntu9 To manage
[Touch-packages] [Bug 1196522] Re: [nouveau] Nux/Unity 7 panels appear as brightly coloured gradients under XMir with nouveau
can't remember when, but I've hit this bug before, probably a shader issue and it has been fixed in nouveau for a while now. ** Changed in: unity (Ubuntu) Status: Confirmed = Invalid ** Changed in: xserver-xorg-video-nouveau (Ubuntu) Status: Confirmed = Fix Released ** Changed in: nux (Ubuntu) Status: Confirmed = Invalid ** Changed in: unity Status: Confirmed = Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1196522 Title: [nouveau] Nux/Unity 7 panels appear as brightly coloured gradients under XMir with nouveau Status in Mir: Invalid Status in Unity: Invalid Status in “mir” package in Ubuntu: Invalid Status in “nux” package in Ubuntu: Invalid Status in “unity” package in Ubuntu: Invalid Status in “xserver-xorg-video-nouveau” package in Ubuntu: Fix Released Bug description: Glitches are visible in this video: http://www.youtube.com/watch?v=twrWVEBih_Efeature=share Configuration: Pentium IV 1.5 GB RAM Nvidia 6200 Graphic Card To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1196522/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1242572] Re: xkeyboard-config, console-setup, and ubiquity should use Super+Space for switching keyboard layouts
** Changed in: xkeyboard-config (Ubuntu Trusty) Assignee: Maarten Kumpen (maarten) = Maarten Lankhorst (mlankhorst) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1242572 Title: xkeyboard-config, console-setup, and ubiquity should use Super+Space for switching keyboard layouts Status in central project for keyboard configuration: Fix Released Status in “console-setup” package in Ubuntu: Confirmed Status in “ubiquity” package in Ubuntu: Confirmed Status in “xkeyboard-config” package in Ubuntu: Fix Released Status in “console-setup” source package in Trusty: Confirmed Status in “ubiquity” source package in Trusty: Confirmed Status in “xkeyboard-config” source package in Trusty: Confirmed Bug description: Super+Space is default combination for switching keyboard layouts in gnome3, unity, Mac OS X, Windows. Thus for consistently, Xorg; console-setup; and ubiquity should also use Super+Space combination for switching keyboard layouts. reading xkeyboard-config sources and documentations i don't see that xkeyboard-config can support grp:lwin_space and i guess that needs to be the first step to properly support super+space. Original bug report below: Recently I installed Ubuntu 13.10 and Ubuntu GNOME 13.10. I use two keyboard layouts - English and Russian. So I select them on the corresponding screen of ubiquity setup wizard. It quietly set the keyboard switching shortcut to Alt+Shift and wrote this setting to /etc/default/keyboard: # ... XKBMODEL=pc105 XKBLAYOUT=us,ru XKBVARIANT=, XKBOPTIONS=grp:alt_shift_toggle,grp_led:scroll # ... On first boot of installed system the small notification pop-up showed that Ibus will use Super+Space for layout switching. Please fix this configuration inconsistency. -- For other layout switching problems introduced in Ubuntu 13.10 you can see bug 1218322. -- ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic i686 ApportVersion: 2.12.5-0ubuntu2 Architecture: i386 Date: Mon Oct 21 12:16:58 2013 InstallCmdLine: file=/cdrom/preseed/ubuntu-gnome.seed boot=casper only-ubiquity initrd=/casper/initrd.lz quiet splash -- InstallationDate: Installed on 2013-10-21 (0 days ago) InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Release i386 (20131017) MarkForUpload: True SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/xkeyboard-config/+bug/1242572/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1242572] Re: xkeyboard-config, console-setup, and ubiquity should use Super+Space for switching keyboard layouts
xkb-data 2.12 is in utopic, so marking it as fix released ** Changed in: xkeyboard-config (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1242572 Title: xkeyboard-config, console-setup, and ubiquity should use Super+Space for switching keyboard layouts Status in central project for keyboard configuration: Fix Released Status in “console-setup” package in Ubuntu: Confirmed Status in “ubiquity” package in Ubuntu: Confirmed Status in “xkeyboard-config” package in Ubuntu: Fix Released Status in “console-setup” source package in Trusty: Confirmed Status in “ubiquity” source package in Trusty: Confirmed Status in “xkeyboard-config” source package in Trusty: Confirmed Bug description: Super+Space is default combination for switching keyboard layouts in gnome3, unity, Mac OS X, Windows. Thus for consistently, Xorg; console-setup; and ubiquity should also use Super+Space combination for switching keyboard layouts. reading xkeyboard-config sources and documentations i don't see that xkeyboard-config can support grp:lwin_space and i guess that needs to be the first step to properly support super+space. Original bug report below: Recently I installed Ubuntu 13.10 and Ubuntu GNOME 13.10. I use two keyboard layouts - English and Russian. So I select them on the corresponding screen of ubiquity setup wizard. It quietly set the keyboard switching shortcut to Alt+Shift and wrote this setting to /etc/default/keyboard: # ... XKBMODEL=pc105 XKBLAYOUT=us,ru XKBVARIANT=, XKBOPTIONS=grp:alt_shift_toggle,grp_led:scroll # ... On first boot of installed system the small notification pop-up showed that Ibus will use Super+Space for layout switching. Please fix this configuration inconsistency. -- For other layout switching problems introduced in Ubuntu 13.10 you can see bug 1218322. -- ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic i686 ApportVersion: 2.12.5-0ubuntu2 Architecture: i386 Date: Mon Oct 21 12:16:58 2013 InstallCmdLine: file=/cdrom/preseed/ubuntu-gnome.seed boot=casper only-ubiquity initrd=/casper/initrd.lz quiet splash -- InstallationDate: Installed on 2013-10-21 (0 days ago) InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Release i386 (20131017) MarkForUpload: True SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/xkeyboard-config/+bug/1242572/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1242572] Re: xkeyboard-config, console-setup, and ubiquity should use Super+Space for switching keyboard layouts
xkeyboard-config patch for trusty Without the console-setup changes I cannot verify this works correctly, which is why I haven't uploaded it yet.. ** Patch added: xkb-config-trusty.patch https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1242572/+attachment/4213592/+files/xkb-config-trusty.patch ** Changed in: xkeyboard-config (Ubuntu Trusty) Status: Confirmed = In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1242572 Title: xkeyboard-config, console-setup, and ubiquity should use Super+Space for switching keyboard layouts Status in central project for keyboard configuration: Fix Released Status in “console-setup” package in Ubuntu: Confirmed Status in “ubiquity” package in Ubuntu: Confirmed Status in “xkeyboard-config” package in Ubuntu: Fix Released Status in “console-setup” source package in Trusty: Confirmed Status in “ubiquity” source package in Trusty: Confirmed Status in “xkeyboard-config” source package in Trusty: In Progress Bug description: Super+Space is default combination for switching keyboard layouts in gnome3, unity, Mac OS X, Windows. Thus for consistently, Xorg; console-setup; and ubiquity should also use Super+Space combination for switching keyboard layouts. reading xkeyboard-config sources and documentations i don't see that xkeyboard-config can support grp:lwin_space and i guess that needs to be the first step to properly support super+space. Original bug report below: Recently I installed Ubuntu 13.10 and Ubuntu GNOME 13.10. I use two keyboard layouts - English and Russian. So I select them on the corresponding screen of ubiquity setup wizard. It quietly set the keyboard switching shortcut to Alt+Shift and wrote this setting to /etc/default/keyboard: # ... XKBMODEL=pc105 XKBLAYOUT=us,ru XKBVARIANT=, XKBOPTIONS=grp:alt_shift_toggle,grp_led:scroll # ... On first boot of installed system the small notification pop-up showed that Ibus will use Super+Space for layout switching. Please fix this configuration inconsistency. -- For other layout switching problems introduced in Ubuntu 13.10 you can see bug 1218322. -- ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic i686 ApportVersion: 2.12.5-0ubuntu2 Architecture: i386 Date: Mon Oct 21 12:16:58 2013 InstallCmdLine: file=/cdrom/preseed/ubuntu-gnome.seed boot=casper only-ubiquity initrd=/casper/initrd.lz quiet splash -- InstallationDate: Installed on 2013-10-21 (0 days ago) InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Release i386 (20131017) MarkForUpload: True SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/xkeyboard-config/+bug/1242572/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1364003] Re: [FFE] mesa 10.3
No idea, but it seems those bugs are probably just bugs in kde5, since I don't hit them with 10.3 on amd64/i386, but I can reproduce something similar with the kde5 ppa, without updating mesa. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1364003 Title: [FFE] mesa 10.3 Status in “mesa” package in Ubuntu: New Bug description: Impact to ubuntu: Proper support for llvm 3.5 without crashing llvmpipe when running tests on i386. kms swrast was requested, will be available in 10.3. Build fixes to support a gallium megablob, reducing size even further. New features GL_ARB_ES3_compatibility on nv50, nvc0, r600, radeonsi, softpipe, llvmpipe GL_ARB_clear_texture on i965 GL_ARB_compressed_texture_pixel_storage on all drivers GL_ARB_conditional_render_inverted on i965, nvc0, softpipe, llvmpipe GL_ARB_derivative_control on i965, nv50, nvc0, r600 GL_ARB_draw_indirect on nvc0, radeonsi GL_ARB_explicit_uniform_location (all drivers that support GLSL) GL_ARB_fragment_layer_viewport on nv50, nvc0, llvmpipe, r600 GL_ARB_gpu_shader5 on i965/gen7, nvc0 GL_ARB_multi_draw_indirect on nvc0, radeonsi GL_ARB_sample_shading on radeonsi GL_ARB_seamless_cubemap_per_texture on i965, llvmpipe, nvc0, r600, radeonsi, softpipe GL_ARB_stencil_texturing on nv50, nvc0, r600, and radeonsi GL_ARB_texture_barrier on nv50, nvc0, r300, r600, radeonsi GL_ARB_texture_compression_bptc on i965/gen7+, nvc0, r600/evergreen+, radeonsi GL_ARB_texture_cube_map_array on radeonsi GL_ARB_texture_gather on r600, radeonsi GL_ARB_texture_query_levels on nv50, nvc0, llvmpipe, r600, radeonsi, softpipe GL_ARB_texture_query_lod on r600, radeonsi GL_ARB_viewport_array on nvc0 GL_AMD_vertex_shader_viewport_index on i965/gen7+, r600 GL_OES_compressed_ETC1_RGB8_texture on nv30, nv50, nvc0, r300, r600, radeonsi, softpipe, llvmpipe GLX_MESA_query_renderer on nv30, nv50, nvc0, r300, r600, radeonsi, softpipe, llvmpipe A new software rasterizer driver (kms_swrast_dri.so) that works with DRM drivers that don't have a full-fledged GEM (such as qxl or simpledrm) Distribute the Khronos GL/glcorearb.h header file. Changes Removed support for the GL_ATI_envmap_bumpmap extension The hacky --enable-32/64-bit is no longer available in configure. To build 32/64 bit mesa refer to the default method recommended by your distribution To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1364003/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1371636] Re: [2.24.51.20140918-1ubuntu1 regression] - /usr/bin/ld: .eh_frame_hdr refers to overlapping FDEs
This affects mesa 10.3 builds too, and happens with debian-experimental as well. ** Changed in: binutils (Ubuntu) Assignee: (unassigned) = Matthias Klose (doko) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1371636 Title: [2.24.51.20140918-1ubuntu1 regression] - /usr/bin/ld: .eh_frame_hdr refers to overlapping FDEs Status in The ARB phylogenetic analysis suite: New Status in “binutils” package in Ubuntu: Confirmed Bug description: Since today mesa fails to build on Ubuntu 14.10 (both i386 and amd64) while it still builds fine on Ubuntu 14.04. Nothing relevant changed in mesa since previous build in my PPA (indeed just some vc4 code only built on arm), the bug is reported by ld which I noticed just got updated with binutils package. Full PPA build log: https://launchpadlibrarian.net/185286922/buildlog_ubuntu-utopic-i386.mesa_10.4~git1409190730.195891~gd~u_FAILEDTOBUILD.txt.gz Error: libtool: link: g++ -fPIC -DPIC -shared -nostdlib /usr/lib/gcc/i686-linux-gnu/4.9/../../../i386-linux-gnu/crti.o /usr/lib/gcc/i686-linux-gnu/4.9/crtbeginS.o -Wl,--whole-archive ../../../../src/gallium/auxiliary/pipe-loader/.libs/libpipe_loader_client.a ../../../../src/gallium/state_trackers/clover/.libs/libclover.a ../../../../src/gallium/auxiliary/.libs/libgallium.a ../../../../src/util/.libs/libmesautil.a ../../../../src/gallium/winsys/sw/null/.libs/libws_null.a ../../../../src/gallium/winsys/sw/dri/.libs/libswdri.a ../../../../src/gallium/winsys/sw/xlib/.libs/libws_xlib.a -Wl,--no-whole-archive -L/usr/lib/llvm-3.5/lib /usr/lib/i386-linux-gnu/libexpat.so -lX11 -lXext -lXfixes -lxcb-dri2 -lxcb -ldrm -ldl -lclangFrontendTool -lclangFrontend -lclangDriver -lclangSerialization -lclangCodeGen -lclangParse -lclangSema -lclangAnalysis -lclangAST -lclangEdit -lclangLex -lclangBasic -lLLVM-3.5.0 -L/usr/lib/gcc/i686-linux-gnu/4.9 -L/usr/lib/gcc/i686-linux-gnu/4.9/../../../i386-linux-gnu -L/usr/lib/gcc/i686-linux-gnu/4.9/../../../../lib -L/lib/i386-linux-gnu -L/lib/../lib -L/usr/lib/i386-linux-gnu -L/usr/lib/../lib -L/usr/lib/gcc/i686-linux-gnu/4.9/../../.. -lstdc++ -lm -lc -lgcc_s /usr/lib/gcc/i686-linux-gnu/4.9/crtendS.o /usr/lib/gcc/i686-linux-gnu/4.9/../../../i386-linux-gnu/crtn.o -O2 -march=pentium3 -Wl,--gc-sections -Wl,--no-undefined -Wl,--version-script=../../../../../../src/gallium/targets/opencl/opencl.sym -Wl,-Bsymbolic-functions -Wl,-z -Wl,relro -Wl,-soname -Wl,libMesaOpenCL.so.1 -o .libs/libMesaOpenCL.so.1.0.0 /usr/bin/ld: .eh_frame_hdr refers to overlapping FDEs. /usr/bin/ld: final link failed: Bad value collect2: error: ld returned 1 exit status Makefile:636: recipe for target 'libMesaOpenCL.la' failed To manage notifications about this bug go to: https://bugs.launchpad.net/arb/+bug/1371636/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1371636] Re: [2.24.51.20140918-1ubuntu1 regression] - /usr/bin/ld: .eh_frame_hdr refers to overlapping FDEs
It doesn't happen if I switch mesa back to using llvm 3.4. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1371636 Title: [2.24.51.20140918-1ubuntu1 regression] - /usr/bin/ld: .eh_frame_hdr refers to overlapping FDEs Status in The ARB phylogenetic analysis suite: New Status in “binutils” package in Ubuntu: Confirmed Bug description: Since today mesa fails to build on Ubuntu 14.10 (both i386 and amd64) while it still builds fine on Ubuntu 14.04. Nothing relevant changed in mesa since previous build in my PPA (indeed just some vc4 code only built on arm), the bug is reported by ld which I noticed just got updated with binutils package. Full PPA build log: https://launchpadlibrarian.net/185286922/buildlog_ubuntu-utopic-i386.mesa_10.4~git1409190730.195891~gd~u_FAILEDTOBUILD.txt.gz Error: libtool: link: g++ -fPIC -DPIC -shared -nostdlib /usr/lib/gcc/i686-linux-gnu/4.9/../../../i386-linux-gnu/crti.o /usr/lib/gcc/i686-linux-gnu/4.9/crtbeginS.o -Wl,--whole-archive ../../../../src/gallium/auxiliary/pipe-loader/.libs/libpipe_loader_client.a ../../../../src/gallium/state_trackers/clover/.libs/libclover.a ../../../../src/gallium/auxiliary/.libs/libgallium.a ../../../../src/util/.libs/libmesautil.a ../../../../src/gallium/winsys/sw/null/.libs/libws_null.a ../../../../src/gallium/winsys/sw/dri/.libs/libswdri.a ../../../../src/gallium/winsys/sw/xlib/.libs/libws_xlib.a -Wl,--no-whole-archive -L/usr/lib/llvm-3.5/lib /usr/lib/i386-linux-gnu/libexpat.so -lX11 -lXext -lXfixes -lxcb-dri2 -lxcb -ldrm -ldl -lclangFrontendTool -lclangFrontend -lclangDriver -lclangSerialization -lclangCodeGen -lclangParse -lclangSema -lclangAnalysis -lclangAST -lclangEdit -lclangLex -lclangBasic -lLLVM-3.5.0 -L/usr/lib/gcc/i686-linux-gnu/4.9 -L/usr/lib/gcc/i686-linux-gnu/4.9/../../../i386-linux-gnu -L/usr/lib/gcc/i686-linux-gnu/4.9/../../../../lib -L/lib/i386-linux-gnu -L/lib/../lib -L/usr/lib/i386-linux-gnu -L/usr/lib/../lib -L/usr/lib/gcc/i686-linux-gnu/4.9/../../.. -lstdc++ -lm -lc -lgcc_s /usr/lib/gcc/i686-linux-gnu/4.9/crtendS.o /usr/lib/gcc/i686-linux-gnu/4.9/../../../i386-linux-gnu/crtn.o -O2 -march=pentium3 -Wl,--gc-sections -Wl,--no-undefined -Wl,--version-script=../../../../../../src/gallium/targets/opencl/opencl.sym -Wl,-Bsymbolic-functions -Wl,-z -Wl,relro -Wl,-soname -Wl,libMesaOpenCL.so.1 -o .libs/libMesaOpenCL.so.1.0.0 /usr/bin/ld: .eh_frame_hdr refers to overlapping FDEs. /usr/bin/ld: final link failed: Bad value collect2: error: ld returned 1 exit status Makefile:636: recipe for target 'libMesaOpenCL.la' failed To manage notifications about this bug go to: https://bugs.launchpad.net/arb/+bug/1371636/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1369510] [NEW] dutch keyboard layout lacks a .com option
Public bug reported: In terms of popularity I would think that when entering an email address .com is a popular option. A lot of people use services like hotmail.com or gmail.com, so the ubuntu-keyboard should have an option for entering .com quickly. ** Affects: ubuntu-keyboard (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1369510 Title: dutch keyboard layout lacks a .com option Status in “ubuntu-keyboard” package in Ubuntu: New Bug description: In terms of popularity I would think that when entering an email address .com is a popular option. A lot of people use services like hotmail.com or gmail.com, so the ubuntu-keyboard should have an option for entering .com quickly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyboard/+bug/1369510/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1364003] Re: [FFE] mesa 10.3
** Changed in: mesa (Ubuntu) Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1364003 Title: [FFE] mesa 10.3 Status in “mesa” package in Ubuntu: New Bug description: Impact to ubuntu: Proper support for llvm 3.5 without crashing llvmpipe when running tests on i386. kms swrast was requested, will be available in 10.3. Build fixes to support a gallium megablob, reducing size even further. New features GL_ARB_ES3_compatibility on nv50, nvc0, r600, radeonsi, softpipe, llvmpipe GL_ARB_clear_texture on i965 GL_ARB_compressed_texture_pixel_storage on all drivers GL_ARB_conditional_render_inverted on i965, nvc0, softpipe, llvmpipe GL_ARB_derivative_control on i965, nv50, nvc0, r600 GL_ARB_draw_indirect on nvc0, radeonsi GL_ARB_explicit_uniform_location (all drivers that support GLSL) GL_ARB_fragment_layer_viewport on nv50, nvc0, llvmpipe, r600 GL_ARB_gpu_shader5 on i965/gen7, nvc0 GL_ARB_multi_draw_indirect on nvc0, radeonsi GL_ARB_sample_shading on radeonsi GL_ARB_seamless_cubemap_per_texture on i965, llvmpipe, nvc0, r600, radeonsi, softpipe GL_ARB_stencil_texturing on nv50, nvc0, r600, and radeonsi GL_ARB_texture_barrier on nv50, nvc0, r300, r600, radeonsi GL_ARB_texture_compression_bptc on i965/gen7+, nvc0, r600/evergreen+, radeonsi GL_ARB_texture_cube_map_array on radeonsi GL_ARB_texture_gather on r600, radeonsi GL_ARB_texture_query_levels on nv50, nvc0, llvmpipe, r600, radeonsi, softpipe GL_ARB_texture_query_lod on r600, radeonsi GL_ARB_viewport_array on nvc0 GL_AMD_vertex_shader_viewport_index on i965/gen7+, r600 GL_OES_compressed_ETC1_RGB8_texture on nv30, nv50, nvc0, r300, r600, radeonsi, softpipe, llvmpipe GLX_MESA_query_renderer on nv30, nv50, nvc0, r300, r600, radeonsi, softpipe, llvmpipe A new software rasterizer driver (kms_swrast_dri.so) that works with DRM drivers that don't have a full-fledged GEM (such as qxl or simpledrm) Distribute the Khronos GL/glcorearb.h header file. Changes Removed support for the GL_ATI_envmap_bumpmap extension The hacky --enable-32/64-bit is no longer available in configure. To build 32/64 bit mesa refer to the default method recommended by your distribution To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1364003/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1364003] [NEW] [FFE] mesa 10.3
Public bug reported: Impact to ubuntu: Proper support for llvm 3.5 without crashing llvmpipe when running tests on i386. kms swrast was requested, will be available in 10.3. Build fixes to support a gallium megablob, reducing size even further. New features GL_ARB_ES3_compatibility on nv50, nvc0, r600, radeonsi, softpipe, llvmpipe GL_ARB_clear_texture on i965 GL_ARB_compressed_texture_pixel_storage on all drivers GL_ARB_conditional_render_inverted on i965, nvc0, softpipe, llvmpipe GL_ARB_derivative_control on i965, nv50, nvc0, r600 GL_ARB_draw_indirect on nvc0, radeonsi GL_ARB_explicit_uniform_location (all drivers that support GLSL) GL_ARB_fragment_layer_viewport on nv50, nvc0, llvmpipe, r600 GL_ARB_gpu_shader5 on i965/gen7, nvc0 GL_ARB_multi_draw_indirect on nvc0, radeonsi GL_ARB_sample_shading on radeonsi GL_ARB_seamless_cubemap_per_texture on i965, llvmpipe, nvc0, r600, radeonsi, softpipe GL_ARB_stencil_texturing on nv50, nvc0, r600, and radeonsi GL_ARB_texture_barrier on nv50, nvc0, r300, r600, radeonsi GL_ARB_texture_compression_bptc on i965/gen7+, nvc0, r600/evergreen+, radeonsi GL_ARB_texture_cube_map_array on radeonsi GL_ARB_texture_gather on r600, radeonsi GL_ARB_texture_query_levels on nv50, nvc0, llvmpipe, r600, radeonsi, softpipe GL_ARB_texture_query_lod on r600, radeonsi GL_ARB_viewport_array on nvc0 GL_AMD_vertex_shader_viewport_index on i965/gen7+, r600 GL_OES_compressed_ETC1_RGB8_texture on nv30, nv50, nvc0, r300, r600, radeonsi, softpipe, llvmpipe GLX_MESA_query_renderer on nv30, nv50, nvc0, r300, r600, radeonsi, softpipe, llvmpipe A new software rasterizer driver (kms_swrast_dri.so) that works with DRM drivers that don't have a full-fledged GEM (such as qxl or simpledrm) Distribute the Khronos GL/glcorearb.h header file. Changes Removed support for the GL_ATI_envmap_bumpmap extension The hacky --enable-32/64-bit is no longer available in configure. To build 32/64 bit mesa refer to the default method recommended by your distribution ** Affects: mesa (Ubuntu) Importance: Undecided Assignee: Maarten Lankhorst (mlankhorst) Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1364003 Title: [FFE] mesa 10.3 Status in “mesa” package in Ubuntu: New Bug description: Impact to ubuntu: Proper support for llvm 3.5 without crashing llvmpipe when running tests on i386. kms swrast was requested, will be available in 10.3. Build fixes to support a gallium megablob, reducing size even further. New features GL_ARB_ES3_compatibility on nv50, nvc0, r600, radeonsi, softpipe, llvmpipe GL_ARB_clear_texture on i965 GL_ARB_compressed_texture_pixel_storage on all drivers GL_ARB_conditional_render_inverted on i965, nvc0, softpipe, llvmpipe GL_ARB_derivative_control on i965, nv50, nvc0, r600 GL_ARB_draw_indirect on nvc0, radeonsi GL_ARB_explicit_uniform_location (all drivers that support GLSL) GL_ARB_fragment_layer_viewport on nv50, nvc0, llvmpipe, r600 GL_ARB_gpu_shader5 on i965/gen7, nvc0 GL_ARB_multi_draw_indirect on nvc0, radeonsi GL_ARB_sample_shading on radeonsi GL_ARB_seamless_cubemap_per_texture on i965, llvmpipe, nvc0, r600, radeonsi, softpipe GL_ARB_stencil_texturing on nv50, nvc0, r600, and radeonsi GL_ARB_texture_barrier on nv50, nvc0, r300, r600, radeonsi GL_ARB_texture_compression_bptc on i965/gen7+, nvc0, r600/evergreen+, radeonsi GL_ARB_texture_cube_map_array on radeonsi GL_ARB_texture_gather on r600, radeonsi GL_ARB_texture_query_levels on nv50, nvc0, llvmpipe, r600, radeonsi, softpipe GL_ARB_texture_query_lod on r600, radeonsi GL_ARB_viewport_array on nvc0 GL_AMD_vertex_shader_viewport_index on i965/gen7+, r600 GL_OES_compressed_ETC1_RGB8_texture on nv30, nv50, nvc0, r300, r600, radeonsi, softpipe, llvmpipe GLX_MESA_query_renderer on nv30, nv50, nvc0, r300, r600, radeonsi, softpipe, llvmpipe A new software rasterizer driver (kms_swrast_dri.so) that works with DRM drivers that don't have a full-fledged GEM (such as qxl or simpledrm) Distribute the Khronos GL/glcorearb.h header file. Changes Removed support for the GL_ATI_envmap_bumpmap extension The hacky --enable-32/64-bit is no longer available in configure. To build 32/64 bit mesa refer to the default method recommended by your distribution To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1364003/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1359262] Re: Chrome + Radeon + hardware acceleration: black Google maps tab
Excellent, can confirm here with chromium-browser, let me check with utopic. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1359262 Title: Chrome + Radeon + hardware acceleration: black Google maps tab Status in “mesa” package in Ubuntu: Confirmed Bug description: When opening Google Maps, i got a completely black tab instead - see the attached image. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libgl1-mesa-dri 10.1.3-0ubuntu0.1 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 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: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Aug 20 17:29:32 2014 DistUpgraded: 2014-04-04 15:34:47,605 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Park [Mobility Radeon HD 5430] [1002:68e1] (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Caicos [Radeon HD 5450] [174b:3000] InstallationDate: Installed on 2012-11-15 (643 days ago) InstallationMedia: Ubuntu-Server 12.10 Quantal Quetzal - Release amd64 (20121017.2) MachineType: Intel Corporation Shark Bay Client platform ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-34-generic root=UUID=5f908618-7000-4276-855c-8ec7a19ce316 ro crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M SourcePackage: mesa UpgradeStatus: Upgraded to trusty on 2014-04-04 (138 days ago) dmi.bios.date: 01/28/2013 dmi.bios.vendor: Intel Corporation dmi.bios.version: HSWLPTU1.86C.0109.R03.1301282055 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Flathead Creek Crb dmi.board.vendor: Intel Corp. dmi.board.version: 2 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnIntelCorporation:bvrHSWLPTU1.86C.0109.R03.1301282055:bd01/28/2013:svnIntelCorporation:pnSharkBayClientplatform:pvr0.1:rvnIntelCorp.:rnFlatheadCreekCrb:rvr2:cvnIntelCorporation:ct3:cvr0.1: dmi.product.name: Shark Bay Client platform dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Wed Aug 20 11:04:41 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu2 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1359262/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1359262] Re: Chrome + Radeon + hardware acceleration: black Google maps tab
Utopic works it seems, testing trusty with xorg-edgers works too, so it's very likely a bug that's been fixed in 10.2.5. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1359262 Title: Chrome + Radeon + hardware acceleration: black Google maps tab Status in “mesa” package in Ubuntu: Confirmed Bug description: When opening Google Maps, i got a completely black tab instead - see the attached image. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libgl1-mesa-dri 10.1.3-0ubuntu0.1 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 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: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Aug 20 17:29:32 2014 DistUpgraded: 2014-04-04 15:34:47,605 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Park [Mobility Radeon HD 5430] [1002:68e1] (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Caicos [Radeon HD 5450] [174b:3000] InstallationDate: Installed on 2012-11-15 (643 days ago) InstallationMedia: Ubuntu-Server 12.10 Quantal Quetzal - Release amd64 (20121017.2) MachineType: Intel Corporation Shark Bay Client platform ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-34-generic root=UUID=5f908618-7000-4276-855c-8ec7a19ce316 ro crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M SourcePackage: mesa UpgradeStatus: Upgraded to trusty on 2014-04-04 (138 days ago) dmi.bios.date: 01/28/2013 dmi.bios.vendor: Intel Corporation dmi.bios.version: HSWLPTU1.86C.0109.R03.1301282055 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Flathead Creek Crb dmi.board.vendor: Intel Corp. dmi.board.version: 2 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnIntelCorporation:bvrHSWLPTU1.86C.0109.R03.1301282055:bd01/28/2013:svnIntelCorporation:pnSharkBayClientplatform:pvr0.1:rvnIntelCorp.:rnFlatheadCreekCrb:rvr2:cvnIntelCorporation:ct3:cvr0.1: dmi.product.name: Shark Bay Client platform dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Wed Aug 20 11:04:41 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu2 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1359262/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1359262] Re: Chrome + Radeon + hardware acceleration: black Google maps tab
Does maps use webgl? ** Changed in: mesa (Ubuntu) Assignee: (unassigned) = Maarten Lankhorst (mlankhorst) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1359262 Title: Chrome + Radeon + hardware acceleration: black Google maps tab Status in “mesa” package in Ubuntu: New Bug description: When opening Google Maps, i got a completely black tab instead - see the attached image. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libgl1-mesa-dri 10.1.3-0ubuntu0.1 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 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: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Aug 20 17:29:32 2014 DistUpgraded: 2014-04-04 15:34:47,605 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Park [Mobility Radeon HD 5430] [1002:68e1] (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Caicos [Radeon HD 5450] [174b:3000] InstallationDate: Installed on 2012-11-15 (643 days ago) InstallationMedia: Ubuntu-Server 12.10 Quantal Quetzal - Release amd64 (20121017.2) MachineType: Intel Corporation Shark Bay Client platform ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-34-generic root=UUID=5f908618-7000-4276-855c-8ec7a19ce316 ro crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M SourcePackage: mesa UpgradeStatus: Upgraded to trusty on 2014-04-04 (138 days ago) dmi.bios.date: 01/28/2013 dmi.bios.vendor: Intel Corporation dmi.bios.version: HSWLPTU1.86C.0109.R03.1301282055 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Flathead Creek Crb dmi.board.vendor: Intel Corp. dmi.board.version: 2 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnIntelCorporation:bvrHSWLPTU1.86C.0109.R03.1301282055:bd01/28/2013:svnIntelCorporation:pnSharkBayClientplatform:pvr0.1:rvnIntelCorp.:rnFlatheadCreekCrb:rvr2:cvnIntelCorporation:ct3:cvr0.1: dmi.product.name: Shark Bay Client platform dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Wed Aug 20 11:04:41 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu2 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1359262/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1325661] Re: second monitor problems
It would be more useful to get some logs with the device already connected, but I'm seeing in the logs: [5.126206] [Firmware Bug]: Duplicate ACPI video bus devices for the same VGA controller, please try module parameter video.allow_duplicates=1if the current driver doesn't work. Maybe try booting with video.allow_duplicates=1 added to the kernel command line? ** Changed in: xorg (Ubuntu) Status: New = Invalid ** Changed in: xorg (Ubuntu) Status: Invalid = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1325661 Title: second monitor problems Status in “xorg” package in Ubuntu: Incomplete Bug description: I plug in a 22 widescreen monitor to my laptop Dell Inspiron 1545, but in system configuration theres no option to set it as a widescreen 1080p monitor, as 4:3 VGA only. I run a sript that fix it for a while, but when I restart my PC appears an error and I most run this script again Do you know some permanent solution? Thanks. #!/bin/bash # Modified for Vaio with 1920x1080 external on VGA XCOM0=`xrandr -q | grep 'VGA1 connected'` XCOM1=xrandr --output VGA1 --primary --mode 1920x1080 --output LVDS1 --mode 1280x800 --left-of VGA1 XCOM2=xrandr --output LVDS1 --mode 1280x800 NEWMODE=xrandr --newmode 1920x1080 148.50 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync ADDMODE=xrandr --addmode VGA1 1920x1080 # Always add this mode in case we need it (better would be to test first) eval $NEWMODE eval $ADDMODE if [ -n $XCOM0 ] || [ ! $XCOM0 = ]; then # if the external monitor is connected, then we tell XRANDR to set up an extended desktop eval $XCOM1 else # if the external monitor is disconnected, then we tell XRANDR to output only to the laptop screen eval $XCOM2 fi exit 0; ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.15.0-4.9-generic 3.15.0-rc7 Uname: Linux 3.15.0-4-generic x86_64 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.14.3-0ubuntu1 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 Jun 2 11:11:24 2014 DistUpgraded: 2014-05-30 15:01:33,471 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.141+bdcom, 3.13.0-27-generic, x86_64: installed bcmwl, 6.30.223.141+bdcom, 3.15.0-4-generic, x86_64: installed virtualbox, 4.3.10, 3.15.0-4-generic, x86_64: installed GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:02aa] Subsystem: Dell Device [1028:02aa] InstallationDate: Installed on 2014-05-30 (3 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) MachineType: Dell Inc. Inspiron 1545 ProcEnviron: LANGUAGE=es_CR:es PATH=(custom, no user) LANG=es_CR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.15.0-4-generic root=UUID=fe21cf91-8e3f-415a-8a39-a5933b38b217 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to utopic on 2014-05-30 (2 days ago) dmi.bios.date: 12/07/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0G848F dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd12/07/2009:svnDellInc.:pnInspiron1545:pvr:rvnDellInc.:rn0G848F:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 1545 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.54-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu4 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Mon Jun 2 10:49:06 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4844 vendor AUO xserver.version: 2:1.15.1-0ubuntu5 To manage notifications about this bug go to:
