Bug#879624: Similar issue, also X1 carbon
Looking into possible known issues for at-spi or gnome-terminal-server
did not bring up anything useful for me.
FTR: Installing xfce4 or kde both gives me a working desktop. So this
might actually be a GNOME issue rather than an X issue, or an
interaction of the two.
On Sat, Nov 4, 2017 at 10:14 AM, Michael Hanke <michael.hanke@gmail.com> wrote:
> Update:
>
> I stopped the gdm3 service and started a freshly installed slim login
> manager. I comes right up, no issues.
>
> Starting the GNOME session from slim, however, results in immediate
> failure. This is syslog from the last message of slim to the X server
> shutdown:
>
> Nov 4 09:49:56 meiner slim[8940]: /usr/bin/X11/xauth: file
> /home/mih/.Xauthority does not exist
> Nov 4 09:49:56 meiner org.a11y.Bus[9347]: Activating service
> name='org.a11y.atspi.Registry'
> Nov 4 09:49:56 meiner org.a11y.Bus[9347]: Successfully activated
> service 'org.a11y.atspi.Registry'
> Nov 4 09:49:56 meiner org.a11y.atspi.Registry[9373]: SpiRegistry
> daemon is running with well-known name - org.a11y.atspi.Registry
> Nov 4 09:49:56 meiner gnome-terminal-[9379]: gnome-terminal-server:
> Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
> Nov 4 09:49:56 meiner org.a11y.atspi.Registry[9373]: XIO: fatal IO
> error 11 (Resource temporarily unavailable) on X server ":0.0"
> Nov 4 09:49:56 meiner org.a11y.atspi.Registry[9373]: after 21
> requests (19 known processed) with 0 events remaining.
> Nov 4 09:49:56 meiner org.gtk.vfs.Daemon[9347]: A connection to the
> bus can't be made
> Nov 4 09:49:58 meiner kernel: [ 249.268908] [drm] Reducing the
> compressed framebuffer size. This may lead to less power savings than
> a non-reduced-size. Try to increase stolen memory size if available in
> BIOS.
> Nov 4 09:49:58 meiner slim[8940]: (II) Server terminated successfully
> (0). Closing log file.
>
> On Fri, Nov 3, 2017 at 5:02 PM, Michael Hanke <michael.hanke@gmail.com> wrote:
>> Hi,
>>
>> same here, after upgrade to buster no X anymore. Normal start works, but
>> ends at terminal login. Manual startx makes the screen flicker briefly, then
>> back to terminal. X log contain no errors (EE).
>>
>> Downgrade to stretch didn't change the situation in any way. Going back from
>> linux 4.13 to 4.8 had no effect either.
>>
>> During downgrade gconf2 choked (triggers hung and never completed). During
>> upgrade I think I saw some gconf error message too, but I cannot find a
>> trace of them anywhere.
>>
>> Any advice would be highly appreciated.
>>
>> Thanks in advance
>>
>> Michael
>>
>
>
>
> --
> Michael Hanke
> http://psychoinformatics.de
--
Michael Hanke
http://psychoinformatics.de
Reply to: