After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 658317 - the Notifications area is disappear when change the input method use "Ctrl + space"
the Notifications area is disappear when change the input method use "Ctrl + ...
Status: RESOLVED DUPLICATE of bug 613543
Product: gnome-shell
Classification: Core
Component: message-tray
3.0.x
Other Linux
: Normal blocker
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2011-09-06 06:00 UTC by licheng.1212@gmail.com
Modified: 2012-08-27 19:49 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description licheng.1212@gmail.com 2011-09-06 06:00:33 UTC 
1.coming a message,and the notification area is appearance
2.use "Ctrl + space" to change the input method

result:
 The notification area is disappear!!
Comment 1 Guillaume Desmottes 2011-09-06 06:32:50 UTC 
Which empathy and desktop (GNOME 2, GNOME 3, etc) are you using?

What do you mean exactly by "notification area"? Empathy's status icon or Ubuntu's indicator?
Comment 2 licheng.1212@gmail.com 2011-09-06 12:12:07 UTC 
(In reply to comment #1)
> Which empathy and desktop (GNOME 2, GNOME 3, etc) are you using?
> 

 GNOME 3.01 and Empathy 3.02

> What do you mean exactly by "notification area"? Empathy's status icon or
> Ubuntu's indicator?

I mean that is GNOME 3 Shell's notification box.
Comment 3 Guillaume Desmottes 2011-09-07 05:58:01 UTC 
Ok that's a Shell issue then.
Comment 4 Giovanni Campagna 2012-08-27 19:49:48 UTC 
The version you're using is obsolete and no longer maintainer.
The handling for IM keybindings changed in 3.6, which could have fixed this, but the message tray now taking a grab broke it again.
Let's say this is a duplicate of bug 613543, which is about handling keybindings when the shell is modal.

*** This bug has been marked as a duplicate of bug 613543 ***