[Touch-packages] [Bug 1581076] [NEW] Xorg segfaults on start-up on Big Endian PPC hardware
Public bug reported: On my Big Endian PowerPC machine, Xorg segfaults when starting. I have been able to confirm that this does not happen when building Xorg from upstream source, and then further confirmed that the source of the segfault appears to be caused by a non-upstreamed, ubuntu specific patch. When building the xorg-server-1.18.3 deb from source, I commented out the following patches from debian/patches/series to try to isolate the source of the crash. With the following patches not-applied, and the resulting .deb package built, the segfault on start does not occur. 08_xfree86_fix_ia64_inx_outx.diff 105_nvidia_autodetect.patch 168_glibc_trace_to_stderr.patch 188_default_primary_to_first_busid.patch 190_cache-xkbcomp_output_for_fast_start_up.patch 191-Xorg-add-an-extra-module-path.patch 232-xf86compatoutput-valgrind.patch no-nv.patch 228_autobind_gpu.patch xf86-inactive-gpuscreen.patch config-add-no-removal.patch xf86-ignore-conflicting-rr-caps.patch fix-detach-gpu.patch disable-rotation-transform-gpuscreens.patch xmir.patch xmir-desktop-file-hint-flag.patch drm_device_keep_trying.patch xi2-resize-touch.patch xmir-fixes.diff ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Description changed: On my Big Endian PowerPC machine, Xorg segfaults when starting. I have been able to confirm that this does not happen when building Xorg from upstream source, and then further confirmed that the source of the segfault appears to be caused by a non-upstreamed, ubuntu specific patch. When building the xorg-server-1.18.3 deb from source, I commented out the following patches from debian/patches/series to try to isolate the - source of the crash: + source of the crash. With the following patches not-applied, and the + resulting .deb package built, the segfault on start does not occur. 08_xfree86_fix_ia64_inx_outx.diff 105_nvidia_autodetect.patch 168_glibc_trace_to_stderr.patch 188_default_primary_to_first_busid.patch 190_cache-xkbcomp_output_for_fast_start_up.patch 191-Xorg-add-an-extra-module-path.patch 232-xf86compatoutput-valgrind.patch no-nv.patch 228_autobind_gpu.patch xf86-inactive-gpuscreen.patch config-add-no-removal.patch xf86-ignore-conflicting-rr-caps.patch fix-detach-gpu.patch disable-rotation-transform-gpuscreens.patch xmir.patch xmir-desktop-file-hint-flag.patch drm_device_keep_trying.patch xi2-resize-touch.patch xmir-fixes.diff -- 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/1581076 Title: Xorg segfaults on start-up on Big Endian PPC hardware Status in xorg package in Ubuntu: New Bug description: On my Big Endian PowerPC machine, Xorg segfaults when starting. I have been able to confirm that this does not happen when building Xorg from upstream source, and then further confirmed that the source of the segfault appears to be caused by a non-upstreamed, ubuntu specific patch. When building the xorg-server-1.18.3 deb from source, I commented out the following patches from debian/patches/series to try to isolate the source of the crash. With the following patches not-applied, and the resulting .deb package built, the segfault on start does not occur. 08_xfree86_fix_ia64_inx_outx.diff 105_nvidia_autodetect.patch 168_glibc_trace_to_stderr.patch 188_default_primary_to_first_busid.patch 190_cache-xkbcomp_output_for_fast_start_up.patch 191-Xorg-add-an-extra-module-path.patch 232-xf86compatoutput-valgrind.patch no-nv.patch 228_autobind_gpu.patch xf86-inactive-gpuscreen.patch config-add-no-removal.patch xf86-ignore-conflicting-rr-caps.patch fix-detach-gpu.patch disable-rotation-transform-gpuscreens.patch xmir.patch xmir-desktop-file-hint-flag.patch drm_device_keep_trying.patch xi2-resize-touch.patch xmir-fixes.diff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1581076/+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 1275042]
Last night, I confirmed that the colors are *correct* with r300g on Big Endian (tested with an RV515), but still incorrect with r600g, as of Mesa 11.0.2. Therefore, I have changed the component for this bug from mesa core to r600. -- 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/1275042 Title: Wrong colors with Mesa 9.2 and Mesa 10.0 on Lubuntu 14.04 PowerPC Status in Mesa: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: Hi all, I've tried Mesa 9.2.2-1 and 10.0.1 on Debian Sid, Lubuntu 13.10, and on Lubuntu 14.04. Unfortunately all have issued false colors in games. They appear to be ABGR instead of RGBA, thus blue becomes green, red becomes alpha etc. Mesa 8.0.5-4 and Mesa 9.1.6 have no color problem. The transitional solution is to install the old Mesa 8.0.X with "Force Version" with the Synaptic package manager on new distributions. We had a problem with wrong colors in SuperTuxKart 0.8 last year. The Irrlicht guys have released a little hack for Irrlicht on Linux PPC (http://irrlicht.sourceforge.net/forum/viewtopic.php?f=7=48577). They told me that is a driver bug, and that workaround costs performance and RAM. Unfortunately this workaround isn't suitable for Mesa 9.2 and higher. At this time we have to install Mesa 9.1.X and lower on new Linux distributions like Lubuntu 13.10, Lubuntu 14.04, Debian Sid etc. It would be nice to solve this issue because we don't need the workaround in the future. Hardware: AmigaOne X1000 (Nemo) PA Semi Dual-core PA6T-1682M, 1.8GHz PowerISA™ v2.04+ CPU "Xena" 500MHz XMOS XS1-L2 124 8GB DDR2 SDRAM HIS Radeon HD 6870, 1 GB RAM OCZ600MXSP 600 Switching power supply RTL 8139/8139C/8139C+ network card TSSTcorp CDDVDW SH-224BB dvd drive ATA ST2000DM001-9YN1 SEAGATE HD ATA ESA 3SF1240GB HD More information: http://en.wikipedia.org/wiki/AmigaOne_X1000 http://www.supertuxkart-amiga.de/amiga/x1000.html Rgds, Christian To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1275042/+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 997483] Re: VT_WAITACTIVE does not work well with a multiseat setup
I appear to still be having this problem in 16.04/Xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/997483 Title: VT_WAITACTIVE does not work well with a multiseat setup Status in Light Display Manager: In Progress Status in lightdm package in Ubuntu: In Progress Bug description: Related to the fix introduced in bug #851612 . 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. lightdm blocked by VT_WAITACTIVE may be the cause... Tested with lightdm 1.2.0-0ubuntu2 in precise. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/997483/+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 1432949] Re: r300 Mesa driver not loading with KMS enabled
Can confirm, I have the same problem. Workaround of 16 bit defaultdepth is successful, albeit sub-optimal. -- 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/1432949 Title: r300 Mesa driver not loading with KMS enabled Status in mesa package in Ubuntu: New Bug description: I cannot get 3D acceleration to work. I was expecting to see the gears via the command 'glxgears' I have KMS enable on my iBook G4 by using the following parameter Linux radeon.modeset=1 video=offb:off video=1024x768-32 video=radeonfb:off radeon.agpmode=-1 Here are my Mesa and Xorg output rican-linux@ibookG4-UbuntuMATE:~$ cat /var/log/Xorg.0.log |grep -e radeon -e dri2 -e drm -e KMS [32.774] Kernel command line: root=UUID=fadadc01-6fd5-49fa-85f3-9e52d0fe6155 ro quiet splash video=offb:off video=1024x768-32 video=radeonfb:off radeon.modeset=1 video=offb:off video=1024x768-32 video=radeonfb:off radeon.agpmode=-1 [33.203] (II) xfree86: Adding drm device (/dev/dri/card0) [35.011] (II) LoadModule: radeon [35.012] (II) Loading /usr/lib/xorg/modules/drivers/radeon_drv.so [35.337] (II) Module radeon: vendor=X.Org Foundation [35.604] (II) [KMS] Kernel modesetting enabled. [35.697] (II) Loading sub module dri2 [35.697] (II) LoadModule: dri2 [35.697] (II) Module dri2 already built-in [35.870] (II) RADEON(0): KMS Color Tiling: enabled [35.870] (II) RADEON(0): KMS Color Tiling 2D: disabled [35.870] (II) RADEON(0): KMS Pageflipping: enabled rican-linux@ibookG4-UbuntuMATE:~$ LIBGL_DEBUG=verbose glxinfo |grep render libGL: screen 0 does not appear to be DRI3 capable libGL: pci id for fd 4: 1002:4e56, driver r300 libGL: OpenDriver: trying /usr/lib/powerpc-linux-gnu/dri/tls/r300_dri.so libGL: OpenDriver: trying /usr/lib/powerpc-linux-gnu/dri/r300_dri.so libGL error: No matching fbConfigs or visuals found libGL error: failed to load driver: r300 libGL: OpenDriver: trying /usr/lib/powerpc-linux-gnu/dri/tls/swrast_dri.so libGL: OpenDriver: trying /usr/lib/powerpc-linux-gnu/dri/swrast_dri.so libGL error: No matching fbConfigs or visuals found libGL error: failed to load driver: swrast Error: couldn't find RGB GLX visual or fbconfig rican-linux@ibookG4-UbuntuMATE:~$ dpkg -l libgl1-mesa-dri Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---= ii libgl1-mesa-dr 10.5.0~rc1-0 powerpc free implementation of the OpenGL rican-linux@ibookG4-UbuntuMATE:~$ rican-linux@ibookG4-UbuntuMATE:~$ lsb_release -rd Description: Ubuntu Vivid Vervet (development branch) Release: 15.04 rican-linux@ibookG4-UbuntuMATE:~$ apt-cache policy libgl1-mesa-dri libgl1-mesa-dri: Installed: 10.5.0~rc1-0ubuntu1 Candidate: 10.5.0-0ubuntu1 Version table: 10.5.0-0ubuntu1 0 500 http://ports.ubuntu.com/ubuntu-ports/ vivid/main powerpc Packages *** 10.5.0~rc1-0ubuntu1 0 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: libgl1-mesa-dri 10.5.0~rc1-0ubuntu1 ProcVersionSignature: Ubuntu 3.18.0-13.14-powerpc-smp 3.18.5 Uname: Linux 3.18.0-13-powerpc-smp ppc ApportVersion: 2.16.1-0ubuntu2 Architecture: powerpc CurrentDesktop: MATE Date: Tue Mar 17 00:58:43 2015 InstallationDate: Installed on 2015-03-17 (0 days ago) InstallationMedia: Ubuntu-MATE 15.04 Vivid Vervet - Alpha powerpc (20150225) SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1432949/+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
