Nautilus rendering is broken if GTK_THEME env variable exists

Bug #2018555 reported by Thomas Debesse
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
Expired
Low
Unassigned

Bug Description

In Ubuntu 22.10, nautilus rendering is broken as soon as GTK_THEME environment exists, and there are some other components of GNOME that sets it at desktop launch (for example the Desktop may set it as GTK_THEME=Adwaita:dark).

I have found no GTK_THEME value to make nautilus render properly, even the empty string breaks nautilus.

How to reproduce:

```
killall nautilus
GTK_THEME=
nautilus
```

Then try to select some icons, selected icons will not be displayed as selected.

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: nautilus 1:43.2-0ubuntu1
ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
Uname: Linux 5.19.0-23-generic x86_64
ApportVersion: 2.23.1-0ubuntu3.3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: GNOME
Date: Fri May 5 06:49:41 2023
GsettingsChanges:

ProcEnviron:
 LANGUAGE=fr_FR:en
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.default.apport: [modified]
mtime.conffile..etc.default.apport: 2018-06-16T17:39:00.798346
usr_lib_nautilus:
 file-roller 43.0-1
 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1
 nautilus-image-converter 0.4.0-2
 python3-nautilus 4.0-1

Revision history for this message
Thomas Debesse (illwieckz) wrote :
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for your bug report. What do you mean by 'not be displayed as selected'? Could you add a screenshot showing the issue?

Changed in nautilus (Ubuntu):
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for nautilus (Ubuntu) because there has been no activity for 60 days.]

Changed in nautilus (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Thomas Debesse (illwieckz) wrote (last edit ):

This looks fixed in Ubuntu 23.04 and this was reported against Ubuntu 22.10.
So, now that Ubuntu 22.10 is not supported, this can be considered fixed.

That said, I don't understand why this bug was closed because “there has been no activity for 60 days”.

The bug was still reproducible on Ubuntu 22.10 and reproduction instructions properly described.

Bugs don't disappear by magic because there is no comment to add.

I noticed that setting GTK_THEME to empty string (you also have to export the variable) still changes the way nautilus look in Ubuntu 23.04, but the different look doesn't make nautilus unusable (unlike what happened on Ubuntu 22.10).

```
killall nautilus
export GTK_THEME=
nautilus
```

I'm not sure what happens on Ubuntu 23.04 is a bug, though.

Revision history for this message
Sebastien Bacher (seb128) wrote :

> Bugs don't disappear by magic because there is no comment to add.

No, but launchpad closes bugs set as 'incomplete' with no answer because that's what is usually done when the bug doesn't have enough information to be actionable, anyway if it's fixed in a newer Ubuntu release then it can stay closed now

Revision history for this message
Thomas Debesse (illwieckz) wrote (last edit ):

There was enough information to be actionable:

1. Get Ubuntu with the version the bug is reported for.
2. Apply the reproduction steps given in the very first message reporting the bug:

```
killall nautilus
GTK_THEME=
nautilus
```

The bug was said to be a rendering bug, any human with functional eyes following the reproduction steps could see the rendering bug described in the very first message:

> Then try to select some icons, selected icons will not be displayed as selected.

There was no need for any screenshot: the described bug is that rendering of nautilus would not change between selected and unselected icon. Those words are more meaningful than a screenshot.

Screenshot may even add more ambiguities to the description, since the bug is that no change were rendered, nothing happens between before and after the action that should lead to a change being rendered.

The bug was that the render did not update when you selected something. There was no way a screenshot could describe the bug as the bug was there was no rendering change.

The bug was that something was not rendered. The bug could not be captured by a screenshot. The bug was that the render was not responding to an event.

The issue was complete from the start.

You're just saying no one tried to reproduce the bug, this is different.

Don't let to machines what machines can't do. This issue was written for humans. That's why there was reproduction steps given, and that's why what should be expected and what was given instead was described.

Revision history for this message
Thomas Debesse (illwieckz) wrote :

I may update that sentence:

> You're just saying no one tried to reproduce the bug, this is different.

You're just saying no one tried to reproduce the bug _and it was just decided to let it expire with the distribution version itself_, this is different.

Launchpad can't be taken responsible for, it's a machine.

Revision history for this message
Thomas Debesse (illwieckz) wrote :

To be even more precise: you activated a countdown that would automatically close this issue if no answer would be given to the only question that was not answerable because of the very nature of this bug.

The Launchpad software is just obeying to human decisions, there.

Revision history for this message
Sebastien Bacher (seb128) wrote :

> There was no need for any screenshot: the described bug is that rendering of nautilus would not change
> between selected and unselected icon. Those words are more meaningful than a screenshot.

Sorry but no I didn't understand the description and couldn't reproduce on my machine/it wasn't obvious enough that I saw the problem. I'm one of the maintainers of that packages and felt like we needed more information to work on the issue which is why I set it as an incomplete with a question. You decided to ignore the question and not follow up so the bug closed, the system is working as expected.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.