[Ubuntu-x-swat] [Bug 1481330] Re: Xmir crashes when client closes display
For me I found much improved stability on client disconnection after this fix: https://git.launchpad.net/~xmir-team/xorg- server/+git/xmir/commit/?id=9287786b58a90cf376c05692fe4d6d0712946337 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1481330 Title: Xmir crashes when client closes display To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1481330/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1493888] Re: FGLRX incompatible with kernel 4.2
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: fglrx-installer (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1493888 Title: FGLRX incompatible with kernel 4.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1493888/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1493888] Re: FGLRX incompatible with kernel 4.2
Same with the AMD Radeon 6600M and 6700M Series, even with the newest 4.2-10 version. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1493888 Title: FGLRX incompatible with kernel 4.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1493888/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1494634] [NEW] Xmir using glamor on mako shows wrong colours
Public bug reported: Xmir using glamor on mako shows wrong colours. Test case (after applying the fix for bug 1494240): $ xlogo -fg orange -bg purple shows blue on magenta. Workaround: $ Xmir -sw -damage renders colours correctly. ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Tags: xmir ** Tags added: xmir ** Description changed: Xmir using glamor on mako shows wrong colours. - Test case: - $ xlogo -fg orange -bg purple + Test case (after applying the fix for bug 1494240): + $ xlogo -fg orange -bg purple shows blue on magenta. Workaround: - $ Xmir -sw -damage + $ Xmir -sw -damage renders colours correctly. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1494634 Title: Xmir using glamor on mako shows wrong colours To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1494634/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1493888] Re: FGLRX incompatible with kernel 4.2
Workaround at the moment: Still booting up with the 4.1.0-3 kernel version. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1493888 Title: FGLRX incompatible with kernel 4.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1493888/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1494240] Re: Xmir crashes immediately on startup using glamor on Nexus4
** Tags added: xmir -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1494240 Title: Xmir crashes immediately on startup using glamor on Nexus4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libepoxy/+bug/1494240/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1493625] Re: Fails to generate texture when running zenity on Nexus 4
** Tags added: xmir -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1493625 Title: Fails to generate texture when running zenity on Nexus 4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1493625/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1494488] Re: Xorg crashed with SIGABRT in dixGetPrivate()
It works fine with nvidia-355. ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1494488 Title: Xorg crashed with SIGABRT in dixGetPrivate() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1494488/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1493596] Re: Glamor chooses texture format that don't work on Nexus 4
** Tags added: mako -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1493596 Title: Glamor chooses texture format that don't work on Nexus 4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1493596/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1493625] Re: Fails to generate texture when running zenity on Nexus 4
** Tags added: mako -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1493625 Title: Fails to generate texture when running zenity on Nexus 4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1493625/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1494240] Re: Xmir crashes immediately on startup using glamor on Nexus4
** Tags added: mako -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1494240 Title: Xmir crashes immediately on startup using glamor on Nexus4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libepoxy/+bug/1494240/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1472097] Re: XMir crashes when running with -rootless
As far as I can tell "-rootless" mode actually is not implemented yet. I can't make it crash but I can see that it mistakenly maps each X Window (some of which could be menus or even individual widgets like in xedit) to separate Mir surfaces. If we're going to continue on this path then Mir needs full sub-surface (child/embedded surfaces) placement support. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1472097 Title: XMir crashes when running with -rootless To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1472097/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1488409] Re: [MacbookPro11, 2] Using external displays show corrupted, flickering images
This behaviour is still present with kernel 4.2.0-7-generic - when an external display is connected the desktop becomes incorrect tiled/scaled, and the displays rapidly (~10 Hz) flicker. Having the external display (Apple Cinema 27) plugged in during boot is no longer a reliable workaround. Usually it displays a correct login screen at native resolution, then the flickering begins when a desktop session starts. I've found a better workaround, pressing Super+S triggers 'spread mode' causes each display to show a zoomed out overview of the entire desktop. This (so far) reliably fixes the flickering and the tiling. Perhaps I've filed this under the wrong package, could it be a bug in Mir or Unity? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1488409 Title: [MacbookPro11,2] Using external displays show corrupted, flickering images To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1488409/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1494634] Re: Xmir using glamor on mako shows wrong colours
** Tags added: mako -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1494634 Title: Xmir using glamor on mako shows wrong colours To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1494634/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1472097] Re: XMir crashes when running with -rootless
Also, each compositor (including QtMir) would need to be modified to support subsurface placement for rootless to work. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1472097 Title: XMir crashes when running with -rootless To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1472097/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1494915] Re: fglrx-core 2:15.200-0ubuntu4.2: fglrx-core kernel module failed to build
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1494915 Title: fglrx-core 2:15.200-0ubuntu4.2: fglrx-core kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1494915/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1494915] [NEW] fglrx-core 2:15.200-0ubuntu4.2: fglrx-core kernel module failed to build
Public bug reported: i report and came with normal update of kernel from 27 to 28, but even before reboot with install(update manager?)my system got broken,and have broken package,even i try SMART type of upgrade, so i coose to report as new ,but i know this was very popular bug in aug/2015 when this even get thrue update to user of stable verstion-LTS, what to say 1st time i saw it when update kernel to .26 then situation was same with ipdate to .27 then i fix it,and have stable system and hae nice conversation about ,as i report but i also write my solution, but really i dont expect that with regular updates i get updates with boroke my system,but this time i keep last kernel ver 27, ( 3.19.0-27-generic #29-Ubuntu SMP Fri Aug) so simular or same bug with upgrading to kernel 25 to 26, then same from upgrading from 26 to 27 and as i see now,steel same with upgrading from 27 to 28.. i think i will really go as many adviced back to orginal kernel 25! as this is ...nice updates ,after which regular user have broken system,and normal user even can not go to terminal as loging to any other TTY 1,2,3,4,5,6 except TTY7 not going... i will not give up from Ubintu..but many will... its serious bug,and this kind of update sure must not go to normal ,ordinary just user. i think that all this is so unstabile and untested,that i can skip all this ...and go or back to 3.19.o-25 or directlly to kernel 4.1and skip all this ... ProblemType: Package DistroRelease: Ubuntu 15.04 Package: fglrx-core 2:15.200-0ubuntu4.2 ProcVersionSignature: Ubuntu 3.19.0-27.29-generic 3.19.8-ckt5 Uname: Linux 3.19.0-27-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.17.2-0ubuntu1.4 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 DKMSKernelVersion: 3.19.0-28-generic Date: Wed Sep 9 18:44:08 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: fglrx-core, 15.200, 3.19.0-27-generic, x86_64: installed fwts-efi-runtime-dkms, 15.03.01, 3.19.0-27-generic, x86_64: installed fwts-efi-runtime-dkms, 15.03.01, 3.19.0-28-generic, x86_64: installed DuplicateSignature: dkms:fglrx-core:2:15.200-0ubuntu4.2:include/linux/socket.h:99:8: error: expected identifier or ‘(’ before ‘struct’ GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Barts PRO [Radeon HD 6850] [1002:6739] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Device [1682:3116] InstallationDate: Installed on 2015-06-02 (100 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: To be filled by O.E.M. To be filled by O.E.M. PackageVersion: 2:15.200-0ubuntu4.2 ProcKernelCmdLine: \boot\vmlinuz-3.19.0-27-generic.efi.signed ro root=/dev/disk/by-uuid/3014311c-d68a-423a-b0cd-c8a6fa4d74f6 vt.handoff=7 quiet splash amd_iommu=on initrd=boot\initrd.img-3.19.0-27-generic RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4.2 SourcePackage: fglrx-installer Title: fglrx-core 2:15.200-0ubuntu4.2: fglrx-core kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/08/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: SABERTOOTH 990FX R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2501:bd04/08/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FXR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.9-2ubuntu1~vivid2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.9-2ubuntu1~vivid2 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Fri Sep 11 21:42:58 2015 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory fglrx(0): XMM failed to initialize AIGLX error:
[Ubuntu-x-swat] [Bug 408903] Re: Does not handle microphone mute button (KEY_MICMUTE)
** Branch linked: lp:~equinox-i/xfce4-volumed-pulse/add-support-for-mic- mute ** Branch unlinked: lp:~equinox-i/xfce4-volumed-pulse/add-support-for- mic-mute ** Branch linked: lp:~equinox-i/xfce4-volumed-pulse/add-support-for-mic- mute ** Branch unlinked: lp:~equinox-i/xfce4-volumed-pulse/add-support-for- mic-mute ** Branch linked: lp:~equinox-i/xfce4-volumed-pulse/add-support-for-mic- mute -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/408903 Title: Does not handle microphone mute button (KEY_MICMUTE) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/408903/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1494932] Re: fglrx-updates-core 2:15.200-0ubuntu4.2: fglrx-updates-core kernel module failed to build
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer-updates in Ubuntu. https://bugs.launchpad.net/bugs/1494932 Title: fglrx-updates-core 2:15.200-0ubuntu4.2: fglrx-updates-core kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer-updates/+bug/1494932/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1494932] [NEW] fglrx-updates-core 2:15.200-0ubuntu4.2: fglrx-updates-core kernel module failed to build
Public bug reported: The DKMS (2.2.0.3-2ubuntu3) can't build module for fglrx-updates (2:15.200-0ubuntu4.2) with kernel 4.0.9 on Ubuntu 15.04 ProblemType: Package DistroRelease: Ubuntu 15.04 Package: fglrx-updates-core 2:15.200-0ubuntu4.2 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 Uname: Linux 3.19.0-28-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.17.2-0ubuntu1.4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None DKMSKernelVersion: 4.0.9-040009-generic Date: Fri Sep 11 08:35:05 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: fglrx-updates-core, 15.200, 3.19.0-26-generic, x86_64: installed fglrx-updates-core, 15.200, 3.19.0-28-generic, x86_64: installed DuplicateSignature: dkms:fglrx-updates-core:2:15.200-0ubuntu4.2:include/generated/utsrelease.h:2:32: error: invalid digit "9" in octal constant GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Hawaii PRO [Radeon R9 290] [1002:67b1] (rev 80) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:22bd] InstallationDate: Installed on 2015-08-28 (13 days ago) InstallationMedia: It MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. PackageVersion: 2:15.200-0ubuntu4.2 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-28-generic root=UUID=4d83a9b8-9253-4c94-96f4-dea7197f27d7 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4.1 SourcePackage: fglrx-installer-updates Title: fglrx-updates-core 2:15.200-0ubuntu4.2: fglrx-updates-core kernel module failed to build UdevLog: Error: [Errno 2] Arquivo ou diretório não encontrado: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) XorgLogOld: dmi.bios.date: 10/31/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.80 dmi.board.name: N68-VS3 FX dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.80:bd10/31/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN68-VS3FX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.9-2ubuntu1~vivid2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.9-2ubuntu1~vivid2 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Fri Sep 11 17:40:32 2015 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.17.1-0ubuntu3 xserver.video_driver: fglrx ** Affects: fglrx-installer-updates (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package ubuntu vivid -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer-updates in Ubuntu. https://bugs.launchpad.net/bugs/1494932 Title: fglrx-updates-core 2:15.200-0ubuntu4.2: fglrx-updates-core kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer-updates/+bug/1494932/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1489696] Please test proposed package
Hello Shih-Yuan, or anyone else affected, Accepted xorg-server-lts-vivid into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xorg- server-lts-vivid/2:1.17.1-0ubuntu3.1~trusty1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1489696 Title: black screen when enabling rotation on a gpu screen To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1489696/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1489696] Re: black screen when enabling rotation on a gpu screen
Hello Shih-Yuan, or anyone else affected, Accepted xorg-server into vivid-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xorg- server/2:1.17.1-0ubuntu3.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Also affects: xorg-server (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: xorg-server-lts-vivid (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: xorg-server (Ubuntu Trusty) Status: New => Invalid ** Changed in: xorg-server-lts-vivid (Ubuntu Vivid) Status: Confirmed => Invalid ** Changed in: xorg-server (Ubuntu Vivid) Status: Confirmed => Fix Committed ** Tags added: verification-needed ** Changed in: xorg-server-lts-vivid (Ubuntu Trusty) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1489696 Title: black screen when enabling rotation on a gpu screen To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1489696/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1424059] Re: libosmesa6 conflicts with libglapi-mesa-lts-utopic
Hello Doug, or anyone else affected, Accepted mesa-lts-vivid into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mesa-lts- vivid/10.5.9-2ubuntu1~trusty3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1424059 Title: libosmesa6 conflicts with libglapi-mesa-lts-utopic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1424059/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1424059] Re: libosmesa6 conflicts with libglapi-mesa-lts-utopic
** Branch linked: lp:ubuntu/trusty-proposed/mesa-lts-vivid -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1424059 Title: libosmesa6 conflicts with libglapi-mesa-lts-utopic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1424059/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 941826] Re: dlopen(libGL.so) resolves to mesa rather than nvidia
Still here on Wily -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/941826 Title: dlopen(libGL.so) resolves to mesa rather than nvidia To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/941826/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1449319] Re: package fglrx 2:14.501-0ubuntu1 failed to install/upgrade: package fglrx is already installed and configured
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1449319 Title: package fglrx 2:14.501-0ubuntu1 failed to install/upgrade: package fglrx is already installed and configured To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1449319/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1387424] Re: package x11-common 1:7.7+7ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1387424 Title: package x11-common 1:7.7+7ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1387424/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1132736] Re: Xorg fails to start after installing the Hardware Enablement Stack due to missing symlink after purging old xserver-xorg
** Changed in: xorg-lts-vivid (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1132736 Title: Xorg fails to start after installing the Hardware Enablement Stack due to missing symlink after purging old xserver-xorg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1132736/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1132736] Re: Xorg fails to start after installing the Hardware Enablement Stack due to missing symlink after purging old xserver-xorg
I've just updated another computer's HWE stack from Trusty (xserver- xorg) to Vivid (xserver-xorg-lts-vivid) and can confirm again that this bug has been fixed, starting from when you update to Vivid HWE stack. The /etc/X11/X symlink is still deleted when one purges the remnants of the previous stack, but X nevertheless starts normally at boot time. I've changed the bug status to Fix Released for xorg-lts-vivid. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1132736 Title: Xorg fails to start after installing the Hardware Enablement Stack due to missing symlink after purging old xserver-xorg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1132736/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
