Hi All,
I compiled the
alpha5 yesterday.
It works with ubuntu MATE 16.04.3 LTS and with the MATE PowerPC Remix 2017. Unfortunately lightdm doesn't work anymore on Debian Sid.
Error messages:
Code: Select all
[+0.09s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/01_debian.conf
[+0.09s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf
[+0.09s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
[+0.33s] DEBUG: Registered seat module xlocal
[+0.33s] DEBUG: Registered seat module xremote
[+0.33s] DEBUG: Registered seat module unity
[+0.33s] DEBUG: Registered seat module surfaceflinger
[+0.33s] DEBUG: Adding default seat
[+0.33s] DEBUG: Seat: Starting
[+0.33s] DEBUG: Seat: Creating greeter session
[+0.59s] DEBUG: Seat: Setting XDG_SEAT=seat0
[+0.59s] DEBUG: Seat: Creating display server of type x
[+0.59s] DEBUG: Seat: Starting local X display
[+0.59s] DEBUG: Could not run plymouth --ping: Failed to execute child process “plymouth” (No such file or directory)
[+0.59s] DEBUG: Using VT 7
[+0.59s] DEBUG: DisplayServer x-0: Logging to /var/log/lightdm/x-0.log
[+0.59s] DEBUG: DisplayServer x-0: Writing X server authority to /var/run/lightdm/root/:0
[+0.59s] DEBUG: DisplayServer x-0: Launching X Server
[+0.59s] DEBUG: Launching process 3781: /usr/bin/Xorg :0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
[+0.59s] DEBUG: DisplayServer x-0: Waiting for ready signal from X server :0
[+0.59s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
[+0.59s] DEBUG: Registering seat with bus path /org/freedesktop/DisplayManager/Seat0
[+5.71s] DEBUG: Got signal 10 from process 3781
[+5.71s] DEBUG: DisplayServer x-0: Got signal from X server :0
[+5.71s] DEBUG: DisplayServer x-0: Connecting to XServer :0
[+5.71s] DEBUG: Seat: Display server ready, starting session authentication
[+5.71s] DEBUG: Session: Setting XDG_VTNR=7
[+5.71s] DEBUG: Session pid=3918: Started with service 'lightdm-greeter', username 'lightdm'
[+6.35s] DEBUG: Session pid=3918: Authentication complete with return value 0: Success
[+6.35s] DEBUG: Seat: Session authenticated, running command
[+6.35s] DEBUG: Session pid=3918: Setting XDG_VTNR=7
[+6.35s] DEBUG: Session pid=3918: Running command /usr/sbin/lightdm-kde-greeter
[+6.36s] DEBUG: Session pid=3918: Logging to /var/log/lightdm/x-0-greeter.log
[+6.88s] DEBUG: Activating VT 7
[+6.88s] WARNING: Error using VT_WAITACTIVE 7 on /dev/console: No such device or address
[+15.16s] DEBUG: Session pid=3918: Greeter connected version=1.8.5
[+78.29s] DEBUG: Got signal 15 from process 4397
[+78.29s] DEBUG: Caught Terminated signal, shutting down
[+78.29s] DEBUG: Stopping display manager
[+78.29s] DEBUG: Seat: Stopping
[+78.29s] DEBUG: Seat: Stopping display server
[+78.29s] DEBUG: Sending signal 15 to process 3781
[+78.29s] DEBUG: Seat: Stopping session
[+78.29s] DEBUG: Session pid=3918: Sending SIGTERM
[+78.35s] DEBUG: Session pid=3918: Greeter closed communication channel
[+78.35s] DEBUG: Session pid=3918: Exited with return value 15
[+78.35s] DEBUG: Seat: Session stopped
Lightdm works with the
alpha4 without any problems.
Maybe we have a new bug somewhere in the patches from Sep 13, 11:48AM till 15 Sep, 1:12PM.
Additionally the PCSX emulator doesn't work anymore with the new
alpha5. If I start a game with the XVideo driver then I get the following error messages:
Code: Select all
The program 'pcsx' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAccess (attempt to access private resource denied)'.
(Details: serial 49 error_code 10 request_code 130 minor_code 1)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
I don't have these problems with the
alpha4.
Please test it. Maybe some other X apps don't work anymore.
Download:
vmlinux-4.14-alpha5-AmigaOne_X1000_X5000.tar.gz
This bug affects the X1000 and the X5000.
Thanks,
Christian