[intrepid] Can only login using failsafe Gnome: "unable to open file '/usr/share/apps/kxkb/ubuntu.xmodmap' for reading"

Bug #300028 reported by Motin
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
xinit (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

After upgrading Ubunt from 8.04 to 8.10, everything seems to work well.
But some problem happens and I can't figure out the reason.
I fail to start gnome session. When I start Ubuntu, error massage appears.
 It says, "/usr/bin/xmodmap: unable to open file '/usr/share/apps/kxkb/ubuntu.xmodmap' for reading
/usr/bin/xmodmap: 1 error encountered, aborting."
I have to change to safemode to start Ubuntu.
After login, I look over the /usr/share/apps folder. But I can find neither "kxkb" folder nor "ubunt.xmodmap ".
Would you help me solve the problem?
Thank you.

The only way to access the desktop is to use the failsafe Gnome session.

Revision history for this message
yu2 (shecoyu2) wrote :

same thing here

Revision history for this message
Sven Vranckx (sven-vranckx) wrote :

Same happens here, but only for one of the two users on my system. So one user can login without any problem, but the other user can only login using a gnome safe mode session

Revision history for this message
Motin (motin) wrote :

I tried the following to no avail:

 - Removed "im-switch"
 - Installed "kdebase-workspace-bin" as it contains the "kxkb" application
 - Created an empty /usr/share/apps/kxkb/ubuntu.xmodmap directory and file

No help...

Please can anyone help us get this sorted out?

Revision history for this message
Joseph (shockpaneater) wrote :

Hello,everyone.

I was confronted with the same problem, too.
And, it was solved by the following procedures.

I found a file "80ubuntu-xmodmap" in /etc/X11/Xsession.d/

I moved "80ubuntu-xmodmap" to other directory.

so I can login without using "failsafe gnome" session.

try it and good luck!

Revision history for this message
Motin (motin) wrote :

Thanks man! That did the trick!

As for the file, it supposedly has an attempt not to lock up the login routine:

# The "|| true" is to ensure that the Xsession script does not terminate on error
/usr/bin/xmodmap /usr/share/apps/kxkb/ubuntu.xmodmap || true

Apparently, this doesn't work too well... I guess this is the real bug in this matter.

Revision history for this message
Motin (motin) wrote :

A better solution than removing this file, is to change:

/usr/bin/xmodmap /usr/share/apps/kxkb/ubuntu.xmodmap || true

Into:

if [ -f /usr/share/apps/kxkb/ubuntu.xmodmap ]; then
        /usr/bin/xmodmap /usr/share/apps/kxkb/ubuntu.xmodmap || true
fi

Maybe this can be done for the Jaunty Xsession scripts?

Revision history for this message
Motin (motin) wrote :

Bah, was too quick with the cheering there...

This did get rid of the error message "/usr/bin/xmodmap: unable to open file '/usr/share/apps/kxkb/ubuntu.xmodmap' for reading
/usr/bin/xmodmap: 1 error encountered, aborting."

But I still can't login normally. The remaining ~/.xsession-errors :

/etc/gdm/Xsession: Beginning session setup...
Setting IM through im-switch for locale=sv_SE.
Start IM through /etc/X11/xinit/xinput.d/default linked to /etc/X11/xinit/xinput.d/default.

Revision history for this message
Dave Gilbert (ubuntu-treblig) wrote :

at least 4 reporters of the same problem.
Changed package to kdebase-workspace-bin since this seems to relate to the missing file ?

Revision history for this message
Motin (motin) wrote :

I don't think this is a problem with the kxkb file, as I removed it wholly and the problem persists. More likely this is some bug with the X init script - at least in the aspect of making it seemingly impossible to get a correct error description of what is actually failing.

Revision history for this message
Motin (motin) wrote :

Finally I have had time to look at this more.

I compared my install with a chrooted intrepid install with the same packages as my system (so as to get a good reference to default configuration files).

I also did the same with a new user on the system, comparing all user settings directories.

In the end, I removed these three files:
~/.Xauthority
~/.Xscrc
~/.xsession

...logged out and could log back in without problems!

Revision history for this message
Motin (motin) wrote :

I have found at least the real bug with my login. .xsession was empty (0 bytes), and the following introduced the bug again:

touch ~/.xsession

Removing it:

rm ~/.xsession

...then enables login again without using the failsafe option.

Is this the same for you others?

Bryce Harrington (bryce)
tags: added: intrepid
Revision history for this message
ginoroman (ginoroman) wrote :

SOLVED:

go to: /usr/share/apps/

and create a new folder: kxkb

then go to: /etc/X11/Xsession.d/

copy the file: 80ubuntu-xmodmap

and paste it to: /usr/share/apps/kxkb/

finally change the name of "80ubuntu-xmodmap" to: "ubuntu-xmodmap" or "ubuntu.xmodmap" I didn't remeber very well but i think that is the first option: "ubuntu-xmodmap"

Remember to do all this as root.

Revision history for this message
Chad Miller (cmiller) wrote :

Hi all. I have the correct solution for you who find your Compose/Multi key not working. The gist is that KDE put its fingers in the fray, and when you removed some KDE program, it left behind commands in 'conffiles' that empty your modmap additions.

The /etc/X11/Xsession.d/80ubuntu-xmodmap file is created by kdebase-bin . Make sure you can remove 'kdebase-bin' package, and its conf files. Either of:

    $ sudo dpkg -P kdebase-bin
    $ apt-get remove --purge kdebase-bin

If you can rid your system of it, you may continue. If not, then this doesn't apply to you.

(AFAICT) That conffile was somehow orphaned not long ago. Even though you remove the package, the orphaned conffile may still exist. Check. If '/etc/X11/Xsession.d/80ubuntu-xmodmap' still exists and

    $ dpkg -S /etc/X11/Xsession.d/80ubuntu-xmodmap

says nothing owns it, then you may remove it.

After you log in next time, your compose key should work.

Revision history for this message
Bryce Harrington (bryce) wrote :

[This is an automatic notification.]

Hi Motin,

This bug was reported against an earlier version of Ubuntu, can you
test if it still occurs on Lucid?

Please note we also provide technical support for older versions of
Ubuntu, but not in the bug tracker. Instead, to raise the issue through
normal support channels, please see:

    http://www.ubuntu.com/support

If you are the original reporter and can still reproduce the issue on
Lucid, please run the following command to refresh the report:

  apport-collect 300028

If you are not the original reporter, please file a new bug report, so
we can work with you as the original reporter instead (you can reference
bug 300028 in your report if you think it may be related):

  ubuntu-bug xorg

If by chance you can no longer reproduce the issue on Lucid or if you
feel it is no longer relevant, please mark the bug report 'Fix Released'
or 'Invalid' as appropriate, at the following URL:

  https://bugs.launchpad.net/ubuntu/+bug/300028

Changed in xinit (Ubuntu):
status: Confirmed → Incomplete
tags: added: needs-retested-on-lucid-by-june
Revision history for this message
Bryce Harrington (bryce) wrote :

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.

Changed in xinit (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Patrick Welche (prlw1) wrote :

I just saw this bug on natty 11.04, BUT, I also added ppa:gnome3-team/gnome3.

> dpkg -S /etc/X11/Xsession.d/80ubuntu-xmodmap
kdebase-bin: /etc/X11/Xsession.d/80ubuntu-xmodmap

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

Other bug subscribers

Related questions

Remote bug watches

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