One Week With GNOME 3 Classic: Day One (Paradigm Shift)

tl;dr GNOME Classic has some polish problems, but it’s a solid desktop and a significant improvement in workflow over GNOME standard.

Over the course of a week, I’m going to be experimenting with the new GNOME Classic desktop in Fedora 19 beta. I will be recording my experiences (hopefully) daily on this blog. This series of blog entries are entirely my own opinion and do not reflect the opinions of my employer, the Fedora community or anyone besides myself (though I hope my findings will be useful to all).

As explained in my Prologue post earlier today[1], I switched to GNOME 3 Classic mode from KDE. I did this by running

yum install gnome-classic-session

I then logged out of KDE back into KDM and signed in, selecting GNOME Classic as the session type. My initial impression was that the new look was very reminiscent of GNOME 2. Back were the twin bars, one at the top and one at the bottom. They’d restored the ability to see active tasks on each workstation on the lower bar. I noticed immediately the circled “1” in the lower right hand corner as being an indication of an awaiting notification. This cheered me greatly, as the lack of such an indicator was one of my primary issues with the GNOME 3 “standard” implementation.

However, when I clicked on the notification icon, I discovered that the “notification” was in fact a persistent system tray icon (specifically, the krb5-auth-dialog applet). I further discovered that there is no way to “dismiss” this “notification”, because the systray is permanent. So as long as I am using an application with a system tray icon, I will always have an apparent notification awaiting (and therefore training my eye not to pay as close attention to the blue circle in the corner).

For now, I decided to simply turn off the krb5-auth-dialog indicator, since it isn’t really needed on my setup. I mostly have it installed as a reminder when I’m tinkering with SSSD to let me know if I currently have Kerberos credentials. So I decided I could live without it (especially since GNOME itself will now let me know when the credentials are nearing expiration, thanks to Gnome Online Accounts and an excellent job done by Ray Strode, Stef Walter and Ray Debarshi).

So I decided from there that I would start up my usual workloads and see how they measured up. My first stop was to start up Thunderbird, Firefox and Pidgin for my email, web browsing and IRC needs, respectively.

Uh oh. Pidgin has a persistent system tray icon as well. Ah well, so much for notification-area purity. I took a note to file an RFE to have the notification applet not include system tray icons in its count and continued on.

One of the next things I discovered as I got up to see to the call of nature was that my familiar keyboard shortcut “ctrl-alt-l” didn’t work to lock my screen. Ok, maybe that’s not the keystroke command for GNOME? I’ll just go up to the user menu in the upper right and… no “Lock” entry? That’s strange. Ok, I’ll try “Switch user”. No response?

Ok, at this point I begin to suspect that there may be some issues with Classic mode, since I’ve seen plenty of people (including myself) able to lock the screen or use fast-user switching. So I took a note to file some bugs here and resorted to just shutting down my machine instead of locking it. Thanks to a solid-state disk and systemd, my boot up is very fast anyway, and shutdown is more secure than screen-lock anyway, since I’m using disk encryption. Of course, I can’t get IRC messages during this time, but that was the trade-off at the moment. I discussed this later with some of the GNOME developers and learned that his was not a GNOME Classic issue, but a PEBKAC. It turns out that some GNOME functionality is absolutely dependent upon using GDM as the display manager that starts the desktop session. Since I had been using KDM, this functionality was lost to me. The recommended workaround was to install XScreensaver and use that to lock the screen instead. I filed an RFE asking them to add a notification at startup if the session was not launched by GDM to warn users of this lack of functionality, since it would otherwise be off-putting to the casual experimenter.

Continuing on with my investigation, I discovered that some useful features have been added to the gnome-tweak-tool (a handy tool that provides some configuration tweak settings that are not included in the basic gnome-settings dialogs). For one excellent example, the “Shell” tab in the gnome-tweak-tool now has a simple toggle button for “Workspaces only on primary monitor”, which defaults to “On”. I promptly toggled this to “Off” to see how my experience compared to when I had been doing this in GNOME 3.0 (with a difficult-to-discover gconf setting). When I had set this option in GNOME 3.0 (and possibly tried again in 3.2, but I don’t clearly recall), I had encountered many crashes and odd visual distortions when using the second monitor. I was thus very pleased that I have had absolutely no issues so far with this option in GNOME 3.8. Windows behave properly, snapping to place as expected, and even in my oddball work setup (where my secondary monitor is rotated 90 degrees for a vertical workspace), GNOME treats everything on it properly. Given this excellent experience, I opened another RFE for making this the default behavior on GNOME Classic (but probably not on GNOME standard), mostly because this behavior would be much closer to the expectation of a person transitioning from another desktop environment such as GNOME 2.

