[prev in list] [next in list] [prev in thread] [next in thread] 

List:       freedesktop-xorg
Subject:    Re: When starting Evolution /usr/lib/gdm3/gdm-x-session[2309]: (II) modeset information is printed t
From:       Chris Pollock <cpollock () embarqmail ! com>
Date:       2018-09-25 0:46:32
Message-ID: ab3f3ab69206b897d2cf18e86a9a669587b0eddc.camel () embarqmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


On Thu, 2018-09-06 at 10:10 -0500, Chris wrote:
> On Thu, 2018-09-06 at 16:00 +0200, Michel Dänzer wrote:
> > On 2018-09-06 1:53 p.m., Chris wrote:
> > > On Thu, 2018-09-06 at 12:21 +0200, Michel Dänzer wrote:
> > > > On 2018-09-05 9:16 p.m., Adam Jackson wrote:
> > > > > On Sat, 2018-09-01 at 10:24 -0500, Chris wrote:
> > > > > 
> > > > > > When starting Evolution this is output to syslog and
> > > > > > periodically
> > > > > > after it's running:
> > > > > > 
> > > > > > https://pastebin.com/zndBukUG
> > > > > 
> > > > > Evolution, or something it provokes, is asking the server for
> > > > > the
> > > > > list
> > > > > of available video modes. It's doing so with
> > > > > XRRGetScreenResources(),
> > > > > apparently, which prompts the X server to go re-check every
> > > > > available
> > > > > output to see if anything has changed. This is silly, it
> > > > > should
> > > > > be
> > > > > using XRRGetScreenResourcesCurrent() and relying on hotplug
> > > > > events
> > > > > to
> > > > > trigger re-polling. Now, maybe the X server shouldn't print
> > > > > the
> > > > > modes
> > > > > in the log when that happens, [...]
> > > > 
> > > > FWIW, it probably shouldn't indeed, at least not at the default
> > > > log
> > > > verbosity.
> > > > 
> > > 
> > > AFAICT my rsyslog.conf it's the default. I don't know if
> > > uncommenting
> > > these lines would help or not:
> > > 
> > > ### Debugging ###
> > > # $DebugFile /var/log/rsyslog-debug
> > > # $DebugLevel 2
> > > 
> > > # syslog.* /var/log/syslog.debug;RSYSLOG_DebugFormat
> > > # $DebugFile /var/log/syslog.debug
> > > # $DebugLevel 2
> > 
> > Yeah, sorry, different meaning of "should" — the code definitely
> > always
> > has printed these by default, it just arguably shouldn't.
> > 
> > Anyway, Adam is right that the client shouldn't use this
> > functionality
> > in the first place.
> > 
> 
> Besides the bug report submitted at Ubuntu Launchpad that I mentioned
> in my original post I've also submitted them as noted below.
> 
> https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1788739
> 
> https://bugs.freedesktop.org/show_bug.cgi?id=107841
> 
> https://gitlab.gnome.org/GNOME/gdm/issues/418
> 
> The reasoning for this is I'm just not exactly who's purview this
> would
> come under.
> 
I thought I'd add that this also happens when starting and stopping XFE

xfe:
  Installed: 1.42-1
  Candidate: 1.42-1

-- 
Chris
KeyID 0xE372A7DA98E6705C
31.11972; -97.90167 (Elev. 1092 ft)
19:44:42 up 13:06, 1 user, load average: 0.58, 0.49, 0.54
Description:	Ubuntu 18.04.1 LTS, kernel 4.15.0-34-generic


["signature.asc" (application/pgp-signature)]
[Attachment #6 (text/plain)]

_______________________________________________
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: https://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

[prev in list] [next in list] [prev in thread] [next in thread]