Created attachment 114810 [details]
kern.log with the latest Xorg packages and with systemd

Created attachment 114811 [details]
Xorg.0.log with the latest Xorg packages and with systemd

Created attachment 114812 [details]
syslog with the latest Xorg packages and with systemd

Created attachment 114813 [details]
dmesg with the latest Xorg packages and with Upstart

I also am have the same issue on my iBook G4. Here are my logs as well.

Created attachment 114814 [details]
my dmseg log

Created attachment 114815 [details]
my kern.log

Created attachment 114816 [details]
my Xorg.0.log

Created attachment 114817 [details]
my syslog

There's no sign of a crash in the attached Xorg.0.log files. Are you sure it's Xorg that's crashing, not e.g. lightdm?

I found the following in the lightdm log:

rican-linux@ibookG4-MATE:~$ cat /media/rican-linux/Lexar/lightdm.log |grep 1482
[+18.98s] DEBUG: Session pid=1482: Started with service 'lightdm-autologin', username 'ubuntu-mate'
[+19.25s] DEBUG: Session pid=1482: Authentication complete with return value 0: Success
[+19.28s] DEBUG: Session pid=1482: Running command /usr/sbin/lightdm-session mate-session
[+19.28s] DEBUG: Session pid=1482: Logging to .xsession-errors
rican-linux@ibookG4-MATE:~$ cat /media/rican-linux/Lexar/lightdm.log |grep -e WARN
[+19.79s] WARNING: Error using VT_WAITACTIVE 7 on /dev/console: No such device or address
rican-linux@ibookG4-MATE:~$

and this in the xsession-error log

rican-linux@ibookG4-MATE:~$ cat /media/rican-linux/Lexar/xsession-errors.log |grep -i error
TypeError: argument of type 'NoneType' is not iterable
GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)
GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)
GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)
GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)
GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)
GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)
GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)
 I am post the entire logs for both.

Created attachment 114834 [details]
lightdm log

Created attachment 114835 [details]
xessions-error log

