Description of problem: When I run Corebird on one of my machines (64-bit Fedora 25, with all current updates), I can't click on any links in Tweets or in the UI in general. Corebird knows that the links are URLs; if I hover the mouse over one, it will give me a fully expanded version in a popup. However, clicking on one does not activate it as a URL (ie, send it to my web browser). If I click on a link in the general timeline view, Corebird acts as if I'd clicked on non-link text and sends me to the individual tweet view. If I try to click on the link in the individual tweet view, it selects text. If I click on the 'Source' bit in the individual tweet view, nothing happens. Using strace, I can see no attempt by Corebird to run anything, which matches up with the observed behavior that Corebird is not acting as if these are links. I'm not using a Gnome desktop; instead I'm using one based on fvwm. However, this works with an identical fvwm configuration on another machine (or at least it did a couple of days ago). Version-Release number of selected component (if applicable): corebird-1.4.2-1.fc25.x86_64 How reproducible: 100% for me on this machine. It doesn't happen on another almost identical machine, or at least it didn't happen a day or two ago when I ran Corebird there. Steps to Reproduce: 1. Start Corebird 2. Click on a tweet in the timeline to switch to viewing that Tweet 3. Click on 'Source' Actual results: Nothing happens. Expected results: Corebird starts a browser to view the Tweet in the browser. Additional info: Running Corebird from the command line reports only: (corebird:21281): Gtk-WARNING **: Theme parsing error: style.css:14:13: The 'icon-shadow' property has been renamed to '-gtk-icon-shadow' (corebird:21281): Gtk-WARNING **: Theme parsing error: style.css:225:16: The 'outline-radius' property has been renamed to '-gtk-outline-radius' (corebird:21281): Gtk-WARNING **: Theme parsing error: style.css:231:19: The :insensitive pseudo-class is deprecated. Use :disabled instead. (corebird:21281): Gtk-WARNING **: Theme parsing error: style.css:232:25: The :insensitive pseudo-class is deprecated. Use :disabled instead. (corebird:21281): Gtk-WARNING **: Theme parsing error: style.css:237:36: The :insensitive pseudo-class is deprecated. Use :disabled instead.
Did this work for you at some point? If so, do you know what might have changed, UI related (gtk+ especially)? Was there any update of any packages that corebird depends on? Since I've had (and had to track down...) similar problems with awesomewm in the past, can you try another wm and see if it works there? Last question: Can you try activating a link via keynav (i.e. focus tweet row and keep pressing tab until the focus ring is around a link, then press return)?
I only discovered Corebird recently, so this has never worked for me on this machine. However, it does work for me on another identical machine (my home machine, which has the same hardware and the same fvwm window manager configuration). I'm afraid that I can't easily try another window manager, as my fvwm configuration is quite customized and extremely important to my overall desktop environment. I tried keynav and discovered some quite interesting results. First, the keynav worked as you described. And second, what I hadn't noticed before, is that when I click on a link (or try to), what happens visually is that a dotted gray box appears around the link, just as in keynav, and if I hit return the link is activated. Does this sound like some odd GTK+ feature has gotten turned on (or turned off) somewhere? I have what I think are relatively normal Corebird settings, and in particular double-click activation is off. My settings are the same between the office (not working) and home (working).
> and if I hit return the link is activated. Does that mean the link gets opened correctly in your browser? Clicking links seems to work here in fvwm. The only other idea I have is to run corebird with G_MESSAGES_DEBUG=1 set and see if there's any interesting debugging output.
Yes, the link opens (in my expected browser). Running with G_MESSAGES_DEBUG=1 doesn't produce any extra messages. Using G_MESSAGES_DEBUG=all produces extra messages but nothing useful that I can see. Possibly the most interesting bits are from the startup: (corebird:9109): Gtk-DEBUG: Connecting to session manager (corebird:9109): Gtk-DEBUG: Failed to get the GNOME session proxy: The name org.gnome.SessionManager is not owned (corebird:9109): Gtk-DEBUG: Failed to get the Xfce session proxy: The name org.xfce.SessionManager is not owned (corebird:9109): Gtk-DEBUG: Failed to get an inhibit portal proxy: The name org.freedesktop.portal.Desktop is not owned (corebird:9109): corebird-DEBUG: Corebird.vala:202: startup (corebird:9109): Gtk-WARNING **: Theme parsing error: style.css:14:13: The 'icon-shadow' property has been renamed to '-gtk-icon-shadow' (the latter message is a normal one.) I just took advantage of the ridiculous speeds of modern DSL to run Corebird from my home machine, displayed over remote X to my office desktop, and in this configuration I can't click links either (but I can click to focus them, then hit return to activate them). (I wanted to see if 'G_MESSAGES_DEBUG=all' on my working home corebird would produce the same messages on startup. The answer is that it does but also that it doesn't work when displaying to my office desktop.)
I have no idea then. The fact that the link gets focused on click proves that the input works correctly. The actual launching of the browser also seems to work, since Enter/Return works. And it works in fvwm here, so really no clue.
This turns out to be a bug in some versions of fvwm. I was running a slightly different binary at home and at work; the home binary works, the work one doesn't. I've reproduced this issue in the latest version of fvwm (from the current git master) with my configuration file and will report this to the fvwm developers so hopefully they can fix it. My apologies for not being sufficiently careful about verifying the behavior with the exact same binaries, but at least this sorts out the mystery. (This bug is in the Fedora 25 version of fvwm, fvwm-2.6.6-1.fc25.x86_64, at least with my configuration file. It'd be interesting to know which version of fvwm you tested with; if you tested with the same version, this issue must be partly due to a configuration file difference.)
I tested with 2.6.7 and the default config file.
Okay, it looks like something in my configuration file is contributing to this issue. Well, I'll see what I can identify and talk to the fvwm developers about. Thanks for your help with this; it's very much appreciated.
Closed, as per Timm's request in #gnome-hackers on GIMPNet: 13:07 <baedert> I guess https://bugzilla.redhat.com/show_bug.cgi?id=1425611 could be closed