1190380 - Ctrl+T does not create new tab under ratpoison in GTK3 builds

Status: RESOLVED WORKSFORME

(Core :: Widget: Gtk, defect)

Description

[m.]

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:42.0) Gecko/20100101 Firefox/42.0
Build ID: 20150803030207

Steps to reproduce:

1. Start Firefox nightly under ratpoison on GNU/Linux
2. Press Ctrl+t t on keyboard


Actual results:

nothing


Expected results:

new tab is opened

Comment 1

[m.]

Additional tests I performed:
- stable Firefox under ratpoison - new tab is opened
- nightly Firefox with new profile - nothing happens
It used to work fine about 2 or 3 weeks ago.

Comment 2

[Nickolay_Ponomarev]

Perhaps related to the switch to GTK3 that happened around that time? https://groups.google.com/forum/#!topic/mozilla.dev.platform/9uYM-c2Guhg
You can test by trying out the builds before/after that change and/or trying the recent GTK2 builds.

If I'm wrong, finding a more specific regression window would help troubleshoot this: http://mozilla.github.io/mozregression/

Comment 3

[m.]

Wow, this mozregression is cool :)
Anyway the last good nightly build is 2015-07-22, the first bad is 2015-07-23.

Comment 4

[m.]

Here is the changeset from the last inbound build 939320b957c5

Comment 5

[Nickolay_Ponomarev]

Great. This does look close to us switching to GTK3 - do you have any idea how this could be relevant?

IIRC, mozregression should give you the link of the form http://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=XXXaab43b65d4&tochange=XXX14f0f3b03 (or two csets - the last good and the last bad one). Could you paste it here?

Comment 6

[m.]

https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=1ee54e043b9b&tochange=939320b957c5

Comment 7

[Nickolay_Ponomarev]

I guessed correctly:
> Mike Hommey — Bug 1186003 - Switch automated builds to Gtk+3. r=mshal

I have no idea how this causes the problem you're seeing...

Comment 8

[m.]

I can try to ask at ratpoison maillist, maybe some developers can have a look..

Comment 9

[m.]

I asked at the ratpoison mail list and the issue does not seem to exist in 32-bit FF, but it was confirmed by another user in 64-bit FF and also in some other window manager (StumpWM).
http://lists.nongnu.org/archive/html/ratpoison-devel/2015-08/msg00010.html

Comment 10

[m.]

This started to work recently, changing status to RESOLVED.