yelp steals focus, cannot be killed

Asked by Guy Verrijdt on 2012-05-28

When opened from certain applications (eg grsync and terminal) but not others (eg nautilus and gedit), the yelp window stays empty, steals focus (forces itself on forground) and cannot be force killed.
The system becomes unusable, although everything seems to continue working.
CPU load increases dramatically, Xorg is the main culprit
Only solution to get control back over the system is a Alt-SysRq-REISUB reboot.
Nothing relevant in .xsession-errors; i have no idea where to look or what to look for in other logs
Should i file a bug? Yelp? Xorg?
Anyone else with this problem?
Please help
(i recorded my desktop, is there a way to attach the video?)

Question information

English Edit question
Ubuntu yelp Edit question
No assignee Edit question
Last query:
Last reply:
Guy Verrijdt (gverrijdt) said : #1

Ubuntu 12.04 64-bit
3.2.0-25-generic Kernel
Gnome 3.4.1
5.8 Gb RAM Intel® Core™ i5-2430M CPU @ 2.40GHz × 4
AMD Radeon HD 7400M Series

Sounds like a bug
You could use youtube to host the video

Guy Verrijdt (gverrijdt) said : #3

Here it is:

OK, a bug, but in yelp? or Xorg?

Never reported a bug befor, so how to do this?


Seems to be with gnome-terminal, as the help on the other app is ok.

You can start the process with:

ubuntu-bug gnome-terminal

I suggest you add the link to your bug too. It's very useful

Guy Verrijdt (gverrijdt) said : #5

Thx, but, as i said, it's not only gnome-terminal, the bug also appears when starting yelp from grsync and gnome-tweak-tools, a.o.
(in the video, i used gedit and terminal only as examples)

'yelp' typed in terminal without arguments works fine, so i can't backtrace with gdb.

In the video you can see Xorg uses a lot of CPU, maybe that's where the bug is?

If i type ubuntu-bug gnome-terminal (or yelp or xorg), i see apport gathering information and sending, and then what??

Can you help with this problem?

Provide an answer of your own, or ask Guy Verrijdt for more information if necessary.

To post a message you must log in.