Starting arandr leads to frozen desktop

[Jens Herrmann]

I use a Thinkpad R500 on a docking station with an external screen. Arandr is used to change screen resolution to adapt to the external screen. Since the update to Xubuntu 14.04 a couple of days ago the desktop freezes after starting arandr. First I get the arandr window with the main area empty, and cannot use any of the menus, switch application, panel stopped working. Then it takes about 1 minute til the screen layout is added to the main area of the arandr window. The only thing I can use then is the mouse pointer. At this point I have to pull the plug and reboot the system.

What log files are needed for this?

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: arandr 0.1.7.1-1
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
CurrentDesktop: XFCE
Date: Mon Apr 28 15:30:49 2014
EcryptfsInUse: Yes
InstallationDate: Installed on 2013-11-26 (153 days ago)
InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
PackageArchitecture: all
SourcePackage: arandr
UpgradeStatus: Upgraded to trusty on 2014-04-22 (6 days ago)

[chrysn (chrysn)]

hello jens,

thank you for reporting this.

On Mon, Apr 28, 2014 at 01:48:01PM -0000, Jens Herrmann wrote:
> What log files are needed for this?

it's not so much the log files i'd need but the output of the following
commands:

(i don't know your background, so i'll explain in as much detail as i
assume is helpful)

open a terminal window from the applications menu, and enter the
following lines (you can't paste them to the terminal window with
ctrl-v, but you can use the edit/paste menu for it):

xrandr --query --verbose > xrandr-qv.out 2> xrandr-qv.err

xrandr --query > xrandr-q.out 2> xrandr-q.err

xrandr --verbose > xrandr-v.out 2> xrandr-v.err

xrandr > xrandr.out 2> xrandr.err

arandr > arandr.out 2> arandr.err

it can happen that the symptoms you described occur after one of those
lines, in which case i you don't need to execute the other lines.

don't wait for any output, the lines save their output to .out and .err
files in your home directory, which i'd ask you to attach to this bug
report, along with the log files /var/log/Xorg.0.log and
/var/log/Xorg.0.log.old (the latter assuming you just reproduced the
error and rebooted, i hope that it's the right file then).

best regards
chrysn

--
To use raw power is to make yourself infinitely vulnerable to greater powers.
  -- Bene Gesserit axiom

[Jens Herrmann (bugs-u)]

Here are the output files. The Xorg.0.log and Xorg.0.log.old will follow later. At the moment I cannot reproduce it.

[Jens Herrmann (bugs-u)]

All the *.err files were empty files (0 Bytes) which I did not attach therefore.

[chrysn (chrysn)]

On Mon, Apr 28, 2014 at 04:56:23PM -0000, Jens Herrmann wrote:
> Here are the output files. The Xorg.0.log and Xorg.0.log.old will follow
> later. At the moment I cannot reproduce it.

thank you.

as the outputs don't contain anything suspicious, and as this happens at
startup, i assume that it is plugging-related.

you might be able to reproduce it when you run arandr right after
plugging your laptop into the docking station. if you find a way to
reproduce the freeze, please run the mentioned commands instead of
arandr (as you would normally make the freeze happen) to see which of
those commands triggers the problem.

best regards
chrysn

[Jens Herrmann (bugs-u)]

It seems I cannot reproduce this bug anymore, instead I get a different symtom now (see clip attached). Should I file a new bug?