[Bug 998310] Re: .Xmodmap file makes xorg temporarily reach high cpu usage (90%-100%) after resume or when coming back from tty to X session

[kmic]

I had the same problem on my Xubuntu 12.04 too, but only for new created
accounts, not for my existing one. After some hours of trial and error
I've got the one file, which made the difference: It was
~/.cache/sessions/xfce4-session-MYCOMPUTERNAME:0 . So simply saving the
desktop session once solved the issue for me.

The hole problem and the solution/workaround is easily to reproduce, at least 
on my machine with Xubuntu 12.04:
1. Create a new user account with an completly empty home-directory.
2. Copy the .Xmodmap file to that home-directory.
3. Log in. There will be a lot of files automatically created, the .Xmodmap 
file will be read in and Xorg will run at 100%.
4. Ignore what Xorg is doing and go (under XFCE) to Main menu - Settings - 
Settings - Session and Startup - Session - Save session.
5. Wait until the session is saved, log out, log in and everything is fine. The 
.Xmodmap is read in, but no Xorg running at 100%.

Notes:
- Maybe you have on an existing account also to disable the 
xfce4-settings-helper in Main menu - Settings - Settings - Session and 
Startup - Application Autostart, but I'm not sure about that.
- When I manually read in the .Xmodmap with the command xmodmap ~/.Xmodmap, 
there will still be 100% CPU for about one minute, both in the existing and in 
the new account. But because I do not need to read it in manually, this is, at 
least for me, no problem.
- Debian seems to have the same bug, see 
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=687112 .

** Bug watch added: Debian Bug tracker #687112
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=687112

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/998310

Title:
  .Xmodmap file makes xorg temporarily reach high cpu usage (90%-100%)
  after resume or when coming back from tty to X session

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/998310/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1017542] Re: grub2 update-grub puts wrong UUID in grub.cfg for system with separate /, /boot partitions when detected by os-prober

[kmic]

Because I had a very similar problem, I just worked through your
attachment. Some remarks:

* First I think, the relevant booting disk is sdd2, not sdb, as you
wrote. Neither sdb1/boot/grub/menu.lst nor sdb1/boot/grub/grub.cfg
contains entries refering to a OS on sdh, but sdd2/boot/grub/grub.cfg
does.

* The UUIDs in sdd2/boot/grub/grub.cfg (lines 950/959 in the attachment)
are correct.

* Instead, the parameter root=/dev/sda2 in sdd2/boot/grub/grub.cfg
(lines 951/960 in the attachment) is incorrect.

But I think, this is not a bug of ubuntus os-prober. It seems to me,
that the problem is in your Arch Linux boot configuration in
sdh1/grub/menu.lst. See lines 1046/1047 and 1052/1053 in the attachment:
There the wrong partitions/drives are set. I suppose, the os-prober just
takes these entries without re-checking them. Try to correct
sdh1/grub/menu.lst and then run update-grub on your ubuntu installation
on sdd2.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1017542

Title:
  grub2 update-grub puts wrong UUID in grub.cfg for system with separate
  /, /boot  partitions when detected by os-prober

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/os-prober/+bug/1017542/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs