Re: Gnome 3.16 applications in other desktop environments have an ugly frame around their windows now

[Bazon Bloch <bazonbloch arcor de>]

OK, I'm one step further and found out which packages to downgrade to prevent that strange frame/border around Gnome-windows-problem:

The following downgrades prevent the problem:
Downgrade of gtk3 (3.16.1-1 => 3.14.9-1)
Downgrade of nautilus (3.16.0-1 => 3.14.2-2)
Downgrade of totem (3.16.0-1 => 3.14.2-1)

I found it by downgrading Nautilus at first. The problem kept appearing, in terminal was the message: (starting nautilus 3.16)

$ nautilus

(nautilus:3652): Gtk-WARNING **: Theme parsing error: gtk-widgets.css:2:19: Theming engine 'adwaita' not found

(nautilus:3652): Gtk-WARNING **: Failed to register client: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files
Initializing nautilus-dropbox 2.10.0
<IntrospectionModule 'Nautilus' from '/usr/lib/girepository-1.0/Nautilus-3.0.typelib'>
Insync Nautilus Plugin
<class 'insync_plugin.InsyncExtension'>
Socket: /run/user/1000/ownCloud/socket <=> /ownCloud/socket
Socket File: /run/user/1000/ownCloud/socket
Setting connected to True
Socket watch id: 16
('[__init__ insync plugin]', <InsyncExtension object at 0x7f349237bd70 (uninitialized at 0x0)>)
sys:1: Warning: The property GtkSettings:gtk-button-images is deprecated and shouldn't be used anymore. It will be removed in a future version.
sys:1: Warning: The property GtkSettings:gtk-menu-images is deprecated and shouldn't be used anymore. It will be removed in a future version.

That made me think of downgrading gtk, in which I was right and wrong at the same time:
The frame-around-windows-problem disappeared, but the waring starting nautilus stayed:
starting nautilus 3.14:

$ nautilus

(nautilus:5174): Gtk-WARNING **: Theme parsing error: gtk-widgets.css:2:19: Theming engine 'adwaita' not found

(nautilus:5174): Gtk-WARNING **: Failed to register client: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files
Initializing nautilus-dropbox 2.10.0
ImportError: No module named Nautilus

(nautilus:5174): Nautilus-Python-WARNING **: nautilus_python_init_python failed

(nautilus:5174): GLib-GObject-WARNING **: The property GtkSettings:gtk-button-images is deprecated and shouldn't be used anymore. It will be removed in a future version.

(nautilus:5174): GLib-GObject-WARNING **: The property GtkSettings:gtk-menu-images is deprecated and shouldn't be used anymore. It will be removed in a future version.

So thanks for your input!

2015-04-10 22:02 GMT+02:00 Bazon Bloch <bazonbloch arcor de>:

I am using a Compositor. kwin includes one and when I use xfwm4 as a fallback, I enable the Compositor, too. (and other Compositor effects such as transparency and wobbly are working... )

And this border hasn't been there with Gnome 3.14. + those other DEs / window managers.

Maybe some aspect of foreign compositors working together with Gnome broke in 3.16?

Am 10.04.2015 17:42 schrieb "Emmanuele Bassi" <ebassi gmail com>:

Hi;

On 10 April 2015 at 16:05, drago01 <drago01 gmail com> wrote:
> On Fri, Apr 10, 2015 at 4:59 PM, Bazon Bloch <bazonbloch arcor de> wrote:
>> With Gnome 3.16, applications like nautilus, totem, file-roller, evince,
>> gnome-calculator and others in other desktop environments (XFCE, KDE) have
>> an ugly frame around their windows now. It's probably a not working shadow.
>> See e. g.  http://i.imgur.com/tNdVSI6.png
>> (Screenshot made with XFCE and kwin, but it happens with xfwm4, too.
>> GTK theme = Adwaita-Manjaro. With pure Adwaita, the frame is slightly
>> thinner and white, but still exists.)
>>
>> This is probably related to
>> https://blogs.gnome.org/fmuellner/2015/01/30/a-small-note-on-window-decorations/
>
> No it isn't.
>
>> Does anyone know how to get rid of this frame in other DEs?
>
> This looks like it tryes to draw a shadow and fails to do so because
> you are not using a compositor.

I don't think that's the case.

> So file a bug against gtk.
> As a workaround enable the compositor provided by your DE.

If no compositor is detected, GTK+ already draws a full border, no
rounded corners, and no shadow.

See bug: https://bugzilla.gnome.org/show_bug.cgi?id=746222

Ciao,
 Emmanuele.

--
https://www.bassi.io
[ ] ebassi [@gmail.com]