(In reply to Christian Zigotzky from comment #0)
> [ 9.371697] lightdm-gtk-gre[2731]: unhandled signal 11 at 00000000 nip
> 6f4e61c4 lr 6f4e619c code 30001

Actually, it says right here that the crashing process is lightdm-gtk-gre, not Xorg. Please file a bug against lightdm.

Quote Adam Smith (ubuntu MATE google+)

Since downgrading the xorg fixes it, then surely that makes it an xorg issue?  Since a lot of applications are giving the same unhandled signal error then it has to be a common library or something else in common so again that points to the xorg.

Quote end

I installed the display manager "slim". It started and I could login. But I have the same errors with the MATE desktop like on QEMU. Some colors are wrong on the ubuntu MATE desktop. I can't use the mate-panel. If I click on the panel (menu, icons etc) then nothing happens. The mate panel and the mate taskbar starts again and again. And there is a blank error message in the middle of the desktop. I installed lightdm again and I downgraded the Xorg packages again. Everything works without any problems again.

Artyom Nikolaev (artyom-q) wrote on 2015-04-03 https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1434036: 

Same for me on PowerBook6,5 after upgrade from 14.04 to 15.04 as well as on live 15.04-beta2 boot.
Error messagebox appers after Mate start and then X restarting in a cycle.

This bug is definitely a Xorg bug. It affects all PowerPC machines. Please look in the following thread: http://ubuntuforums.org/showthread.php?t=2264322&page=22&p=13260389#post13260389.

Please help us.

I loaded Ubuntu-MATE 15.04 Beta2 again. This time I added these to my boot parameters drm.debug=14 log_buf_len=14M and pulled the dmesg and journalctl log off. Will be attaching them. Here is a sample of what I am seeing

Apr 09 15:21:52 ubuntu-mate ureadahead[857]: ureadahead:/etc/dbus-1/system.d/org.freedesktop.Accounts.conf: Error retrieving chunk extents: Operation not supported
Apr 09 15:21:52 ubuntu-mate ureadahead[857]: ureadahead:/etc/dbus-1/system.d/org.freedesktop.ColorManager.conf: Error retrieving chunk extents: Operation not supported
Apr 09 15:21:52 ubuntu-mate ureadahead[857]: ureadahead:/etc/dbus-1/system.d/org.freedesktop.DisplayManager.conf: Error retrieving chunk extents: Operation not supported
Apr 09 15:21:52 ubuntu-mate ureadahead[857]: ureadahead:/etc/dbus-1/system.d/org.freedesktop.ModemManager1.conf: Error retrieving chunk extents: Operation not supported
Apr 09 15:21:52 ubuntu-mate ureadahead[857]: ureadahead:/etc/dbus-1/system.d/org.freedesktop.NetworkManager.conf: Error retrieving chunk extents: Operation not supported
Apr 09 15:21:52 ubuntu-mate ureadahead[857]: ureadahead:/etc/dbus-1/system.d/org.freedesktop.PackageKit.conf: Error retrieving chunk extents: Operation not supported
Apr 09 15:21:52 ubuntu-mate ureadahead[857]: ureadahead:/etc/dbus-1/system.d/org.freedesktop.PolicyKit1.conf: Error retrieving chunk extents: Operation not supported
Apr 09 15:21:52 ubuntu-mate ureadahead[857]: ureadahead:/etc/dbus-1/system.d/org.freedesktop.RealtimeKit1.conf: Error retrieving chunk extents: Operation not supported
Apr 09 15:21:52 ubuntu-mate ureadahead[857]: ureadahead:/etc/dbus-1/system.d/org.freedesktop.SystemToolsBackends.conf: Error retrieving chunk extents: Operation not supported

Created attachment 114988 [details]
dmesg-drm_debug

Created attachment 114989 [details]
journalctl

Hi All,

I updated ubuntu MATE 15.04 on my AMIGA one X1000 today. And this is unbelievable. Xorg starts with Upstart and systemd. I don't need to downgrade Xorg. But unfortunately some colors are wrong on the ubuntu MATE desktop. I mean I have the same color problems as on QEMU PowerPC. The mate-settings-daemon starts with systemd 10 minutes after the login. With Upstart the mate-settings-daemon works without any problems immediately. 

[QUOTE=Martin Wimpress ubuntu MATE google+]
I've pinged some devs. Can you see if 'startx' works and update both the Xorg and LP bugs with the results please?
[/QUOTE]

I stopped lightdm with 'service lightdm stop'. After that I started X11 with 'startx'. But it didn't start with 'startx'. I didn't find any error messages in the file 'Xorg.0.log'. I found some error messages in the file '/var/log/syslog'.

[CODE]
Apr  9 23:18:29 ubuntu org.a11y.Bus[4532]: Activating service name='org.a11y.atspi.Registry'
Apr  9 23:18:29 ubuntu org.a11y.Bus[4532]: Successfully activated service 'org.a11y.atspi.Registry'
Apr  9 23:18:29 ubuntu org.a11y.atspi.Registry[4569]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
Apr  9 23:18:29 ubuntu gnome-session[4528]: x-session-manager[4528]: CRITICAL: We failed, but the fail whale is dead. Sorry....
Apr  9 23:18:29 ubuntu x-session-manager[4528]: CRITICAL: We failed, but the fail whale is dead. Sorry....
Apr  9 23:18:29 ubuntu org.a11y.atspi.Registry[4569]: XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
Apr  9 23:18:29 ubuntu org.a11y.atspi.Registry[4569]: after 21 requests (21 known processed) with 0 events remaining.
Apr  9 23:18:29 ubuntu org.gtk.vfs.Daemon[4532]: A connection to the bus can't be made
Apr  9 23:18:29 ubuntu org.gtk.vfs.Daemon[4532]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
Apr  9 23:18:29 ubuntu org.a11y.Bus[4532]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
[/CODE]

I installed Upstart with 'apt-get install upstart-sysv' again and then I downgraded Xorg to version 1.16.0. After a reboot all things work without any problems.

Rgds,

Christian

I booted in the current daily live iso. The DE no longer crashes however I am seeing the colors are all off. I am still noticing errors on the logs and will post them to LP and Freedesktop.

Created attachment 115017 [details]
Xorg-20150410.log

Created attachment 115018 [details]
xsession-error-20150410.log

Created attachment 115019 [details]
dmesg-20150410

Created attachment 115020 [details]
journalctl-20150410

Sounds like the crashes are fixed.

The wrong colours are probably (related to) the well-known Gallium driver endianness bugs.

Does anyone know why Xorg is trying to load fglrx (propietary radeon) on PowerPC? I did not think this was supported?

163.141] (II) LoadModule: "fglrx"
[   163.144] (WW) Warning, couldn't open module fglrx
[   163.144] (II) UnloadModule: "fglrx"
[   163.144] (II) Unloading fglrx
[   163.144] (EE) Failed to load module "fglrx" (module does not exist, 0)