[Ubuntu-x-swat] [Bug 1828790] [NEW] On a Wyse system, if Intel DP is connected before the AMD one, there's a 50% chance the AMD one would have no output
Public bug reported: Summary: On extended SKU (AMD SKU), boot to OS with monitor connecting to Intel DP, then connect another monitor to AMD DP, there is a 50% chance AMD DP has no video output to monitor. Step to reproduce: 1. Attached a 2k/4K monitor to Intel UMA DP port. 2. Power on system and boot to desktop. 3. Attach another 2k/4K monitor to AMD Graphics DP port. Expect result: Both monitors can display correctly Actually result: AMD DP monitor will be black screen. (Intel DP output still normal) ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Affects: xorg-server-hwe-16.04 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: xorg-server (Ubuntu Xenial) Importance: Undecided Status: Won't Fix ** Affects: xorg-server-hwe-16.04 (Ubuntu Xenial) Importance: Undecided Status: New ** Affects: xorg-server (Ubuntu Bionic) Importance: Undecided Status: New ** Affects: xorg-server-hwe-16.04 (Ubuntu Bionic) Importance: Undecided Status: Invalid ** Also affects: xorg-server-hwe-16.04 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1828790 Title: On a Wyse system, if Intel DP is connected before the AMD one, there's a 50% chance the AMD one would have no output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1828790/+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 1368168] Re: package fglrx-core (not installed) failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 2
It seems that this is caused by previously installed fglrx failed to remove x86_64-linux-gnu_gl_conf when it get removed. After removing fglrx, /usr/lib/pxpress/ld.so.conf is still shown in update- alternatives: $ update-alternatives --display x86_64-linux-gnu_gl_conf x86_64-linux-gnu_gl_conf - auto mode link currently points to /usr/lib/pxpress/ld.so.conf /usr/lib/pxpress/ld.so.conf - priority 901 slave x86_64-linux-gnu_10fglrx: /usr/lib/fglrx/10fglrx slave x86_64-linux-gnu_amdcccle: /usr/lib/fglrx/bin/amdcccle slave x86_64-linux-gnu_amdcccle_desktop: /usr/share/fglrx/amdcccle.desktop slave x86_64-linux-gnu_amdccclesu_desktop: /usr/share/fglrx/amdccclesu.desktop slave x86_64-linux-gnu_amdconfig: /usr/lib/fglrx/bin/amdconfig slave x86_64-linux-gnu_amdnotifyui: /usr/lib/fglrx/bin/amdnotifyui slave x86_64-linux-gnu_amdocl32.icd: /usr/lib/fglrx/etc/OpenCL/vendors/amdocl32.icd slave x86_64-linux-gnu_amdocl64.icd: /usr/lib/fglrx/etc/OpenCL/vendors/amdocl64.icd slave x86_64-linux-gnu_amdupdaterandrconfig: /usr/lib/fglrx/bin/amdupdaterandrconfig slave x86_64-linux-gnu_amdxdg_su: /usr/lib/fglrx/bin/amdxdg-su slave x86_64-linux-gnu_ati_conf: /usr/lib/fglrx/etc/ati slave x86_64-linux-gnu_aticonfig: /usr/lib/fglrx/bin/aticonfig slave x86_64-linux-gnu_atieventsd: /usr/lib/fglrx/bin/atieventsd slave x86_64-linux-gnu_atiodcli: /usr/lib/fglrx/bin/atiodcli slave x86_64-linux-gnu_atiode: /usr/lib/fglrx/bin/atiode slave x86_64-linux-gnu_clinfo: /usr/lib/fglrx/bin/clinfo slave x86_64-linux-gnu_fgl_glxgears: /usr/lib/fglrx/bin/fgl_glxgears slave x86_64-linux-gnu_fglrx_dri: /usr/lib/fglrx/dri/fglrx_dri.so slave x86_64-linux-gnu_fglrx_drv: /usr/lib/fglrx/xorg/modules/drivers/fglrx_drv.so slave x86_64-linux-gnu_fglrx_modconf: /lib/fglrx/modprobe.conf slave x86_64-linux-gnu_fglrxinfo: /usr/lib/fglrx/bin/fglrxinfo slave x86_64-linux-gnu_grub_fb_blacklist: /usr/share/fglrx/fglrx-updates.grub-gfxpayload slave x86_64-linux-gnu_libAMDXvBA_cap: /usr/lib/fglrx/libAMDXvBA.cap slave x86_64-linux-gnu_libOpenCL.so: /usr/lib/fglrx/libOpenCL.so slave x86_64-linux-gnu_libaticalcl.so: /usr/lib/fglrx/libaticalcl.so slave x86_64-linux-gnu_libaticalcl.so_lib32: /usr/lib32/fglrx/libaticalcl.so slave x86_64-linux-gnu_libaticalrt.so: /usr/lib/fglrx/libaticalrt.so slave x86_64-linux-gnu_libaticalrt.so_lib32: /usr/lib32/fglrx/libaticalrt.so slave x86_64-linux-gnu_xorg_extra_modules: /usr/lib/pxpress/xorg /usr/lib/x86_64-linux-gnu/mesa/ld.so.conf - priority 500 slave x86_64-linux-gnu_xorg_extra_modules: /usr/lib/x86_64-linux-gnu/xorg/x11-extra-modules Current 'best' version is '/usr/lib/pxpress/ld.so.conf'. And this triggers the error in #3 when postinst of fglrx-core is executed. To manually fix this issue, please do $ sudo update-alternatives --remove x86_64-linux-gnu_gl_conf /usr/lib/pxpress/ld.so.conf -- 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/1368168 Title: package fglrx-core (not installed) failed to install/upgrade: le sous- processus script post-installation installé a retourné une erreur de sortie d'état 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1368168/+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 1368168] Re: package fglrx-core (not installed) failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 2
Setting up fglrx-core (2:14.201-0ubuntu1) ... update-alternatives: error: alternative x86_64-linux-gnu_fglrx_modconf can't be slave of x86_64-linux-gnu_gfxcore_conf: it is a slave of x86_64-linux-gnu_gl_conf dpkg: error processing package fglrx-core (--configure): subprocess installed post-installation script returned error exit status 2 -- 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/1368168 Title: package fglrx-core (not installed) failed to install/upgrade: le sous- processus script post-installation installé a retourné une erreur de sortie d'état 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1368168/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 873495] Re: LightDM fails to start when installed in OEM mode after nvidia-current or nvidia-current-updates are installed
Running precise on a laptop with i7 and nvidia display, and does not have this issue. Possibly it's already fixed. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/873495 Title: LightDM fails to start when installed in OEM mode after nvidia-current or nvidia-current-updates are installed To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/873495/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 851612] Re: Logging out from a FUS session does not reliably return to VT7
Forgot to mention that I'm using precise with lightdm 1.2.0-0ubuntu2. -- 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/851612 Title: Logging out from a FUS session does not reliably return to VT7 To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/851612/+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 851612] Re: Logging out from a FUS session does not reliably return to VT7
Seems that this fix does not work well with a multiseat setup... Saw this in lightdm.log (system call interrupted because of ctrl-alt-del pressed): [+2.97s] DEBUG: New display ready, switching to it [+2.97s] DEBUG: Activating VT 8 [+77.56s] WARNING: Error using VT_WAITACTIVE 8 on /dev/console: Interrupted system call [+77.56s] DEBUG: Got signal 15 from process 1 [+77.56s] DEBUG: Caught Terminated signal, shutting down And in x-1-greeter.log: [+0.48s] DEBUG: Loading users from org.freedesktop.Accounts [+0.48s] DEBUG: Loading user /org/freedesktop/Accounts/User1001 [+0.50s] DEBUG: Loading user /org/freedesktop/Accounts/User1000 [+50.56s] WARNING: Error getting session list from org.freedesktop.DisplayManager: Timeout was reached On vt7, unity-greeter would get stuck after password input. On vt8, unity-greeter appears after that "getting session list timeout", which is about a minute later than vt7, and does not have a password input field. -- 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/851612 Title: Logging out from a FUS session does not reliably return to VT7 To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/851612/+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