As I continued to go about my day, I discovered that I had one major problem with my workflow. When I’m at work, I mute my laptop in order to avoid annoying my fellow coworkers. However, what I discovered was that this meant I was very regularly missing summonses on IRC for various topics (and if you’re reading this and were wondering why it was taking me a half-hour or more to reply to you yesterday, this is why). The reason for this is that My general view is that if something is working forthe Pidgin IRC client uses changes to the system tray icon as the mechanism for alerting a user to pending messages and IRC “mentions”. Unfortunately, because in GNOME (both Classic and standard) the system tray icons are hidden until you go look for them, there is no indication that a message has been received. I tried using the pidgin-libnotify plugin to work around this, but that only worked for direct “/msg” pings, so that wasn’t a good enough workaround. This revealed to me a greater problem than just the waiting message-counter issue I My general view is that if something is working fordocumented above.

There are a great number of applications out there that rely on system tray icons to either provide user interaction or inform the user of important events. I understand that the GNOME people are trying to discourage this practice, as they view this as a legacy mechanism with many flaws. I’m not really going to argue this point either way. However, hiding this information strikes me more as a tactic to force your view, rather than a mechanism for convincing other upstreams to adopt it. That impression is hard to shake off. Furthermore, there are a great many applications out there that do useful work, and not all of them are going to be willing to adapt themselves (possibly writing massive amounts of changes to their notification infrastructures) just to support GNOME. It’s reasonable to assume that some of these upstreams will never adopt GNOME’s preferred signaling mechanism. In order to accomodate users that require sensible interaction with these legacy applications, I think that GNOME Classic should permit the display of these system tray applets by default somewhere on one of the two menu visible bars. I’ve opened yet another RFE for this.

This was not my only concern with notifications, either. One thing that puzzled me and I found extremely unintuitive was that when notifications appeared at the bottom of the screen, I was given only one obvious way to interact with them (out of three actual options) and it did not behave the way I intuitively would expect.

  1. Wait for the message to disappear, which would occur after a few seconds. This placed the message into the message tray, so I could review it again later. That’s behaving perfectly from my perspective.
  2. Click on the message. This would immediately change the active window to the workspace and window referenced by the alert. It would also dismiss the alert so that it does not appear in the message tray. It was not obvious that I would want to click there, but its behavior when I did was pretty much what I would want it to do.
  3. Click on the big (X) in the upper-right corner. This is the only obvious interaction element, and it did not do anything like I would expect it to. My natural expectation when clicking (X) would be to indicate to the message tray that “yes, I’ve seen this and don’t need to be reminded of it”. However, the effect of clicking on the (X) is merely to hasten the behavior of waiting for it to disappear. This was highly unintuitive and I filed a bug on it. The discussion on that bug and related bugs seems like no one knows exactly how to handle that, but in my experience I can certainly say that this is the wrong way. Not having a way to immediately dismiss a notification (and forcing me to go into the tray and remove it manually as an extra step) is disruptive to my workflow. I’d also like to point out that KDE had an identical bug recently that was immediately fixed in the way I’m describing here.

I have one final issue that I encountered on my first day, and that was with the behavior of “alt-tab”. The default behavior in GNOME Classic was much closer to the behavior I’d come to expect from most desktop environments, but had one significant jarring behavior. By default, alt-tab will move to the last used window, no matter what workspace it was on. This is extremely disconcerting if, for example, you just paged into a workspace and try to use “alt-tab” to find a particular window in it (which is a behavior so long coded into my muscle-memory that I expect my two year old daughter probably does this instinctually). I filed a bug recommending that we make alt-tab in GNOME Classic behave more like it did in GNOME 2. One of the upstream developers pointed me at a workaround to change a low-level setting that would have this effect. I recommended that this should be the default when using GNOME Classic. We’ll see what the decision on that becomes. At minimum, I think this option should be added to the gnome-tweak-tool.

gsettings set current-workspace-only true

