xmonad file not found: ~/.xmonad/xmonad-x86_64-linux

Bug #1059358 reported by hotsauce on 2012-10-01
18
This bug affects 4 people
Affects Status Importance Assigned to Milestone
xmonad (Ubuntu)
Undecided
Unassigned

Bug Description

Ubuntu 12.10 beta 2 64bit. I try to run Xmonad or Xmonad-Gnome sessions but the procedure hangs with desktop background and nothing in the session (default Xmonad keys don't work either). Found this output in ~/.xsessions-error:

xmonad 0.10-4build2

~/.xmonad/xmonad-x86_64-linux: executeFile: does not exist (No such file or directory)
gnome-session[1908]: WARNING: Application 'xmonad.desktop' failed to register before timeout
gnome-session[1908]: CRITICAL: We failed, but the fail whale is dead. Sorry....

(gnome-panel:2014): Gtk-CRITICAL **: gtk_accelerator_parse_with_keycode: assertion `accelerator != NULL' failed

** (gnome-panel:2014): WARNING **: Unable to parse mouse modifier '(null)'

** Message: applet now removed from the notification area

(gnome-panel:2014): Gtk-CRITICAL **: gtk_accelerator_parse_with_keycode: assertion `accelerator != NULL' failed

** (gnome-panel:2014): WARNING **: Unable to parse mouse modifier '(null)'

** Message: using fallback from indicator to GtkStatusIcon

** (nautilus:2027): WARNING **: Can not calculate _NET_NUMBER_OF_DESKTOPS

** (nautilus:2027): WARNING **: Can not calculate _NET_NUMBER_OF_DESKTOPS

** (nautilus:2027): WARNING **: Can not get _NET_WORKAREA

** (nautilus:2027): WARNING **: Can not determine workarea, guessing at layout
** Message: moving back from GtkStatusIcon to indicator
~

Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in xmonad (Ubuntu):
status: New → Confirmed
description: updated
Ryan Harper (raharper) wrote :

If you create and install an xmonad.hs file in ~/.xmonad/xmonad.hs the Gnome + Xmonad session works as expected.

It would seem that the xmonad install could/should create a default xmonad.hs file in the user home dir?

Ryan Harper (raharper) wrote :

I experienced this on a clean install of 12.10 Desktop 64-bit edition.

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

Other bug subscribers