default xmonad install crashes when first logging in via lightdm in quantel

Bug #1047785 reported by Tom Smith
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
xmonad
Unknown
Unknown
xmonad (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Note: This is very similar to bug #1047794, but the error manifests itself slightly differently.

On a fairly virgin install of the Quantel beta:

$ sudo apt-get install xmonad
then reboot
select xmonad in lightdm
attempt to log in

lightdm simply hangs and becomes completely unresponsive.

not sure what log information I could provide to help diagnose the problem more fully.

will also try to replicate on a completely virgin install.

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: xmonad 0.10-4build2
ProcVersionSignature: Ubuntu 3.5.0-13.14-generic 3.5.3
Uname: Linux 3.5.0-13-generic x86_64
ApportVersion: 2.5.1-0ubuntu7
Architecture: amd64
Date: Sat Sep 8 11:19:40 2012
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905.2)
ProcEnviron:
 LANGUAGE=en_GB:en
 TERM=linux
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: xmonad
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Tom Smith (takeontom) wrote :
Revision history for this message
Iain Lane (laney) wrote : Re: [Bug 1047785] [NEW] default xmonad install crashes when first logging in via lightdm in quantel

On Sat, Sep 08, 2012 at 10:37:02AM -0000, Tom Smith wrote:
> Public bug reported:
>
> On a fairly virgin install of the Quantel beta:
>
> $ sudo apt-get install xmonad
> then reboot
> select xmonad in lightdm
> attempt to log in
>
> lightdm simply hangs and becomes completely unresponsive.
>
> not sure what log information I could provide to help diagnose the
> problem more fully.
>
> will also try to replicate on a completely virgin install.

Hmm, did you update from 12.04? Can you attach ~/.xsession-errors and
/var/log/lightdm/* please? One thing to try would be `xmonad
--recompile' then re-logging in, in case it's caused by the newer
Haskell stack.

Cheers,

--
Iain Lane [ <email address hidden> ]
Debian Developer [ <email address hidden> ]
Ubuntu Developer [ <email address hidden> ]

Tom Smith (takeontom)
description: updated
Revision history for this message
Tom Smith (takeontom) wrote :

Did not update from 12.04, I installed the 12.10 64bit PC image onto a blank laptop from here http://cdimage.ubuntu.com/daily-live/current/.

Am attaching the requested logs.

Note there might be errors from unrelated issues in there. Am about to re-image this laptop and get clean logs for you.

Revision history for this message
Tom Smith (takeontom) wrote :

lightdm.log

Revision history for this message
Tom Smith (takeontom) wrote :

x-0.log

Revision history for this message
Tom Smith (takeontom) wrote :
Revision history for this message
Tom Smith (takeontom) wrote :
Revision history for this message
Tom Smith (takeontom) wrote :

$ sudo xmonad --recompile
xmonad: /home/tom/.xmonad/xmonad.errors: openFile: does not exist (No such file or directory)

And for kicks:

$ xmonad
/home/tom/.xmonad/xmonad-x86_64-linux: executeFile: does not exist (No such file or directory)
X Error of failed request: BadAccess (attempt to access private resource denied)
  Major opcode of failed request: 2 (X_ChangeWindowAttributes)
  Serial number of failed request: 7
  Current serial number in output stream: 8

Revision history for this message
Tom Smith (takeontom) wrote :

Ok, tried on a fresh laptop and it worked this time.

Installed 12-10 using the previously mentioned live CD
$ sudo apt-get update
$ sudo apt-get upgrade
$ sudo apt-get install xmonad

reboot
selected XMonad in lightdm
logged in
went to blank screen, at which point xmonad was working fine.

original bug i think was simply a graphics glitch that looked like it was not working, but in fact was.

Changed in xmonad (Ubuntu):
status: New → Invalid
Revision history for this message
Tom Smith (takeontom) wrote :

Marked as invalid as I think was more a graphics glitch than a problem with XMonad.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.