I realize that the above sounds like a real bitch-list, and that’s somewhat the side-effect of the first day operating in a new environment. I want to say in closing that, despite the above (most of which are nitpicks, other than the notification issues I pointed out), I find GNOME Classic thus far to be a very usable and highly-enjoyable environment to work in. It offers me both the classic environment that I’m accustomed to while also offering me all the power of the GNOME Shell (including the overlay with intelligent search, which was the piece I missed the most when switching to KDE). On Day 2, I’m going to try switching my IRC client from Pidgin to Empathy to see how things behave with a more native notification mechanism.

All in all, my first impressions of GNOME Classic are actually largely positive. There are a few rough edges, but I’m giving that some leeway given that it’s effectively the 1.0 of the environment. I think if we clean up these remaining hurdles, GNOME Classic will end up being my preferred operating environment.


  2. Notification icon should not count permanent systray entries
  3. – [RFE] Notify user that some functionality is unavailable when not using GDM
  4. [RFE] Classic mode should have “Workspaces only on primary monitor” set to False by default
  5. [RFE] Do not hide classic systray icons in the message-tray
  6. Clicking on the X on popped up notifications should not add them to the message tray
  7. – The close button on notification popup does not remove the notification from history
  8. alt-tab should not switch workspaces

10 thoughts on “One Week With GNOME 3 Classic: Day One (Paradigm Shift)

  1. I would like to make a comment on the Gnome desktop. I recently have been using Centos with the Gnome desktop. Here are some of the problems that should be looked at.

    1). Password and encryption I set up a RSA 3072 Sign and encryption keys using seahorse I also set a ssh secure shell 6144 bits open pgp ASCII code format 8 bit ????

    2). I set encryption on my swap and home directory not root

    3). I found in other keys a unidentified ssh that could not be validated using export and import to the documents folder and reviewed this

    4). I checked my firewall and closed the port 22 ssh

    5). I went in the terminal and set the secure shell file permissions to chmod 7xx. rwx rx rx basically the owner can read write and execute while the group can read and execute.

    Guess what the server configuration started having problems because of the idea of shared resource no-good bye the way. I do not agree with how file management property rights are being managed usually I set others access to none and allow group resources to read only. SSH even thought it is secured is really not because 8 bit ASCII code is dated way back in the 80’s when I started using this hint early 80’s.

    1. I’m sorry, but it’s not actually clear what the problem is here. Your point 1 is a rambling collection of numbers that don’t have any obvious connection (ssh and PGP are unrelated). I have no idea what your point 3 means at all. As for point 5, SSH intentionally doesn’t work if your .ssh/* files are accessible to anyone at all besides you, because that is a security vulnerability.
      Your last paragraph is unparseable. I have no idea what you are trying to say. Sorry.

  2. I have a laptop that I just installed Fedora 19 Beta. I saw your post and I immediately installed classic session. I liked very much. But I have a work station on my job, that I don’t want to experiment alpha/beta … there is a way to install classic session on Fedora 18 ?

    1. No, GNOME Classic mode is a new feature of Fedora 19 and it relies on GNOME 3.8 to function, which will never be backported to Fedora 18. You can get much of the same functionality by installing a set of extensions from in Fedora 18:

  3. You might be able to solve the notification issue by installing the TopIcons extension, which shows legacy tray icons on top bar. Worth a try.

  4. Ive been using Gnome 3.8 with F19. What bothers me most is the Frequent button showing me the most recently used. I have both KDE and Gnome installed with Fedora 19, as well as some software workbenches. The result in the All section was an accumulation of over 200 icons, all in alphabetical order, as opposed to the way Gnome 3.6 (Fedora 18) had it categorized.
    My frequent area window has 30 icons in it, because my exploring of new applications filled it up. There is no documentation or apparent functionality presented to explain how to selectively purge the Frequent Window entries.
    My opinion is that the favourites bar be thrown out, and those default application icons be made part of the Frequent group, along with the ability to pin them permenantly to that group. The favourites bar is a waste of space and does not contribute much. Having the [:::] lcon list button next to activities would make me happy.
    It take up to 7 keystrokes and much mouse wheel turning to select a less frequently used application. This needs to be reduced to 3 or 4, as is the benefit of working with KDE or Cinnamon or Mate interface.

  5. KDE does have “intelligent” search. In KDE4 press Alt+F2 and try it. I have no idea why it’s not well known but my only complaint is that it lacks support for floating point maths and that use of internet is not clear as it could for example do currency calculations which would require accessing currency exchange rates at best and querying Google with the whole input at worst.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s